koji mock failing
by steve.webb＠beatport.com
build.log:
Mock Version: 1.1.6
Mock Version: 1.1.6
ENTER do(['bash', '--login', '-c', 'rpmbuild -bs --target x86_64 --nodeps builddir/build/SPECS/php.spec'], False, '/var/lib/mock/dist-EL5-beatport-build-20-2115/root/', None, 86400, True, 0, 498, 498, None, logger=<mock.trace_decorator.getLog object at 0x1f8ea50>)
Executing command: ['bash', '--login', '-c', 'rpmbuild -bs --target x86_64 --nodeps builddir/build/SPECS/php.spec']
error: /builddir/build/SPECS/php.spec:29: parseExpressionBoolean returns -1
error: Name field must be present in package: (main package)
error: Version field must be present in package: (main package)
error: Release field must be present in package: (main package)
error: Summary field must be present in package: (main package)
error: Group field must be present in package: (main package)
error: License field must be present in package: (main package)
Building target platforms: x86_64
Building for target x86_64
Child returncode was: 1
EXCEPTION: Command failed. See logs for output.
# ['bash', '--login', '-c', 'rpmbuild -bs --target x86_64 --nodeps builddir/build/SPECS/php.spec']
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/mock/trace_decorator.py", line 70, in trace
result = func(*args, **kw)
File "/usr/lib/python2.7/site-packages/mock/util.py", line 345, in do
raise mock.exception.Error, ("Command failed. See logs for output.\n # %s" % (command,), child.returncode)
Error: Command failed. See logs for output.
# ['bash', '--login', '-c', 'rpmbuild -bs --target x86_64 --nodeps builddir/build/SPECS/php.spec']
LEAVE do --> EXCEPTION RAISED
root.log:
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:102: kill orphans
INFO backend.py:747: Mock Version: 1.1.6
DEBUG backend.py:242: rootdir = /var/lib/mock/dist-EL5-beatport-build-20-2115/root/
DEBUG backend.py:243: resultdir = /var/lib/mock/dist-EL5-beatport-build-20-2115/result
DEBUG backend.py:249: create skeleton dirs
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/var/lib/rpm
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/var/lib/yum
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/var/lib/dbus
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/var/log
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/var/lock/rpm
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/etc/rpm
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/tmp
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/var/tmp
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/etc/yum.repos.d
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/etc/yum
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/sys
DEBUG backend.py:267: touch required files
DEBUG util.py:68: touching file: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/etc/mtab
DEBUG util.py:68: touching file: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/etc/fstab
DEBUG util.py:68: touching file: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/var/log/yum.log
DEBUG backend.py:275: configure yum
DEBUG util.py:82: remove tree: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/pts
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/pts
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/shm
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/shm
DEBUG backend.py:647: mount -n -t proc mock_chroot_proc /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc
DEBUG util.py:301: Executing command: mount -n -t proc mock_chroot_proc /var/lib/mock/dist-EL5-beatport-build-20-2115/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-EL5-beatport-build-20-2115/root/sys
DEBUG util.py:301: Executing command: mount -n -t sysfs mock_chroot_sysfs /var/lib/mock/dist-EL5-beatport-build-20-2115/root/sys
DEBUG util.py:340: Child returncode was: 0
DEBUG backend.py:647: mount -n --bind /tmp/mock-selinux-pluginuI8o0W /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc/filesystems
DEBUG util.py:301: Executing command: mount -n --bind /tmp/mock-selinux-pluginuI8o0W /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc/filesystems
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-EL5-beatport-build-20-2115/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-EL5-beatport-build-20-2115/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-EL5-beatport-build-20-2115/root/dev/shm
DEBUG util.py:301: Executing command: mount -n -t tmpfs mock_chroot_shmfs /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/shm
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:82: remove tree: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir
DEBUG util.py:301: Executing command: ['/usr/sbin/userdel', '-r', 'mockbuild']
DEBUG util.py:267: userdel: error removing directory /builddir
DEBUG util.py:340: Child returncode was: 12
DEBUG util.py:301: Executing command: ['/usr/sbin/groupdel', 'mockbuild']
DEBUG util.py:267: groupdel: group mockbuild does not exist
DEBUG util.py:340: Child returncode was: 6
DEBUG util.py:301: Executing command: ['/usr/sbin/groupadd', '-g', '498', 'mockbuild']
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: /usr/sbin/useradd -o -m -u 498 -g 498 -d /builddir -n mockbuild
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/RPMS
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/RPMS
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/SRPMS
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/SRPMS
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/SOURCES
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/SOURCES
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/SPECS
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/SPECS
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/BUILD
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/BUILD
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/BUILDROOT
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/BUILDROOT
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/originals
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/builddir/build/originals
DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/shm
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/pts
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc/filesystems
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-EL5-beatport-build-20-2115/root/sys
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:82: remove tree: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/pts
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/pts
DEBUG util.py:57: ensuring that dir exists: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/shm
DEBUG util.py:60: creating dir: /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/shm
DEBUG backend.py:647: mount -n -t proc mock_chroot_proc /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc
DEBUG util.py:301: Executing command: mount -n -t proc mock_chroot_proc /var/lib/mock/dist-EL5-beatport-build-20-2115/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-EL5-beatport-build-20-2115/root/sys
DEBUG util.py:301: Executing command: mount -n -t sysfs mock_chroot_sysfs /var/lib/mock/dist-EL5-beatport-build-20-2115/root/sys
DEBUG util.py:340: Child returncode was: 0
DEBUG backend.py:647: mount -n --bind /tmp/mock-selinux-pluginuI8o0W /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc/filesystems
DEBUG util.py:301: Executing command: mount -n --bind /tmp/mock-selinux-pluginuI8o0W /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc/filesystems
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-EL5-beatport-build-20-2115/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-EL5-beatport-build-20-2115/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-EL5-beatport-build-20-2115/root/dev/shm
DEBUG util.py:301: Executing command: mount -n -t tmpfs mock_chroot_shmfs /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/shm
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: ['rpm', '-Uvh', '--nodeps', '/builddir/build/originals/php-5.3.3-3.el5.beatport.src.rpm']
DEBUG util.py:267: error: cannot open Packages index using db3 - Invalid argument (22)
DEBUG util.py:267: error: cannot open Packages database in /var/lib/rpm
DEBUG util.py:267: warning: /builddir/build/originals/php-5.3.3-3.el5.beatport.src.rpm: Header V4 DSA signature: NOKEY, key ID 08ba6a4f
DEBUG util.py:267: error: cannot open Packages database in /var/lib/rpm
DEBUG util.py:267: php ##################################################
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/shm
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-EL5-beatport-build-20-2115/root/dev/pts
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc/filesystems
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-EL5-beatport-build-20-2115/root/sys
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:301: Executing command: umount -n /var/lib/mock/dist-EL5-beatport-build-20-2115/root/proc
DEBUG util.py:340: Child returncode was: 0
DEBUG util.py:102: kill orphans
state.log:
2011-01-24 09:45:38,073 - Mock Version: 1.1.6
2011-01-24 09:45:38,088 - State Changed: running yum
2011-01-24 09:46:52,873 - Mock Version: 1.1.6
2011-01-24 09:46:52,884 - State Changed: running yum
2011-01-24 09:46:53,139 - State Changed: setup
- Steve
--
Steve Webb | System Administrator
Beatport | Play With Music
------------------------------------------
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
13 years, 3 months
<class 'pg.DatabaseError'>: error 'ERROR: relation "win_builds" does not exist
by steve.webb＠beatport.com
When I click on one of my packages in the web interface, I'm getting this
python backtrace:
An error has occurred while processing your request.
Fault: <Fault 1: '<class \'pg.DatabaseError\'>: error \'ERROR: relation "win_builds" does not exist\nLINE 3: FROM win_builds\n ^\n\' in \'\nSELECT build_id, platform\n FROM win_builds\n\n WHERE (build_id = 1)\n \n\n \n\''>
Traceback (most recent call last):
File "/usr/share/koji-web/lib/kojiweb/publisher.py", line 16, in publish_object
return old_publish_object(req, object)
File "/usr/lib64/python2.7/site-packages/mod_python/publisher.py", line 425, in publish_object
return publish_object(req,util.apply_fs_data(object, req.form, req=req))
File "/usr/lib64/python2.7/site-packages/mod_python/util.py", line 554, in apply_fs_data
return object(**args)
File "/usr/share/koji-web/scripts/index.py", line 1040, in buildinfo
winbuild = server.getWinBuild(buildID)
File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 1510, in __call__
return self.__func(self.__name,args,opts)
File "/usr/lib/python2.7/site-packages/koji/__init__.py", line 1761, in _callMethod
raise err
Fault: <Fault 1: '<class \'pg.DatabaseError\'>: error \'ERROR: relation "win_builds" does not exist\nLINE 3: FROM win_builds\n ^\n\' in \'\nSELECT build_id, platform\n FROM win_builds\n\n WHERE (build_id = 1)\n \n\n \n\''>
--
Steve Webb | System Administrator
Beatport | Play With Music
------------------------------------------
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
13 years, 3 months
New koji install - having issues with mock initial packages
by steve.webb＠beatport.com
I think that I'm having issues with the initial package list for mock.
New koji install (Thanks Mike, BTW).
I added some packages and groups:
koji add-group-pkg dist-EL5-beatport-build build bash bzip2 coreutils cpio diffutils findutils gawk gcc gcc-c++ grep gzip info make patch redhat-rpm-config centos-release rpm-build sed shadow-utils tar unzip unil-linux-ng which
koji add-group-pkg dist-EL5-beatport-build srpm-build bash buildsys-macros cvs fedpkg gnupg make redhat-release redhat-rpm-config rpm-build
koji add-pkg --owner swebb dist-EL5-beatport bash bzip2 coreutils cpio diffutils findutils gawk gcc gcc-c++ grep gzip info make patch redhat-rpm-config centos-release rpm-build sed shadow-utils tar unzip unil-linux-ng which
... but I think that I'm missing something.
Here's my mock_output.log:
INFO: mock.py version 1.1.6 starting...
State Changed: init plugins
INFO: selinux enabled
State Changed: start
State Changed: lock buildroot
State Changed: clean
State Changed: init
State Changed: lock buildroot
Mock Version: 1.1.6
INFO: Mock Version: 1.1.6
State Changed: running yum
WARNING: Command failed. See logs for output.
# umount -n /var/lib/mock/dist-EL5-beatport-build-12-847/root/dev/shm --setopt=tsflags=nocontexts
WARNING: Command failed. See logs for output.
# umount -n /var/lib/mock/dist-EL5-beatport-build-12-847/root/dev/pts --setopt=tsflags=nocontexts
WARNING: Command failed. See logs for output.
# umount -n /var/lib/mock/dist-EL5-beatport-build-12-847/root/proc/filesystems --setopt=tsflags=nocontexts
WARNING: Command failed. See logs for output.
# umount -n /var/lib/mock/dist-EL5-beatport-build-12-847/root/sys --setopt=tsflags=nocontexts
WARNING: Command failed. See logs for output.
# umount -n /var/lib/mock/dist-EL5-beatport-build-12-847/root/proc --setopt=tsflags=nocontexts
WARNING: Forcibly unmounting '/var/lib/mock/dist-EL5-beatport-build-12-847/root/dev/shm' from chroot.
WARNING: Forcibly unmounting '/var/lib/mock/dist-EL5-beatport-build-12-847/root/dev/pts' from chroot.
WARNING: Forcibly unmounting '/var/lib/mock/dist-EL5-beatport-build-12-847/root/proc/filesystems' from chroot.
WARNING: Forcibly unmounting '/var/lib/mock/dist-EL5-beatport-build-12-847/root/sys' from chroot.
WARNING: Forcibly unmounting '/var/lib/mock/dist-EL5-beatport-build-12-847/root/proc' from chroot.
ERROR: Command failed:
# /usr/bin/yum --installroot /var/lib/mock/dist-EL5-beatport-build-12-847/root/ groupinstall build --setopt=tsflags=nocontexts
Error: Package: rpm-libs-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libgcc_s.so.1(GCC_3.0)(64bit)
Error: Package: rpm-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: /bin/sh
Error: Package: rpm-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libsqlite3.so.0()(64bit)
Error: Package: rpm-libs-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libelf.so.1(ELFUTILS_1.1.1)(64bit)
Error: Package: logrotate-3.7.4-9.el5_5.2.x86_64 (build)
Requires: libselinux.so.1()(64bit)
Error: Package: nss-3.12.8-1.el5.centos.x86_64 (build)
Requires: libz.so.1()(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: elfutils
Error: Package: 4:perl-5.8.8-32.el5_5.2.x86_64 (build)
Requires: libgdbm.so.2()(64bit)
Error: Package: rpm-libs-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libelf.so.1(ELFUTILS_1.0)(64bit)
Error: Package: rpm-libs-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libselinux.so.1()(64bit)
Error: Package: rpm-libs-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libz.so.1()(64bit)
Error: Package: rpm-libs-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libsqlite3.so.0()(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libsqlite3.so.0()(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: gzip
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: gawk
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: unzip
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libselinux.so.1()(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: /bin/sh
Error: Package: glibc-2.5-49.el5_5.7.x86_64 (build)
Requires: basesystem
Error: Package: logrotate-3.7.4-9.el5_5.2.x86_64 (build)
Requires: /bin/sh
Error: Package: nss-3.12.8-1.el5.centos.x86_64 (build)
Requires: /bin/sh
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: file
Error: Package: rpm-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: crontabs
Error: Package: rpm-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libz.so.1()(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: diffutils
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libelf.so.1(ELFUTILS_1.0)(64bit)
Error: Package: rpm-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libelf.so.1()(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: patch >= 2.5
Error: Package: rpm-libs-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libgcc_s.so.1(GCC_3.3.1)(64bit)
Error: Package: nspr-4.8.6-1.el5_5.x86_64 (build)
Requires: /bin/sh
Error: Package: db4-4.3.29-10.el5_5.2.x86_64 (build)
Requires: libgcc_s.so.1(GCC_3.0)(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: binutils
Error: Package: db4-4.3.29-10.el5_5.2.x86_64 (build)
Requires: libstdc++.so.6(GLIBCXX_3.4)(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: grep
Error: Package: db4-4.3.29-10.el5_5.2.x86_64 (build)
Requires: libstdc++.so.6(CXXABI_1.3)(64bit)
Error: Package: rpm-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: /bin/bash
Error: Package: rpm-libs-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libelf.so.1()(64bit)
Error: Package: rpm-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: coreutils
Error: Package: rpm-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libselinux.so.1()(64bit)
Error: Package: bzip2-1.0.3-6.el5_5.x86_64 (build)
Requires: /bin/sh
Error: Package: glibc-2.5-49.el5_5.7.x86_64 (build)
Requires: libgcc
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: sed
Error: Package: db4-4.3.29-10.el5_5.2.x86_64 (build)
Requires: libgcc_s.so.1()(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libelf.so.1()(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libz.so.1()(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: cpio
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: findutils
Error: Package: rpm-libs-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: libgcc_s.so.1()(64bit)
Error: Package: rpm-build-4.4.2.3-20.el5_5.1.x86_64 (build)
Requires: /bin/bash
Error: Package: db4-4.3.29-10.el5_5.2.x86_64 (build)
Requires: libstdc++.so.6()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
--
Steve Webb | System Administrator
Beatport | Play With Music
------------------------------------------
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
13 years, 3 months
koji/mash : resolving runtime dependency requirements
by Alan Franzoni
Hello,
I hope this is not a dumb question. I'm asking it just before I start
coding my own script for such purpose.
My use case:
I create a new, empty tag, let's call it footag.
In that tag, I start building a project, le'ts say it's called barproject.
barproject has got some BuildRequires (that must be satisfied it it
has been build with kojid, but that's out scope right now) and some
Requires; let's say that it it requires mylib 1.0.0 and otherlib
2.0.0.
mylib 1.0.0 in turns requires exoticlib 1.5.0, and so on, forming a
dependency chain.
Now, my deployment machines are usually configured with standard
centos/redhat repos and another URL pointing to a mash-generated repo
for a certain tag.
Right now, when starting a new tag, I usually go for a pretty
time-consuming process like:
- try installing barproject 1.0;
- yum error: missing deps mylib and otherlib
- add mylib and otherlib to my tag
- try installing barproject 1.0
- yum error: missing dep exoticlib
- add exoticlib to tag
and so on.
So, what I'd like is to have a way to build a dependency chain based
on any build which is available in koji or external repos, so that I
can just tag builds or add repos to the machine. The ideal would be
something like:
> resolve_runtime_deps barproject-1.0.0-1
koji dep: mylib-1.0.0-1
koji dep: otherlib 2.0.0-2
koji dep: exoticlib 1.5.0-2
external repo dep (rh5-os-x86_64): glibc-2.12.10-10
Any clue? Do you think I'm doing anything wrong?
--
Alan Franzoni
--
contact me at public(a)[mysurname].eu
13 years, 3 months
user creation in koji
by Pierre Guillet
Hi all,
I'm trying to build nagios package with my koji server but the build fails
because "nagios" user is not created in the mock chroot. I find some docs to
handle user and group in packages (
http://fedoraproject.org/wiki/Packaging:UsersAndGroups) but no docs to
handle them from koji build.
Are users created in mock chroot from a specific RPM referenced in tag's
build group ?
Regards,
Pierre Guillet
13 years, 3 months
Pungi features - (was: Is pungi the preferred composer for installers?)
by Martin Langhoff
On Wed, Jan 19, 2011 at 5:38 PM, Bruno Wolff III <bruno(a)wolff.to> wrote:
> Pungi is what is used for the install images released by the Fedora Project.
> So for install images it makes sense to use that tool.
Thanks! So we turn to trying to do what I used to do with revisor,
which I am not sure pungi supports
- A custom, locally defined comps file -- how is that done for Spins?
For example, how would you build the server spin based on the files at
http://dmach.fedorapeople.org/server-spin/ ?
- Can I copy a kickstart file in the resulting iso?
- Can I set the syslinux menu? What I normally do is set the defaul
menu item to use the provided ks...
thanks!
cheers,
m
--
martin.langhoff(a)gmail.com
martin(a)laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
13 years, 3 months
Revisor broken on F14? Is pungi the preferred composer for installers?
by Martin Langhoff
Trying to build a minimal 'server' profile compose, I find that
revisor on F14 has bugs/issues that hint at it not being used at all
-- notably #bz649815, where revisor expects to find and use
/usr/lib/anaconda-runtime and expects an anaconda-runtime package to
exist in the compose.
Is pungi used more widely?
cheers,
m
--
martin.langhoff(a)gmail.com
martin(a)laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
13 years, 3 months
Tag inheritance and "masked" newer builds
by Alan Franzoni
Hello,
we've just found out a behaviour we'd like to change in koji.
Simple case:
two tags: child and parent, with child (obviously) inheriting from parent.
builds:
foopkg-1.0.0-1 is tagged 'child'
foopkg-2.0.0-1 is tagged 'parent'
If I list the builds in the 'child' tag, setting inherited and latest,
i get foopkg-1.0.0-1 - it seems that koji resorts to inheritance only
if a build for a package name does not exist in the required tag.
Is there any way to prevent this from happening, and get the "truly
latest" build for a package in the 'child' tag?
--
Alan Franzoni
--
contact me at public(a)[mysurname].eu
13 years, 3 months
koji 1.6.0 new feature - win-build
by Michael Cronenworth
Does a documentation page exist for the new win-build feature? I cannot
seem to find one.
If there isn't one, could someone reply with a simple HOW-TO on how to
use it?
Thanks,
Michael
13 years, 3 months
where is glibc32
by Farkas Levente
hi,
it seems on koji's mock there is a glibc32 packages which is in x86_64
system's input repo since mock can install it during build (eg: grub).
but glibc32 is not included in neither any fedora distro nor in
http://infrastructure.fedoraproject.org/ (at least i cant find it). but
i can find the packages itself at
http://pkgs.fedoraproject.org/gitweb/?p=glibc32.git
so what is the status of this package how can be it get into the mock
buildroot etc?
thanks in advance.
regards.
--
Levente "Si vis pacem para bellum!"
13 years, 3 months
