Hello fellow Fedorans.
I'm trying to build a new package for Fawkes which has just passed review. It build fine on f13/f14/f15, but it fails on el5/el6 with an error that seems to be related to the build system, not to the actual package.
Koji Builds: https://koji.fedoraproject.org/koji/taskinfo?taskID=2580299 https://koji.fedoraproject.org/koji/taskinfo?taskID=2580290 Git: http://pkgs.fedoraproject.org/gitweb/?p=fawkes.git
If you look into the root log, you can find the following errors: DEBUG util.py:82: remove tree: /var/lib/mock/dist-6E-epel-build-919001-135356/root/builddir DEBUG util.py:294: Executing command: ['/usr/sbin/userdel', '-r', 'mockbuild'] DEBUG util.py:333: Child returncode was: 6 DEBUG util.py:294: Executing command: ['/usr/sbin/groupdel', 'mockbuild'] DEBUG util.py:260: groupdel: group 'mockbuild' does not exist DEBUG util.py:333: Child returncode was: 6
and
DEBUG util.py:82: remove tree: /var/lib/mock/dist-5E-epel-build-919006-135362/root/builddir DEBUG util.py:294: Executing command: ['/usr/sbin/userdel', '-r', 'mockbuild'] DEBUG util.py:260: userdel: error removing directory /builddir DEBUG util.py:333: Child returncode was: 12 DEBUG util.py:294: Executing command: ['/usr/sbin/groupdel', 'mockbuild'] DEBUG util.py:260: groupdel: group mockbuild does not exist DEBUG util.py:333: Child returncode was: 6
I had seen this once before two weeks ago or so for another package. Back then a simple resubmission worked and did the trick. But not this time, I resubmitted the el5 job twice, everytime the same error.
Any idea what is causing this, or how it can be solved? Should I file a bug (against what, which tracker)?
Tim
On Fri, 05 Nov 2010 14:47:38 -0400 Tim Niemueller tim@niemueller.de wrote:
Hello fellow Fedorans.
I'm trying to build a new package for Fawkes which has just passed review. It build fine on f13/f14/f15, but it fails on el5/el6 with an error that seems to be related to the build system, not to the actual package.
...snip...
I had seen this once before two weeks ago or so for another package. Back then a simple resubmission worked and did the trick. But not this time, I resubmitted the el5 job twice, everytime the same error.
Any idea what is causing this, or how it can be solved? Should I file a bug (against what, which tracker)?
The userdel seems unrelated to the real problem:
DEBUG util.py:260: No Package Found for gearbox-devel >= 9.11 DEBUG util.py:260: 0:urg-devel-0.8.7-2.el5.x86_64 DEBUG util.py:260: 0:glibmm24-devel-2.12.10-1.el5.x86_64 DEBUG util.py:260: 0:avahi-devel-0.6.16-9.el5_5.x86_64 DEBUG util.py:260: 0:libkni3-devel-3.9.2-12.el5.x86_64 DEBUG util.py:260: No Package Found for libdaemon-devel >= 0.14 DEBUG util.py:260: 0:libjpeg-devel-6b-37.x86_64 DEBUG util.py:260: 0:gtkmm24-devel-2.10.10-1.el5.x86_64 DEBUG util.py:260: No Package Found for file-devel DEBUG util.py:260: 0:libglademm24-devel-2.6.3-3.el5.x86_64 DEBUG util.py:260: 0:lua-devel-5.1.4-4.el5.x86_64 DEBUG util.py:260: No Package Found for xmlrpc-c-devel DEBUG util.py:260: No Package Found for libdc1394-devel >= 2.1 DEBUG util.py:260: No Package Found for player-devel >= 3.0 DEBUG util.py:260: 0:gcc-c++-4.1.2-48.el5.x86_64 DEBUG util.py:260: No Package Found for graphviz-devel >= 2.22 DEBUG util.py:260: 0:SDL-devel-1.2.10-8.el5.x86_64 DEBUG util.py:260: 0:libmicrohttpd-devel-0.4.6-1.el5.x86_64 DEBUG util.py:260: 0:asciidoc-8.1.0-1.el5.noarch DEBUG util.py:260: 0:gconfmm26-devel-2.14.2-1.el5.x86_64 DEBUG util.py:260: 0:flite-devel-1.3-11.el5.x86_64 DEBUG util.py:260: 0:desktop-file-utils-0.10-7.x86_64 DEBUG util.py:260: No Package Found for readline-devel >= 6.1 DEBUG util.py:260: 0:opencv-devel-1.0.0-3.el5.x86_64 DEBUG util.py:260: 1:doxygen-1.4.7-1.1.x86_64 DEBUG util.py:260: 0:sqlite-devel-3.3.6-5.x86_64 DEBUG util.py:260: 2:libpng-devel-1.2.10-7.1.el5_5.3.x86_64 DEBUG util.py:260: 0:cairomm-1.2.4-1.el5.x86_64 DEBUG util.py:260: No Package Found for libxml++-devel >= 2.26 DEBUG util.py:260: No Package Found for tolua++-devel DEBUG util.py:260: 0:openssl-devel-0.9.8e-12.el5_4.6.x86_64 DEBUG util.py:260: 0:kernel-headers-2.6.18-194.17.4.el5.x86_64
All those "No Package Found" issues need to be fixed. ;) Either by branching the needed packages into EPEL, or fixing the package to not need them or need the available versions in EPEL.
RHEL5 is pretty old at this point, you cannot assume that something that works fine on fedora builds and works fine in epel.
kevin
On 05.11.2010 14:52, Kevin Fenzi wrote:
The userdel seems unrelated to the real problem:
DEBUG util.py:260: No Package Found for gearbox-devel>= 9.11
[...] Thanks, missed those. I wish it could be made more clear which state failed. I wonder why it says return code 0, although this failed?
All those "No Package Found" issues need to be fixed. ;) Either by branching the needed packages into EPEL, or fixing the package to not need them or need the available versions in EPEL.
RHEL5 is pretty old at this point, you cannot assume that something that works fine on fedora builds and works fine in epel.
It can be built on EL5. We have a CentOS 5 build slave building new revisions checked into the git master. By reducing the BuildRequires I can produce a basic version which allows for running the basic stuff.
Thanks, Tim
Some more question related to el6:
When will packages appear in el6? I maintain some of the dependencies for el5, but they are not in el6.
Do I just need to build them? Will there be or should there have been a mass rebuild? Do I need to file a koji update?
Thanks again, Tim
On Fri, 05 Nov 2010 15:08:40 -0400 Tim Niemueller tim@niemueller.de wrote:
Some more question related to el6:
When will packages appear in el6? I maintain some of the dependencies for el5, but they are not in el6.
They will appear when someone branches them and builds them, or when the maintainers of the already existing branch builds them. ;)
Basically we branched everything that was in epel5 except for those things that will be in RHEL6. It's then up to the maintainers to build and maintain them.
What packages? You should be able to look in pkgdb and see if they already have a branch or not.
Do I just need to build them? Will there be or should there have been a mass rebuild? Do I need to file a koji update?
If they aren't already branched or in rhel6, yeah, just make a scm request on the package review for the package to branch for el6. If they are, ping the maintainer to do a build?
No updates are currently needed. It's in 'beta' mode, which is like rawhide, everything pushes out every day or two. Once rhel6 comes out we will go to bodhi/updates, etc.
kevin
On 5 November 2010 19:47, Tim Niemueller tim@niemueller.de wrote:
Koji Builds: https://koji.fedoraproject.org/koji/taskinfo?taskID=2580299
That then points to
https://koji.fedoraproject.org/koji/taskinfo?taskID=2580322
Note the Result : BuildError: error building package (arch noarch), mock exited with status 10; see root.log for more information
which can be found lower down http://koji.fedoraproject.org/koji/getfile?taskID=2580322&name=root.log
... DEBUG util.py:260: No Package Found for libdaemon-devel >= 0.14 DEBUG util.py:260: 0:libjpeg-devel-6b-37.x86_64 DEBUG util.py:260: 0:gtkmm24-devel-2.10.10-1.el5.x86_64 DEBUG util.py:260: No Package Found for file-devel ...
Not all Fedora packages/versions are available in RHEL/EPEL and some have different names due to the age of RHEL5
Mark