I just deployed the raspberry pi image for some testing and found a couple of rough edges with the armhfp port.
Mock doesn't work out of the box; it'd be nice if it shipped with a working config file, but after having written one builds are failing because the @buildsys-build yum group is not available. I can probably work around this by specifying the list of packages needed for the buildroot manually, but I suspect that the group may not exist because some required packages are missing.
I've confirmed that httpd-devel and apr-devel are not present in the repository; is this an oversight or is there a problem building them for arm?
Regards,
Adam Bishop Systems Development Specialist
gpg: 0x6609D460 t: +44 (0)1235 822 245 xmpp: adamb@jabber.dev.ja.net
jisc.ac.uk
Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.
Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.
On 2016-04-03 15:12, Adam Bishop wrote:
I just deployed the raspberry pi image for some testing and found a couple of rough edges with the armhfp port.
Mock doesn't work out of the box; it'd be nice if it shipped with a working config file, but after having written one builds are failing because the @buildsys-build yum group is not available.
Funnily enough, I pointed out the exact same thing a week or two ago. The response was that this group is no longer used and the packages are instead included in the base root - except that clearly isn't what actually happens.
I can probably work around this by specifying the list of packages needed for the buildroot manually, but I suspect that the group may not exist because some required packages are missing.
They exist, at least on aarch64 and armv5tel (RedSleeve), so it is a virtual certainty they are there on c7 armhf. What you need is: http://ftp.redsleeve.org/pub/el6/6.7/comps.xml and make a dummy empty repository out of it: createrepo -g comps.xml .
Add that path to that repo to your mock repositories, and all will start working just fine.
I've confirmed that httpd-devel and apr-devel are not present in the repository; is this an oversight or is there a problem building them for arm?
Interesting, they are missing on armhf, but they are there on aarch64. :-/
Gordan
On 3 Apr 2016, at 15:31, Gordan Bobic gordan@redsleeve.org wrote:
Funnily enough, I pointed out the exact same thing a week or two ago. The response was that this group is no longer used and the packages are instead included in the base root - except that clearly isn't what actually happens.
I tried a few things (removing the groupinstall entirely, building for fedora etc.) but didn't get anywhere - if that is how it's supposed to work, it's definitely not obvious how to configure it.
Add that path to that repo to your mock repositories, and all will start working just fine.
Thanks, I'll give that a try.
Interesting, they are missing on armhf, but they are there on aarch64. :-/
Yup, hopefully someone can magic them back into the armhf repository.
Regards,
Adam Bishop
gpg: 0x6609D460
jisc.ac.uk
Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.
Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.
On 04/03/2016 09:31 AM, Gordan Bobic wrote:
On 2016-04-03 15:12, Adam Bishop wrote:
I just deployed the raspberry pi image for some testing and found a couple of rough edges with the armhfp port.
Mock doesn't work out of the box; it'd be nice if it shipped with a working config file, but after having written one builds are failing because the @buildsys-build yum group is not available.
Funnily enough, I pointed out the exact same thing a week or two ago. The response was that this group is no longer used and the packages are instead included in the base root - except that clearly isn't what actually happens.
It really is. The mock configs are in git, you can see that we spell out the packages for the buildroot.
I can probably work around this by specifying the list of packages needed for the buildroot manually, but I suspect that the group may not exist because some required packages are missing.
They exist, at least on aarch64 and armv5tel (RedSleeve), so it is a virtual certainty they are there on c7 armhf. What you need is: http://ftp.redsleeve.org/pub/el6/6.7/comps.xml and make a dummy empty repository out of it: createrepo -g comps.xml .
Redsleeve makes changes, and that's up to them. The buildsys-build group has always come from EPEL, even on x86_64.
Add that path to that repo to your mock repositories, and all will start working just fine.
I've confirmed that httpd-devel and apr-devel are not present in the repository; is this an oversight or is there a problem building them for arm?
Interesting, they are missing on armhf, but they are there on aarch64. :-/
The buildsys-build group isn't available on aarch64 for CentOS either.
On 2016-04-04 13:17, Jim Perrin wrote:
On 04/03/2016 09:31 AM, Gordan Bobic wrote:
On 2016-04-03 15:12, Adam Bishop wrote:
I just deployed the raspberry pi image for some testing and found a couple of rough edges with the armhfp port.
Mock doesn't work out of the box; it'd be nice if it shipped with a working config file, but after having written one builds are failing because the @buildsys-build yum group is not available.
Funnily enough, I pointed out the exact same thing a week or two ago. The response was that this group is no longer used and the packages are instead included in the base root - except that clearly isn't what actually happens.
It really is. The mock configs are in git, you can see that we spell out the packages for the buildroot.
So perhaps the correct thing to do would be to make sure a suitable centos-7-aarch64.cfg config file ships with mock as provided in the CentOS 7 aarch64 extras repository?
I can probably work around this by specifying the list of packages needed for the buildroot manually, but I suspect that the group may not exist because some required packages are missing.
They exist, at least on aarch64 and armv5tel (RedSleeve), so it is a virtual certainty they are there on c7 armhf. What you need is: http://ftp.redsleeve.org/pub/el6/6.7/comps.xml and make a dummy empty repository out of it: createrepo -g comps.xml .
Redsleeve makes changes, and that's up to them. The buildsys-build group has always come from EPEL, even on x86_64.
Fair enough, but since mock _package_ that ships with CentOS 7 aarch64 doesn't come with the C7 aarch64 build configuration file, that at least could be considered a bug. The fact is that mock, as shipped with C7 aarch64 doesn't work for building C7 aarch64 packages without a custom config.
Add that path to that repo to your mock repositories, and all will start working just fine.
I've confirmed that httpd-devel and apr-devel are not present in the repository; is this an oversight or is there a problem building them for arm?
Interesting, they are missing on armhf, but they are there on aarch64. :-/
The buildsys-build group isn't available on aarch64 for CentOS either.
That last paragraph was about httpd-devel and apr-devel _packages_, not group definitions. Those don't appear to be there in the armhf repository.
Gordan
Hi Adam,
On 03/04/16 15:12, Adam Bishop wrote:
I just deployed the raspberry pi image for some testing and found a couple of rough edges with the armhfp port.
Mock doesn't work out of the box; it'd be nice if it shipped with a working config file, but after having written one builds are failing because the @buildsys-build yum group is not available. I can probably work around this by specifying the list of packages needed for the buildroot manually, but I suspect that the group may not exist because some required packages are missing.
https://github.com/CentOS/sig-core-bld-seven/blob/master/mock/gcc-x86_64.cfg as an example you can draw from. This is the buildinstall line we use :
config_opts['chroot_setup_cmd'] = 'install bash bzip2 coreutils cpio diffutils system-release findutils gawk gcc gcc-c++ grep gzip info make patch redhat-rpm-config rpm-build sed shadow-utils tar unzip util-linux which xz'
Hope this helps.
I know that there was talk of getting an armhfp config included in the mock shipped, maybe Fabian can work with Johnny to get an updated config in and shipped into Extras/
Shubham: is this something you were working on as well with Lala ?
Regards
Hello Guys,
This is another me too . I have been working with the Bananapi image on my R1 , and have noticed the same patchy repo situation . Lots of packages do not have the devel component . Some of the packages such as dhcp , have the client part but not the server package . Which is strange because when you compile the src rpm all those packages will be built . However it looks like they are not making it into the repo .
Best Regards Milorad
On Mon, Apr 4, 2016 at 12:12 AM, Adam Bishop Adam.Bishop@jisc.ac.uk wrote:
I just deployed the raspberry pi image for some testing and found a couple of rough edges with the armhfp port.
Mock doesn't work out of the box; it'd be nice if it shipped with a working config file, but after having written one builds are failing because the @buildsys-build yum group is not available. I can probably work around this by specifying the list of packages needed for the buildroot manually, but I suspect that the group may not exist because some required packages are missing.
I've confirmed that httpd-devel and apr-devel are not present in the repository; is this an oversight or is there a problem building them for arm?
Regards,
Adam Bishop Systems Development Specialist
gpg: 0x6609D460 t: +44 (0)1235 822 245 xmpp: adamb@jabber.dev.ja.net
jisc.ac.uk
Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.
Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
On 05/04/16 05:25, OM Ugarcina wrote:
Hello Guys,
This is another me too . I have been working with the Bananapi image on my R1 , and have noticed the same patchy repo situation . Lots of packages do not have the devel component . Some of the packages such as dhcp , have the client part but not the server package . Which is strange because when you compile the src rpm all those packages will be built . However it looks like they are not making it into the repo .
Best Regards Milorad
Reason was that even if a package is built, it doesn't mean that it's installable, as there is no "repoclosure" so pkgs that are listed as Requires: for pkgA isn't available built. You'll find the raw output (logs and rpm packages) on : - http://armv7.dev.centos.org/repodir/ (built and available .rpm pkgs) - http://armv7.dev.centos.org/rpmbuild/ (build logs and so where to search for failed pkgs)
Thanks to some people having a look at that recently (thanks a lot Henrik !) and sending patches to either this list, or discussing that in #arm-dev on freenode, we were able to build other pkgs, and slowly then be able to move previously built pkgs to updates repo (as deps were now available)
On 2016-04-05 09:05, Fabian Arrotin wrote:
On 05/04/16 05:25, OM Ugarcina wrote:
Hello Guys,
This is another me too . I have been working with the Bananapi image on my R1 , and have noticed the same patchy repo situation . Lots of packages do not have the devel component . Some of the packages such as dhcp , have the client part but not the server package . Which is strange because when you compile the src rpm all those packages will be built . However it looks like they are not making it into the repo .
Best Regards Milorad
Reason was that even if a package is built, it doesn't mean that it's installable, as there is no "repoclosure" so pkgs that are listed as Requires: for pkgA isn't available built.
Are you sure that this is the problem here? We are talking about -devel packages. It also doesn't explain why rebuilding the package from src.rpm locally fixes the problem.
Gordan
On 5 Apr 2016, at 09:05, Fabian Arrotin arrfab@centos.org wrote:
Reason was that even if a package is built, it doesn't mean that it's installable, as there is no "repoclosure" so pkgs that are listed as Requires: for pkgA isn't available built.
I'm not sure that's what's happened in this instance (or I'm not understanding the problem correctly).
The two missing packages I've found are present in that directory: http://armv7.dev.centos.org/repodir/c71511-pass-1/curl/7.29.0-25.el7.centos/... http://armv7.dev.centos.org/repodir/c71511-pass-1/httpd/2.4.6-40.el7.centos/...
I've successfully installed libcurl-devel and httpd-devel from there without any dependency problems. No problems are noted in the build logs.
Is it possible that some packages have just been omitted when moved from the build server to the public repository?
Regards,
Adam Bishop
gpg: 0x6609D460
jisc.ac.uk
Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.
Jisc Services Limited is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under company number 2881024, VAT number GB 197 0632 86. The registered office is: One Castle Park, Tower Hill, Bristol BS2 0JA. T 0203 697 5800.
-
Adam Bishop -
Fabian Arrotin -
Gordan Bobic -
Jim Perrin -
Karanbir Singh -
OM Ugarcina