I'm trying to do a build on koji and ran into an error during the mock buildroot setup ( http://koji.fedoraproject.org/koji/taskinfo?taskID=6488038 ).
I posted previously on the Fedora devel mailing list but haven't figured it out yet ( https://lists.fedoraproject.org/pipermail/devel/2014-February/195111.html ).
Is this something wrong with koji? Or with the EL6/EPEL packages?
Thanks, Dave
On Thu, 20 Feb 2014 07:54:07 -0700 Dave Johansen davejohansen@gmail.com wrote:
I'm trying to do a build on koji and ran into an error during the mock buildroot setup ( http://koji.fedoraproject.org/koji/taskinfo?taskID=6488038 ).
I posted previously on the Fedora devel mailing list but haven't figured it out yet ( https://lists.fedoraproject.org/pipermail/devel/2014-February/195111.html ).
Is this something wrong with koji? Or with the EL6/EPEL packages?
I answered you on the devel list:
https://lists.fedoraproject.org/pipermail/devel/2014-February/195114.html
Did a more recent build also fail?
Please resubmit.
kevin
On Thu, Feb 20, 2014 at 10:26 AM, Kevin Fenzi kevin@scrye.com wrote:
On Thu, 20 Feb 2014 07:54:07 -0700 Dave Johansen davejohansen@gmail.com wrote:
I'm trying to do a build on koji and ran into an error during the mock buildroot setup ( http://koji.fedoraproject.org/koji/taskinfo?taskID=6488038 ).
I posted previously on the Fedora devel mailing list but haven't figured it out yet (
https://lists.fedoraproject.org/pipermail/devel/2014-February/195111.html
).
Is this something wrong with koji? Or with the EL6/EPEL packages?
I answered you on the devel list:
https://lists.fedoraproject.org/pipermail/devel/2014-February/195114.html
Did a more recent build also fail?
Please resubmit.
Yes, waiting did work for that issue ( https://lists.fedoraproject.org/pipermail/devel/2014-February/195156.html), but this is another issue and appears to that the building of the source .rpm isn't working properly for some reason.
On Thu, Feb 20, 2014 at 7:47 PM, Dave Johansen davejohansen@gmail.comwrote:
Yes, waiting did work for that issue ( https://lists.fedoraproject.org/pipermail/devel/2014-February/195156.html), but this is another issue and appears to that the building of the source .rpm isn't working properly for some reason.
From root.log in the failed build (
http://kojipkgs.fedoraproject.org//work/tasks/8044/6488044/root.log) :
---------- DEBUG util.py:281: http://kojipkgs.fedoraproject.org/repo/rhel/rhel-i386-server-6/getPackage/op...: [Errno 14] HTTP Error 404 - Not Found DEBUG util.py:281: Trying other mirror. DEBUG util.py:281: Error downloading packages: DEBUG util.py:281: openldap-2.4.23-32.el6_4.1.i686: failed to retrieve openldap-2.4.23-32.el6_4.1.i686.rpm from build DEBUG util.py:281: error was [Errno 14] HTTP Error 404 - Not Found DEBUG util.py:371: Child return code was: 1 ----------
It had an error installing openldap. There was actually an openldap release for EL6 the day before this build ran, so it may be possible that whatever mirror/RHN Koji uses was "syncing" when this ran. Pure speculation on my part, not knowing the details of the Koji setup.
Do you get the same error if you attempt a rebuild?
-Jeff
On Fri, Feb 21, 2014 at 7:09 AM, Jeff Sheltren jeff@tag1consulting.comwrote:
On Thu, Feb 20, 2014 at 7:47 PM, Dave Johansen davejohansen@gmail.comwrote:
Yes, waiting did work for that issue ( https://lists.fedoraproject.org/pipermail/devel/2014-February/195156.html), but this is another issue and appears to that the building of the source .rpm isn't working properly for some reason.
From root.log in the failed build ( http://kojipkgs.fedoraproject.org//work/tasks/8044/6488044/root.log) :
DEBUG util.py:281: http://kojipkgs.fedoraproject.org/repo/rhel/rhel-i386-server-6/getPackage/op...: [Errno 14] HTTP Error 404 - Not Found DEBUG util.py:281: Trying other mirror. DEBUG util.py:281: Error downloading packages: DEBUG util.py:281: openldap-2.4.23-32.el6_4.1.i686: failed to retrieve openldap-2.4.23-32.el6_4.1.i686.rpm from build DEBUG util.py:281: error was [Errno 14] HTTP Error 404 - Not Found DEBUG util.py:371: Child return code was: 1
It had an error installing openldap. There was actually an openldap release for EL6 the day before this build ran, so it may be possible that whatever mirror/RHN Koji uses was "syncing" when this ran. Pure speculation on my part, not knowing the details of the Koji setup.
Do you get the same error if you attempt a rebuild?
Doh! The original email in this chain was a copy and paste/stupid user error on my part. No, I no longer get that issue with the llvm build and like Kevin pointed out, just waiting worked.
But I sent two emails this month with very similar titles and I accidentally copied the wrong one in the original email. The correct one is https://lists.fedoraproject.org/pipermail/devel/2014-February/195687.htmland the failed build is http://koji.fedoraproject.org/koji/taskinfo?taskID=6542755 with an issue during the creation of the source rpm. Any ideas on what may be causing this?
Thanks, Dave
On Fri, Feb 21, 2014 at 7:28 AM, Dave Johansen davejohansen@gmail.comwrote:
Doh! The original email in this chain was a copy and paste/stupid user error on my part. No, I no longer get that issue with the llvm build and like Kevin pointed out, just waiting worked.
But I sent two emails this month with very similar titles and I accidentally copied the wrong one in the original email. The correct one is https://lists.fedoraproject.org/pipermail/devel/2014-February/195687.htmland the failed build is http://koji.fedoraproject.org/koji/taskinfo?taskID=6542755 with an issue during the creation of the source rpm. Any ideas on what may be causing this?
I'm not sure why that's failing. I thought it might be a problem with the spec, but I'm able to build cleanly in a local EPEL 6 mock chroot (running CentOS) -- both the spec that failed in the linked build, and the most recent spec.
-Jeff
On Fri, 21 Feb 2014 08:28:24 -0700 Dave Johansen davejohansen@gmail.com wrote:
Doh! The original email in this chain was a copy and paste/stupid user error on my part. No, I no longer get that issue with the llvm build and like Kevin pointed out, just waiting worked.
But I sent two emails this month with very similar titles and I accidentally copied the wrong one in the original email. The correct one is https://lists.fedoraproject.org/pipermail/devel/2014-February/195687.htmland the failed build is http://koji.fedoraproject.org/koji/taskinfo?taskID=6542755 with an issue during the creation of the source rpm. Any ideas on what may be causing this?
Ah, that makes more sense...
So, in that build:
DEBUG util.py:281: Downloading qt-creator-opensource-src-3.0.1.tar.gz DEBUG util.py:281: error: Unable to open /builddir/build/SOURCES/qt-creator-Fedora-privlibs: No such file or directory DEBUG util.py:281: error: query of specfile qt-creator.spec failed, can't parse DEBUG util.py:281: Could not execute sources: Could not parse the spec, exited 1 DEBUG util.py:371: Child return code was: 1
So, you were missing a sources file. It seems after that you commented that out, however the build then failed due to a ppc64 issue.
make[3]: *** [.obj/release-shared/botan.o] Error 1
not sure what is causing that off hand...
kevin
On Fri, Feb 21, 2014 at 9:16 AM, Kevin Fenzi kevin@scrye.com wrote:
On Fri, 21 Feb 2014 08:28:24 -0700 Dave Johansen davejohansen@gmail.com wrote:
Doh! The original email in this chain was a copy and paste/stupid user error on my part. No, I no longer get that issue with the llvm build and like Kevin pointed out, just waiting worked.
But I sent two emails this month with very similar titles and I accidentally copied the wrong one in the original email. The correct one is
https://lists.fedoraproject.org/pipermail/devel/2014-February/195687.htmland
the failed build is http://koji.fedoraproject.org/koji/taskinfo?taskID=6542755 with an issue during the creation of the source rpm. Any ideas on what may be causing this?
Ah, that makes more sense...
So, in that build:
DEBUG util.py:281: Downloading qt-creator-opensource-src-3.0.1.tar.gz DEBUG util.py:281: error: Unable to open /builddir/build/SOURCES/qt-creator-Fedora-privlibs: No such file or directory DEBUG util.py:281: error: query of specfile qt-creator.spec failed, can't parse DEBUG util.py:281: Could not execute sources: Could not parse the spec, exited 1 DEBUG util.py:371: Child return code was: 1
So, you were missing a sources file. It seems after that you commented that out, however the build then failed due to a ppc64 issue.
make[3]: *** [.obj/release-shared/botan.o] Error 1
not sure what is causing that off hand...
The source wasn't missing, but was causing the source rpm to not complete for some reason, so I tried commenting it out to see if that would allow the source rpm to build correctly (which it did), but like you said now it's getting a build error on ppc64. I've never tried building on ppc64 before, so I assumed it would work, but maybe there's something that needs to be worked out there.
On Fri, Feb 21, 2014 at 2:29 PM, Dave Johansen davejohansen@gmail.comwrote:
On Fri, Feb 21, 2014 at 9:16 AM, Kevin Fenzi kevin@scrye.com wrote:
On Fri, 21 Feb 2014 08:28:24 -0700 Dave Johansen davejohansen@gmail.com wrote:
Doh! The original email in this chain was a copy and paste/stupid user error on my part. No, I no longer get that issue with the llvm build and like Kevin pointed out, just waiting worked.
But I sent two emails this month with very similar titles and I accidentally copied the wrong one in the original email. The correct one is
https://lists.fedoraproject.org/pipermail/devel/2014-February/195687.htmland
the failed build is http://koji.fedoraproject.org/koji/taskinfo?taskID=6542755 with an issue during the creation of the source rpm. Any ideas on what may be causing this?
Ah, that makes more sense...
So, in that build:
DEBUG util.py:281: Downloading qt-creator-opensource-src-3.0.1.tar.gz DEBUG util.py:281: error: Unable to open /builddir/build/SOURCES/qt-creator-Fedora-privlibs: No such file or directory DEBUG util.py:281: error: query of specfile qt-creator.spec failed, can't parse DEBUG util.py:281: Could not execute sources: Could not parse the spec, exited 1 DEBUG util.py:371: Child return code was: 1
So, you were missing a sources file. It seems after that you commented that out, however the build then failed due to a ppc64 issue.
make[3]: *** [.obj/release-shared/botan.o] Error 1
not sure what is causing that off hand...
The source wasn't missing, but was causing the source rpm to not complete for some reason, so I tried commenting it out to see if that would allow the source rpm to build correctly (which it did), but like you said now it's getting a build error on ppc64. I've never tried building on ppc64 before, so I assumed it would work, but maybe there's something that needs to be worked out there.
Ok, I did some scratch builds to test a few things and here are my questions.
1) There's an issue with building on ppc64 for el6 ( http://koji.fedoraproject.org/koji/taskinfo?taskID=6558674 ). I would like to fix this, but don't have the time to look into why the include of cpuid.h is causing a problem on ppc64, so unless someone knows the solution, then I'm just going to exclude it for the time being.
2) The source rpm with the same files that are in the git branch for el6 builds just fine ( http://koji.fedoraproject.org/koji/taskinfo?taskID=6559811 ), so is this a koji issue I should file a bug against? Or should I just exclude the privlibs just to use that on el6 for the time being?
Thanks, Dave
epel-devel@lists.fedoraproject.org
-
Dave Johansen -
Jeff Sheltren -
Kevin Fenzi