-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Just to let you know that I've spent (some) time today on some remaining packages, and some new packages built fine.
If someone else also want to have a look at why the remaining packages don't build (probably need patches now), feel free to contribute ;-)
Depending on how it goes, we can eventually decide to go to pass-2 (massive rebuild) against pass-1 only and then evaluate again. Then decide the current status (and updates to be built) , push "official" images for public consumption for various boards (and automate all that), and release the tree to mirrors (after having signed the whole tree)
Happy week-end
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
thanks for the update.
On 09/25/2015 02:31 PM, Fabian Arrotin wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Just to let you know that I've spent (some) time today on some remaining packages, and some new packages built fine.
If someone else also want to have a look at why the remaining packages don't build (probably need patches now), feel free to contribute ;-)
Depending on how it goes, we can eventually decide to go to pass-2 (massive rebuild) against pass-1 only and then evaluate again. Then decide the current status (and updates to be built) , push "official" images for public consumption for various boards (and automate all that), and release the tree to mirrors (after having signed the whole tree)
Happy week-end
Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlYFkv0ACgkQnVkHo1a+xU6PTQCeKA8uoMJoovixxtgMfV/8PbrN YRcAniUiRefyMqiU++NPkJG9mkUBdKVa =WVKq -----END PGP SIGNATURE----- _______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Great news :-)
I will check too if I can help.
Nicolas Repentin nicolas@shivaserv.fr
Le 25 septembre 2015 20:53, Robert Moskowitz a écrit: thanks for the update.
On 09/25/2015 02:31 PM, Fabian Arrotin wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Just to let you know that I've spent (some) time today on some remaining packages, and some new packages built fine.
If someone else also want to have a look at why the remaining packages don't build (probably need patches now), feel free to contribute ;-)
Depending on how it goes, we can eventually decide to go to pass-2 (massive rebuild) against pass-1 only and then evaluate again. Then decide the current status (and updates to be built) , push "official" images for public consumption for various boards (and automate all that), and release the tree to mirrors (after having signed the whole tree)
Happy week-end
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
_______________________________________________ Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 25/09/15 20:31, Fabian Arrotin wrote:
Hi,
Just to let you know that I've spent (some) time today on some remaining packages, and some new packages built fine.
If someone else also want to have a look at why the remaining packages don't build (probably need patches now), feel free to contribute ;-)
Depending on how it goes, we can eventually decide to go to pass-2 (massive rebuild) against pass-1 only and then evaluate again. Then decide the current status (and updates to be built) , push "official" images for public consumption for various boards (and automate all that), and release the tree to mirrors (after having signed the whole tree)
Happy week-end
So no real opinion/momentum on that thread, so just wondering if just using arm-dev list is the way to go or should we discuss that on the centos-devel list ?
Building packages is one thing, but there are other issues, like how can we build reproduceable images that people can download and use) AFAIK, the built images so far were built with kernel built outside of our build environment. Like specific kernel for raspberry pi2, odroid, etc .. How do we want to proceed for those kind of boards ?
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/10/15 14:45, Fabian Arrotin wrote:
On 25/09/15 20:31, Fabian Arrotin wrote:
Hi,
Just to let you know that I've spent (some) time today on some remaining packages, and some new packages built fine.
If someone else also want to have a look at why the remaining packages don't build (probably need patches now), feel free to contribute ;-)
Depending on how it goes, we can eventually decide to go to pass-2 (massive rebuild) against pass-1 only and then evaluate again. Then decide the current status (and updates to be built) , push "official" images for public consumption for various boards (and automate all that), and release the tree to mirrors (after having signed the whole tree)
Happy week-end
So no real opinion/momentum on that thread, so just wondering if just using arm-dev list is the way to go or should we discuss that on the centos-devel list ?
Building packages is one thing, but there are other issues, like how can we build reproduceable images that people can download and use) AFAIK, the built images so far were built with kernel built outside of our build environment. Like specific kernel for raspberry pi2, odroid, etc .. How do we want to proceed for those kind of boards ?
While waiting for input from Community (and myself being busy on CentOS Infra), I decided to enqueue all the pending c7 (1503) updates to the plague build farm. I *just* submitted the jobs in the queue, so : - - packages built will appear at : http://armv7.dev.centos.org/repodir/c7-updates-1/ - - packages build logs will appear at : http://armv7.dev.centos.org/rpmbuild/c7-updates-1/
Cheers,
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 05/10/15 13:45, Fabian Arrotin wrote:
On 25/09/15 20:31, Fabian Arrotin wrote:
Hi,
Just to let you know that I've spent (some) time today on some remaining packages, and some new packages built fine.
If someone else also want to have a look at why the remaining packages don't build (probably need patches now), feel free to contribute ;-)
Depending on how it goes, we can eventually decide to go to pass-2 (massive rebuild) against pass-1 only and then evaluate again. Then decide the current status (and updates to be built) , push "official" images for public consumption for various boards (and automate all that), and release the tree to mirrors (after having signed the whole tree)
Happy week-end
So no real opinion/momentum on that thread, so just wondering if just using arm-dev list is the way to go or should we discuss that on the centos-devel list ?
Building packages is one thing, but there are other issues, like how can we build reproduceable images that people can download and use) AFAIK, the built images so far were built with kernel built outside of our build environment. Like specific kernel for raspberry pi2, odroid, etc .. How do we want to proceed for those kind of boards ?
are there mainline kernels for those boards ? do we have a list of boards we want to target ?