build error in koji
Hey there.
I got my own koji server up and running, but builds seem to be failing. Here's the errors that I'm seeing: 19 build (dist-foo, less-436-2.el5.src.rpm): open (kojibuilder1) -> FAILED: BuildrootError: could not init mock buildroot, mock exited with status 20; see root.log for more information The root.log shows: INFO backend.py:747: Mock Version: 1.1.6 DEBUG backend.py:242: rootdir = /var/lib/mock/dist-foo-build-2-5/root/ DEBUG backend.py:243: resultdir = /var/lib/mock/dist-foo-build-2-5/result DEBUG backend.py:249: create skeleton dirs DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/lib/rpm DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/lib/rpm DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/lib/yum DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/lib/yum DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/lib/dbus DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/lib/dbus DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/log DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/log DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/lock/rpm DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/lock/rpm DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/etc/rpm DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/etc/rpm DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/tmp DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/tmp DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/var/tmp DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/var/tmp DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/etc/yum.repos.d DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/etc/yum.repos.d DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/etc/yum DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/etc/yum DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/proc DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/proc DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/sys DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/sys DEBUG backend.py:267: touch required files DEBUG util.py:68: touching file: /var/lib/mock/dist-foo-build-2-5/root/etc/mtab DEBUG util.py:68: touching file: /var/lib/mock/dist-foo-build-2-5/root/etc/fstab DEBUG util.py:68: touching file: /var/lib/mock/dist-foo-build-2-5/root/var/log/yum.log DEBUG backend.py:275: configure yum DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/etc DEBUG util.py:82: remove tree: /var/lib/mock/dist-foo-build-2-5/root/dev DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/dev/pts DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/dev/pts DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-foo-build-2-5/root/dev/shm DEBUG util.py:60: creating dir: /var/lib/mock/dist-foo-build-2-5/root/dev/shm DEBUG backend.py:647: mount -n -t proc mock_chroot_proc /var/lib/mock/dist-foo-build-2-5/root/proc DEBUG util.py:301: Executing command: mount -n -t proc mock_chroot_proc /var/lib/mock/dist-foo-build-2-5/root/proc DEBUG util.py:340: Child returncode was: 0 DEBUG backend.py:647: mount -n -t sysfs mock_chroot_sysfs /var/lib/mock/dist-foo-build-2-5/root/sys DEBUG util.py:301: Executing command: mount -n -t sysfs mock_chroot_sysfs /var/lib/mock/dist-foo-build-2-5/root/sys DEBUG util.py:340: Child returncode was: 0 DEBUG backend.py:647: mount -n -t devpts -o gid=5,mode=0620,ptmxmode=0666,newinstance mock_chroot_devpts /var/lib/mock/dist-foo-build-2-5/root/dev/pts DEBUG util.py:301: Executing command: mount -n -t devpts -o gid=5,mode=0620,ptmxmode=0666,newinstance mock_chroot_devpts /var/lib/mock/dist-foo-build-2-5/root/dev/pts DEBUG util.py:340: Child returncode was: 0 DEBUG backend.py:647: mount -n -t tmpfs mock_chroot_shmfs /var/lib/mock/dist-foo-build-2-5/root/dev/shm DEBUG util.py:301: Executing command: mount -n -t tmpfs mock_chroot_shmfs /var/lib/mock/dist-foo-build-2-5/root/dev/shm DEBUG util.py:340: Child returncode was: 0 DEBUG backend.py:680: /usr/bin/yum --installroot /var/lib/mock/dist-foo-build-2-5/root/ groupinstall build DEBUG util.py:301: Executing command: /usr/bin/yum --installroot /var/lib/mock/dist-foo-build-2-5/root/ groupinstall build DEBUG util.py:340: Child returncode was: 0 DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-foo-build-2-5/root/dev/shm DEBUG util.py:340: Child returncode was: 0 DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-foo-build-2-5/root/dev/pts DEBUG util.py:340: Child returncode was: 0 DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-foo-build-2-5/root/sys DEBUG util.py:340: Child returncode was: 0 DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-foo-build-2-5/root/proc DEBUG util.py:340: Child returncode was: 0 DEBUG util.py:102: kill orphans - Steve Webb -- Steve Webb | System Administrator Beatport | Music for DJ's ------------------------------------------ 2399 Blake Street, Suite 170 Denver, Colorado USA 80205 tel: +1.720.932.9103 fax: +1.720.932.9104 noc: +1.303.565.2710 mobile: +1.303.564.4269 -- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys |
build error in koji
On 11/09/2010 03:01 PM, steve.webb@beatport.com wrote:
> Hey there. > > I got my own koji server up and running, but builds seem to be failing. > Here's the errors that I'm seeing: > > 19 build (dist-foo, less-436-2.el5.src.rpm): open (kojibuilder1) -> > FAILED: BuildrootError: could not init mock buildroot, mock exited with > status 20; see root.log for more information > > The root.log shows: ... > DEBUG backend.py:680: /usr/bin/yum --installroot /var/lib/mock/dist-foo-build-2-5/root/ groupinstall build > DEBUG util.py:301: Executing command: /usr/bin/yum --installroot /var/lib/mock/dist-foo-build-2-5/root/ groupinstall build > DEBUG util.py:340: Child returncode was: 0 Normally at this point you'd see some yum install output, but your log has none. Is your build group empty? (Use koji list-groups <build tag> to check) -- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys |
build error in koji
On Tue, 9 Nov 2010, Mike McLean wrote:
> On 11/09/2010 03:01 PM, steve.webb@beatport.com wrote: >> The root.log shows: > ... >> DEBUG backend.py:680: /usr/bin/yum --installroot /var/lib/mock/dist-foo-build-2-5/root/ groupinstall build >> DEBUG util.py:301: Executing command: /usr/bin/yum --installroot /var/lib/mock/dist-foo-build-2-5/root/ groupinstall build >> DEBUG util.py:340: Child returncode was: 0 > > Normally at this point you'd see some yum install output, but your log > has none. Is your build group empty? (Use koji list-groups <build tag> > to check) [kojiadmin@bpkojipoc001 ~]$ koji list-groups dist-foo-build build [dist-foo-build] less-436-2.el5.src.rpm: None, default [dist-foo-build] lftp-3.7.11-4.el5.src.rpm: None, default [dist-foo-build] srpm-build [dist-foo-build] [kojiadmin@bpkojipoc001 ~]$ I'm kind of at a loss as to how to populate the koji system to get builds started, so this may not be the right way to do things. Is there a howto somewhere that shows how to populate koji with some initial data and do a sample build? The howtos at http://fedoraproject.org/wiki/Koji/ExternalRepoServerBootstrap don't really go into many specifics and Google has been less than helpful. - Steve -- Steve Webb | System Administrator Beatport | Music for DJ's ------------------------------------------ 2399 Blake Street, Suite 170 Denver, Colorado USA 80205 tel: +1.720.932.9103 fax: +1.720.932.9104 noc: +1.303.565.2710 mobile: +1.303.564.4269 -- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys |
build error in koji
On 11/10/2010 10:37 AM, steve.webb@beatport.com wrote:
> [kojiadmin@bpkojipoc001 ~]$ koji list-groups dist-foo-build > build [dist-foo-build] > less-436-2.el5.src.rpm: None, default [dist-foo-build] > lftp-3.7.11-4.el5.src.rpm: None, default [dist-foo-build] > srpm-build [dist-foo-build] > [kojiadmin@bpkojipoc001 ~]$ The build group is generally not quite this compact. Also, you should using just the name part of the rpm (e.g. less and lftp). Your data is causing yum to look for rpms whose package names are 'less-436-2.el5.src.rpm' and 'lftp-3.7.11-4.el5.src.rpm'. This matches nothing, so yum installs nothing. You might look at the groups data on koji.fedoraproject.org to get started. For example: $ koji list-groups dist-f14-build $ koji list-groups dist-5E-epel-build Exactly what you put in there depends on your building needs. Just keep in mind that more buildroot content makes for slower buildroot generation. -- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys |
build error in koji
Ahh, I added the base packages like you mentioned and I was able to build
my first package! Woohoo! Thanks! [kojiadmin@bpkojipoc001 ~]$ koji build dist-foo --scratch lftp-3.7.11-4.el5.src.rpm Uploading srpm: lftp-3.7.11-4.el5.src.rpm [====================================] 100% 00:00:01 1.44 MiB 1.33 MiB/sec Created task: 86 Task info: http://bplkojipoc001.co0.nar.beatportcorp.net/koji/taskinfo?taskID=86 Watching tasks (this may be safely interrupted)... 86 build (dist-foo, lftp-3.7.11-4.el5.src.rpm): free 86 build (dist-foo, lftp-3.7.11-4.el5.src.rpm): free -> open (kojibuilder1) 88 buildArch (lftp-3.7.11-4.el5.src.rpm, i386): free 87 buildArch (lftp-3.7.11-4.el5.src.rpm, x86_64): free 88 buildArch (lftp-3.7.11-4.el5.src.rpm, i386): free -> open (kojibuilder1) 87 buildArch (lftp-3.7.11-4.el5.src.rpm, x86_64): free -> open (kojibuilder1) 87 buildArch (lftp-3.7.11-4.el5.src.rpm, x86_64): open (kojibuilder1) -> closed 0 free 2 open 1 done 0 failed 88 buildArch (lftp-3.7.11-4.el5.src.rpm, i386): open (kojibuilder1) -> closed 0 free 1 open 2 done 0 failed 86 build (dist-foo, lftp-3.7.11-4.el5.src.rpm): open (kojibuilder1) -> closed 0 free 0 open 3 done 0 failed 86 build (dist-foo, lftp-3.7.11-4.el5.src.rpm) completed successfully - Steve Webb On Wed, 10 Nov 2010, Mike McLean wrote: > On 11/10/2010 10:37 AM, steve.webb@beatport.com wrote: >> [kojiadmin@bpkojipoc001 ~]$ koji list-groups dist-foo-build >> build [dist-foo-build] >> less-436-2.el5.src.rpm: None, default [dist-foo-build] >> lftp-3.7.11-4.el5.src.rpm: None, default [dist-foo-build] >> srpm-build [dist-foo-build] >> [kojiadmin@bpkojipoc001 ~]$ > > The build group is generally not quite this compact. > Also, you should using just the name part of the rpm (e.g. less and > lftp). Your data is causing yum to look for rpms whose package names are > 'less-436-2.el5.src.rpm' and 'lftp-3.7.11-4.el5.src.rpm'. This matches > nothing, so yum installs nothing. > > You might look at the groups data on koji.fedoraproject.org to get > started. For example: > $ koji list-groups dist-f14-build > $ koji list-groups dist-5E-epel-build > > Exactly what you put in there depends on your building needs. Just keep > in mind that more buildroot content makes for slower buildroot generation. > > -- > buildsys mailing list > buildsys@lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/buildsys > -- Steve Webb | System Administrator Beatport | Music for DJ's ------------------------------------------ 2399 Blake Street, Suite 170 Denver, Colorado USA 80205 tel: +1.720.932.9103 fax: +1.720.932.9104 noc: +1.303.565.2710 mobile: +1.303.564.4269 -- buildsys mailing list buildsys@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/buildsys |
| All times are GMT. The time now is 06:54 AM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.