-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
FWIW, I've created the c71511-pass-1 target/repodir for the distributed build farm, and the current status is the following - - waiting for gcc to finish - - then rebuilding glibc - - then enqueing all the other packages
I've adapted the .sql and generated html reports on http://armv7.dev.centos.org/ so that you can have a look if you're interested.
Cheers, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 20/11/15 16:59, Fabian Arrotin wrote:
FWIW, I've created the c71511-pass-1 target/repodir for the distributed build farm, and the current status is the following - waiting for gcc to finish - then rebuilding glibc - then enqueing all the other packages
I've adapted the .sql and generated html reports on http://armv7.dev.centos.org/ so that you can have a look if you're interested.
woo! thanks for taking this up.
- -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 21/11/15 10:26, Karanbir Singh wrote:
On 20/11/15 16:59, Fabian Arrotin wrote:
FWIW, I've created the c71511-pass-1 target/repodir for the distributed build farm, and the current status is the following
- waiting for gcc to finish - then rebuilding glibc - then
enqueing all the other packages
I've adapted the .sql and generated html reports on http://armv7.dev.centos.org/ so that you can have a look if you're interested.
woo! thanks for taking this up.
Just to add that 461 SRPMS built so far (http://armv7.dev.centos.org/built.html) and still some in the queue. Some SRPMS failed due to packages in C7-1503-updates not being already rebuilt (like nss needing newer nss-softokn, now patched and in the queue too). I'll retry those failed packages then.
It would be good starting looking at a minimal set of packages for a 7.1511 install for boards like : - - cubie{board,truck} - - odroid c1 - - raspberry pi 2
Opinions, ideas, etc ?
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 23/11/15 15:38, Fabian Arrotin wrote:
It would be good starting looking at a minimal set of packages for a 7.1511 install for boards like : - cubie{board,truck} - odroid c1 - raspberry pi 2
Opinions, ideas, etc ?
I think thats the best way for us to work from here, lets focus on a bare minimal setup, say the baseline 400 odd rpms needed for the system to be complete, and ssh running, with yum and a few baseline support tools. Then lets look at a few more packages that are typically used in a headless box. Here is my list :
- - bind - - httpd - - php - - gnupg - - mariadb
on your second point, I agree, the cubie, odroid and raspi are a great 3 first step devices to hit up on the armv7 side of things. And if we do end up using upstream kernels, I am also going to propose we call this 'CentOS Linux userland ARMv7 1511' instead of CentOS Linux Armv7 - -> that just clears up the expectations from the user side.
thanks
- -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 23/11/15 17:51, Karanbir Singh wrote:
On 23/11/15 15:38, Fabian Arrotin wrote:
It would be good starting looking at a minimal set of packages for a 7.1511 install for boards like : - cubie{board,truck} - odroid c1 - raspberry pi 2
Opinions, ideas, etc ?
I think thats the best way for us to work from here, lets focus on a bare minimal setup, say the baseline 400 odd rpms needed for the system to be complete, and ssh running, with yum and a few baseline support tools. Then lets look at a few more packages that are typically used in a headless box. Here is my list :
- bind - httpd - php - gnupg - mariadb
on your second point, I agree, the cubie, odroid and raspi are a great 3 first step devices to hit up on the armv7 side of things. And if we do end up using upstream kernels, I am also going to propose we call this 'CentOS Linux userland ARMv7 1511' instead of CentOS Linux Armv7 -> that just clears up the expectations from the user side.
thanks
So we should start discussing about which tools/procedure to use to build those images that people would be then able to consume.
There is/was https://github.com/mndar/rbf , but now that I look at that, it seems that the github repository in fact contains binaries of uboot and kernels not built on our infra, so we can probably reuse that, but if we modify it to only be a tool that
- either build on demand missing files not coming from upstream SRPMS (like uboot/kernel/$others ? ) - either be pointed to url containing those binaries, but that can be audited/verified and so something to discuss too.
I've myself never worked really on arm boards, so if people can give us pointers about where to start, etc ....
+1 on the idea of "CentOS Linux userland ARMv7 $release" if we need to mix with packages not coming from RHEL
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 24/11/15 10:32, Fabian Arrotin wrote:
On 23/11/15 17:51, Karanbir Singh wrote:
On 23/11/15 15:38, Fabian Arrotin wrote:
It would be good starting looking at a minimal set of packages for a 7.1511 install for boards like : - cubie{board,truck} - odroid c1 - raspberry pi 2
Opinions, ideas, etc ?
I think thats the best way for us to work from here, lets focus on a bare minimal setup, say the baseline 400 odd rpms needed for the system to be complete, and ssh running, with yum and a few baseline support tools. Then lets look at a few more packages that are typically used in a headless box. Here is my list :
- bind - httpd - php - gnupg - mariadb
on your second point, I agree, the cubie, odroid and raspi are a great 3 first step devices to hit up on the armv7 side of things. And if we do end up using upstream kernels, I am also going to propose we call this 'CentOS Linux userland ARMv7 1511' instead of CentOS Linux Armv7 -> that just clears up the expectations from the user side.
thanks
So we should start discussing about which tools/procedure to use to build those images that people would be then able to consume.
There is/was https://github.com/mndar/rbf , but now that I look at that, it seems that the github repository in fact contains binaries of uboot and kernels not built on our infra, so we can probably reuse that, but if we modify it to only be a tool that
- either build on demand missing files not coming from upstream SRPMS
(like uboot/kernel/$others ? )
+1 , download and validate sources, do a local build, sign the build ( even if its signing a tar ball ), and consume it from there if we cant work it via a SRPM route. Having said that, even a make & make install & collect files like .spec might be better than nothing.
- either be pointed to url containing those binaries, but that can be
audited/verified and so something to discuss too.
If you have time time and we can do this, it would be good to host these on a centos resource, as long as it does not also violate any licenses or terms.
I've myself never worked really on arm boards, so if people can give us pointers about where to start, etc ....
+1 on the idea of "CentOS Linux userland ARMv7 $release" if we need to mix with packages not coming from RHEL
cool!
So we should start discussing about which tools/procedure to use to build those images that people would be then able to consume.
There is/was https://github.com/mndar/rbf , but now that I look at that, it seems that the github repository in fact contains binaries of uboot and kernels not built on our infra, so we can probably reuse that, but if we modify it to only be a tool that
- either build on demand missing files not coming from upstream SRPMS
(like uboot/kernel/$others ? )
- either be pointed to url containing those binaries, but that can be
audited/verified and so something to discuss too.
I've myself never worked really on arm boards, so if people can give us pointers about where to start, etc ....
I would love to help you out but my semester exams are going on and will be for the next month. So I won't be able to reply quickly. Yes, the github repo contains u-boot cross compiled on my machine. If you would like rbf to use u-boot compiled on the plague farm, it's easy.
You'll have to modify the xml template. First add the u-boot package to the <package> tag (comma separated) and then change the value of the <uboot> tag to /tmp/temp/<path-to-uboot-in-new-rootfs> where /tmp/temp is your <workdir> Hope this helps
-Mandar
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 25/11/15 12:25, Mandar Joshi wrote:
So we should start discussing about which tools/procedure to use to build those images that people would be then able to consume.
There is/was https://github.com/mndar/rbf , but now that I look at that, it seems that the github repository in fact contains binaries of uboot and kernels not built on our infra, so we can probably reuse that, but if we modify it to only be a tool that
- either build on demand missing files not coming from upstream
SRPMS (like uboot/kernel/$others ? ) - either be pointed to url containing those binaries, but that can be audited/verified and so something to discuss too.
I've myself never worked really on arm boards, so if people can give us pointers about where to start, etc ....
I would love to help you out but my semester exams are going on and will be for the next month. So I won't be able to reply quickly. Yes, the github repo contains u-boot cross compiled on my machine. If you would like rbf to use u-boot compiled on the plague farm, it's easy.
You'll have to modify the xml template. First add the u-boot package to the <package> tag (comma separated) and then change the value of the <uboot> tag to /tmp/temp/<path-to-uboot-in-new-rootfs> where /tmp/temp is your <workdir> Hope this helps
-Mandar
Hi Mandar,
Thanks for the clarification. Hope that everything will run fine for your exams, and then hoping to see you back "at full steam" for the armv7 CentOS userland ;-)
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 20/11/15 16:59, Fabian Arrotin wrote:
FWIW, I've created the c71511-pass-1 target/repodir for the
https://twitter.com/kbsingh/status/669864215507791872
there has been some great progress here thanks to Fabian's work.
FWIW, I've created the c71511-pass-1 target/repodir for the distributed build farm, and the current status is the following
- waiting for gcc to finish
- then rebuilding glibc
- then enqueing all the other packages
Hi Fabian, Which repositories did you use to generate the images you've released?
I am creating a new template in RootFS Build Factory.for Cubietruck using the latest CentOS Userland I used the following repos
---------------------------------------------------------------------------------------------- http://armv7.dev.centos.org/repodir/c7-buildroot/ http://armv7.dev.centos.org/repodir/c71511-pass-1/ http://armv7.dev.centos.org/repodir/c71511-updates-1/ http://armv7.dev.centos.org/repodir/comps/ http://armv7.dev.centos.org/repodir/tools/ http://armv7.dev.centos.org/repodir/arm-kernels/4.2.3/ ----------------------------------------------------------------------------------------------
However, "yum ... groupinstall core" keeps giving me the message ---------------------------------------------------------------------------------------------- Resolving Dependencies --> Running transaction check ---> Package NetworkManager.armv7hl 1:1.0.6-27.el7 will be installed... ... ... --.
Finished Dependency Resolution
You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest ---------------------------------------------------------------------------------------------- Full yum output: http://pastebin.com/iVUzbF35
Think I might be missing some repo.
Regards Mandar Joshi
Think I might be missing some repo.
Found it. Seems to have gone past that error. I was missing
http://armv7.dev.centos.org/repodir/c7-pass-1/ http://armv7.dev.centos.org/repodir/c7-updates-1/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 10/12/15 16:10, Mandar Joshi wrote:
FWIW, I've created the c71511-pass-1 target/repodir for the distributed build farm, and the current status is the following -
- waiting for gcc to finish - - then rebuilding glibc - - then
enqueing all the other packages
Hi Fabian, Which repositories did you use to generate the images you've released?
I am creating a new template in RootFS Build Factory.for Cubietruck using the latest CentOS Userland I used the following repos
http://armv7.dev.centos.org/repodir/c7-buildroot/
http://armv7.dev.centos.org/repodir/c71511-pass-1/ http://armv7.dev.centos.org/repodir/c71511-updates-1/ http://armv7.dev.centos.org/repodir/comps/ http://armv7.dev.centos.org/repodir/tools/ http://armv7.dev.centos.org/repodir/arm-kernels/4.2.3/
Hi Mandar,
I haven't used all those repositories coming directly from Plague, but a composed tree. The tree I used is "internal" but is the same as the one that was pushed to buildlogs nodes : http://dev.centos.org/centos/7/os/armhfp/ and http://dev.centos.org/centos/7/extras/armhfp/
I also pointed to specific kernel repositories (as the raspberrypi2 kernel has its own kernel, etc ...) , based on the board model.
I'll need to open a bunch of PR against rbf github repo, as I had to change some specific things. For example, the uboot images are also built through plague as rpm, and so are coming from http://dev.centos.org/centos/7/extras/armhfp/Packages/uboot-images-armv7-201...
It would be good to sync when you'll have time to discuss rbf a bit ;-)
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 12/22/2015 05:18 AM, Mandar Joshi wrote:
It would be good to sync when you'll have time to discuss rbf a bit ;-)
Sent you an email on Dec 18. Have you seen it?
Oh?
Don't see anything new at:
http://mirror.centos.org/altarch/7/isos/armhfp/
Hopefully you will push this out soon. And hopefully it has /usr/share/uboot so we can have a more general image.
-
Fabian Arrotin -
Karanbir Singh -
Karanbir Singh -
Mandar Joshi -
Robert Moskowitz