tor 2015-10-01 klockan 13:43 -0400 skrev Irina Boverman: > See here: > http://koji.fedoraproject.org/koji/taskinfo?taskID=11296302 > > https://kojipkgs.fedoraproject.org//work/tasks/6309/11296309/root.log > -- > DEBUG util.py:441: Executing command: ['/usr/bin/yum', '- > -installroot', '/var/lib/mock/dist-6E-epel-build-4130166 > -530761/root/', 'groupinstall', 'build'] with env {'LANG': 'en_US.UTF > -8', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'LC_MESSAGES': 'C', > 'PROMPT_COMMAND': 'printf "\x1b]0;<mock-chroot>\x07<mock-chroot>"', > 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'HOME': '/builddir', > 'HOSTNAME': 'mock'} and shell False > DEBUG util.py:377: Error: Package: redhat-rpm-config-9.0.3 > -44.el6.noarch (build) > DEBUG util.py:377: Requires: /bin/sh > DEBUG util.py:377: Error: Package: redhat-rpm-config-9.0.3 > -44.el6.noarch (build) > DEBUG util.py:377: Requires: mktemp > DEBUG util.py:377: Error: Package: epel-release-6-8.noarch (build) > DEBUG util.py:377: Requires: /bin/sh > DEBUG util.py:377: Error: Package: epel-release-6-8.noarch (build) > DEBUG util.py:377: Requires: redhat-release >= 6 > DEBUG util.py:377: You could try using --skip-broken to work around > the problem > DEBUG util.py:377: You could try running: rpm -Va --nofiles - > -nodigest > DEBUG util.py:377: Error: Package: redhat-rpm-config-9.0.3 > -44.el6.noarch (build) > DEBUG util.py:377: Requires: /usr/bin/perl > DEBUG util.py:377: Error: Package: redhat-rpm-config-9.0.3 > -44.el6.noarch (build) > DEBUG util.py:377: Requires: perl(Getopt::Long) > DEBUG util.py:377: Error: Package: redhat-rpm-config-9.0.3 > -44.el6.noarch (build) > DEBUG util.py:377: Requires: /bin/bash > DEBUG util.py:488: Child return code was: 1 > DEBUG util.py:170: kill orphans > -- > Regards, Irina.
The EPEl build root contains the combination of the RHEL and EPEL
repos. Koji knows when the EPEL repo is updated and regenerates the
build root when this happens, but when RHEL is updated there is no
immediate automatic regeneration triggered of the EPEL build root, so
the EPEL build root can be broken for some time.
The trick I usually do in this case is that I request a build root
override for some package in the affected EPEL release (even though I
don't really need one), which triggers a regeneration of the build root
that picks up the changes from the RHEL repo.
Mattias
smime.p7s
Description: S/MIME cryptographic signature
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
