So as you may have seen, I've been playing with the community build system today. The authentication and certificates all seem to have worked flawlessly, so thank you!
But now I'm running into some errors with the build and I'm not sure how to debug them.
In both cases, if I'm reading this right, the 64-bit build fails with this:
DEBUG util.py:283: Error: No Package found for /usr/include/gnu/stubs-32.h
In both cases, the rpm builds just fine on my dev box.
The file in question is owned by glibc-devel; and "rpm -q --whatprovides" finds it just fine.
Any ideas?
Below are the commands I've run along with links to the cbs builds. The first is a development branch (but is publicly available on github). The second is the one currently available in the xen4centos repos.
git repo can be found at https://github.com/gwd/sig-virt-xen.git
git checkout out/update-4.4.1-rc1-ee81dda-RFC rpmbuild --define "_topdir $PWD" -bs SPECS/xen.spec koji build --scratch bananas6-el6 SRPMS/xen-4.4.1-0.1rc1.el6.src.rpm https://cbs.centos.org/koji/taskinfo?taskID=376
git checkout xen rpmbuild --define "_topdir $PWD" -bs SPECS/xen.spec koji build --scratch bananas6-el6 SRPMS/xen-4.2.4-30.el6.src.rpm https://cbs.centos.org/koji/taskinfo?taskID=380
Thanks!
-George
On 09/02/2014 05:48 PM, George Dunlap wrote:
In both cases, if I'm reading this right, the 64-bit build fails with this:
DEBUG util.py:283: Error: No Package found for /usr/include/gnu/stubs-32.h
this is likely a mock issue - it just needs glibc.i686 to be available in the x86_64 buildroots.
Hi,
I had the same issue. I recompiled the following x86_64 package to solve this problem: http://koji.fedoraproject.org/koji/packageinfo?packageID=1160
It is an x86_64 only package, which provides these basic files (like stubs-32.h).
Hope it helps, Peter Bojtoss
----- Eredeti üzenet -----
Feladó: "Karanbir Singh" mail-lists@karan.org Címzett: centos-devel@centos.org Elküldött üzenetek: Kedd, 2014. Szeptember 2. 18:52:30 Tárgy: Re: [CentOS-devel] Debugging CBS build failure
On 09/02/2014 05:48 PM, George Dunlap wrote:
In both cases, if I'm reading this right, the 64-bit build fails with this:
DEBUG util.py:283: Error: No Package found for /usr/include/gnu/stubs-32.h
this is likely a mock issue - it just needs glibc.i686 to be available in the x86_64 buildroots.
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Tue, Sep 2, 2014 at 5:52 PM, Karanbir Singh mail-lists@karan.org wrote:
On 09/02/2014 05:48 PM, George Dunlap wrote:
In both cases, if I'm reading this right, the 64-bit build fails with this:
DEBUG util.py:283: Error: No Package found for /usr/include/gnu/stubs-32.h
this is likely a mock issue - it just needs glibc.i686 to be available in the x86_64 buildroots.
So we either need to make mock search for i686 RPMs available as a fall-back if we can't find a package in x86_64; or, as Bojtos says, we need to have a special glibc32 package for 64-bit. Which would be the preferred approach, do you think?
-George
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi All,
On 09/03/2014 03:11 PM, George Dunlap wrote:
On Tue, Sep 2, 2014 at 5:52 PM, Karanbir Singh mail-lists@karan.org wrote:
On 09/02/2014 05:48 PM, George Dunlap wrote:
In both cases, if I'm reading this right, the 64-bit build fails with this:
DEBUG util.py:283: Error: No Package found for /usr/include/gnu/stubs-32.h
this is likely a mock issue - it just needs glibc.i686 to be available in the x86_64 buildroots.
So we either need to make mock search for i686 RPMs available as a fall-back if we can't find a package in x86_64; or, as Bojtos says, we need to have a special glibc32 package for 64-bit. Which would be the preferred approach, do you think?
I used the EPEL approach and added the glibc32 package to our buildsys6 tag.
Please retry !
cheers, Thomas.
On 09/03/2014 08:54 AM, Thomas Oulevey wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi All,
On 09/03/2014 03:11 PM, George Dunlap wrote:
On Tue, Sep 2, 2014 at 5:52 PM, Karanbir Singh mail-lists@karan.org wrote:
On 09/02/2014 05:48 PM, George Dunlap wrote:
In both cases, if I'm reading this right, the 64-bit build fails with this:
DEBUG util.py:283: Error: No Package found for /usr/include/gnu/stubs-32.h
this is likely a mock issue - it just needs glibc.i686 to be available in the x86_64 buildroots.
So we either need to make mock search for i686 RPMs available as a fall-back if we can't find a package in x86_64; or, as Bojtos says, we need to have a special glibc32 package for 64-bit. Which would be the preferred approach, do you think?
I used the EPEL approach and added the glibc32 package to our buildsys6 tag.
Please retry !
cheers, Thomas. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux)
iQEcBAEBAgAGBQJUBx2bAAoJEH2Wn86OP8NiVxUH/1j5w8E2Lt+6M7wqLexju4+1 4rnJWAEabkfI0a5sFtiqICF6Mt2I4+/X4xvjeCXKYgKEQj7/qzAFke5scQOwFA4G TCywSYSGg7yFYPOSvgvWrs0oOLKKnR0vDqUkc5C8lgoM4T6aWnsM10CAHwvjNW1E cH+CK5t8V8AJGeb6s7WgXCQqCsgbpzeVdiAjxrDwu+1+X4NUUUxr6z6zAQ6bfksq rThmsHB191vrFrC51P0zZu9hz3IpWTgFmsSa5MPpW8cPyWm7JGiNehRhsDxTsgrG HGIZctSfGuV1azyGTdTFFWPUTzIPeZ6nrTaX4ad5KVqFSW7Qq0qaB9JADxGrX7M= =6nrn -----END PGP SIGNATURE----- _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
Or the solution from Koji upstream Mike merged back in May:
https://git.fedorahosted.org/cgit/koji/commit/?id=794abb71b1cd5662354475e2be...