Re: Why fedpkg build failed ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



If you take a look inside the root.log of the build task here: https://kojipkgs.fedoraproject.org//work/tasks/4647/45824647/root.log, you will see the actual error that is being reported. It appears that a depoendency of the package (aqsis-core) cannot be installed due to an issue with how it is packaged and the Boost update that just happened. This already has a Bugzilla here: https://bugzilla.redhat.com/show_bug.cgi?id=1843098, so you are probably going to have to wait until that gets fixed before you are able to build.

-Ian

On Wed, Jun 17, 2020 at 2:03 PM J. Scheurich <mufti11@xxxxxx> wrote:
Hi,

I updated white_dune with creating a source.rpm,

$ fedpkg clone wdune
$ fedpkg import source.rpm
$ fedpkg commit
$ fedpkg push
$ fedpkg build

but i get the following problem

https://koji.fedoraproject.org/koji/taskinfo?taskID=45824536 ->
https://koji.fedoraproject.org/koji/taskinfo?taskID=45824645 ->
https://kojipkgs.fedoraproject.org//work/tasks/4645/45824645/root.log

INFO buildroot.py:440:  Mock Version: 2.3
DEBUG util.py:215:  ensuring that dir exists: /var/lib/mock/f33-build-21066053-1630063/root/dev/pts
DEBUG util.py:218:  creating dir: /var/lib/mock/f33-build-21066053-1630063/root/dev/pts
DEBUG util.py:215:  ensuring that dir exists: /var/lib/mock/f33-build-21066053-1630063/root/dev/shm
DEBUG util.py:218:  creating dir: /var/lib/mock/f33-build-21066053-1630063/root/dev/shm
DEBUG buildroot.py:598:  kernel version == 5.6.15-300.fc32.armv7hl+lpae
DEBUG util.py:228:  touching file: /var/lib/mock/f33-build-21066053-1630063/root/etc/fstab
DEBUG util.py:228:  touching file: /var/lib/mock/f33-build-21066053-1630063/root/etc/yum/yum.conf
DEBUG util.py:228:  touching file: /var/lib/mock/f33-build-21066053-1630063/root/etc/dnf/dnf.conf
DEBUG util.py:228:  touching file: /var/lib/mock/f33-build-21066053-1630063/root/var/log/yum.log
DEBUG util.py:215:  ensuring that dir exists: /var/lib/mock/f33-build-21066053-1630063/root/proc
DEBUG util.py:793:  child environment: None
DEBUG util.py:719:  Executing command: ['/bin/mount', '-n', '-t', 'tmpfs', '-o', 'rprivate', 'tmpfs', '/var/lib/mock/f33-build-21066053-1630063/root/proc'] with env {'TERM': 'vt100', 'SHELL': '/bin/sh', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'LANG': 'C.UTF-8'} and shell False
DEBUG util.py:774:  Child return code was: 0
DEBUG util.py:215:  ensuring that dir exists: /var/lib/mock/f33-build-21066053-1630063/root/proc
DEBUG util.py:793:  child environment: None
DEBUG util.py:719:  Executing command: ['/bin/mount', '-n', '--rbind', '-o', 'nodev,noexec,nosuid,readonly,rprivate', '/proc', '/var/lib/mock/f33-build-21066053-1630063/root/proc'] with env {'TERM': 'vt100', 'SHELL': '/bin/sh', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'LANG': 'C.UTF-8'} and shell False
DEBUG util.py:774:  Child return code was: 0
DEBUG util.py:215:  ensuring that dir exists: /var/lib/mock/f33-build-21066053-1630063/root/sys
DEBUG util.py:793:  child environment: None
DEBUG util.py:719:  Executing command: ['/bin/mount', '-n', '-t', 'tmpfs', '-o', 'rprivate', 'tmpfs', '/var/lib/mock/f33-build-21066053-1630063/root/sys'] with env {'TERM': 'vt100', 'SHELL': '/bin/sh', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'LANG': 'C.UTF-8'} and shell False
DEBUG util.py:774:  Child return code was: 0
DEBUG util.py:215:  ensuring that dir exists: /var/lib/mock/f33-build-21066053-1630063/root/sys
DEBUG util.py:793:  child environment: None
DEBUG util.py:719:  Executing command: ['/bin/mount', '-n', '--rbind', '-o', 'nodev,noexec,nosuid,readonly,rprivate', '/sys', '/var/lib/mock/f33-build-21066053-1630063/root/sys'] with env {'TERM': 'vt100', 'SHELL': '/bin/sh', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'LANG': 'C.UTF-8'} and shell False
DEBUG util.py:774:  Child return code was: 0
...
....

What do this messages mean ?

so long
MUFTI
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux