Kenneth Goldman wrote: > https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_ > GNU_Hello/ > > ~~~~~~~~~~~~~~~~~~~~~~~ > > when running that tutorial (Fedora 37, x86), I get this error: > > ERROR: Exception(/home/kgold/hello/hello-2.10-1.fc37.src.rpm) > Config(fedora-37-x86_64) 0 minutes 18 seconds > INFO: Results and/or logs in: /home/kgold/hello/results_hello/2.10/1.fc37 > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > The log has at the end:, but I suspect that the python issue is a reporting > issue, not the actual failure. > > RPM build errors: > Child return code was: 1 > EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M > d0156a2d35ca46a0ba55a993d05852c1 -D /var/lib/mock/fedora-37-x86_64/root -a > -u mockbuild --capability=cap_ipc_lock > --bind=/tmp/mock-resolv.lphffv1r:/etc/resolv.conf --bind=/dev/btrfs-control > --bind=/dev/mapper/control --bind=/dev/loop-control --bind=/dev/loop0 > --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 > --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 > --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe > --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir > --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin > --setenv=PROMPT_COMMAND=printf "\\033]0;<mock-chroot>\\007" > --setenv=PS1=<mock-chroot> \\s-\\v\\$ --setenv=LANG=C.UTF-8 > --resolv-conf=off bash --login -c /usr/bin/rpmbuild -bb --target x86_64 > --nodeps /builddir/build/SPECS/hello.spec\n', 1)] > Traceback (most recent call last): > File "/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py", > line 93, in trace > result = func(*args, **kw) > ^^^^^^^^^^^^^^^^^ > File "/usr/lib/python3.11/site-packages/mockbuild/util.py", line 598, in > do_with_status > raise exception.Error("Command failed: \n # %s\n%s" % (command, output), > child.returncode) > mockbuild.exception.Error: Command failed: > > ~~~~~~~~~~~~~~~~~~~~~~~~~ > > When I try /usr/bin/systemd-nspawn directly, I get this. What directory is > it looking for? /var/lib/mock/fedora-37-x86_64/root exists. I don't run as > root, right? > > mock-chroot: No such file or directory. If you're running that command directly, it looks like you need to quote some things. Particularly: --setenv=PS1=<mock-chroot> \\s-\\v\\$ should be quoted: --setenv=PS1='<mock-chroot> \\s-\\v\\$' (I don't know offhand if the backslashes still need to be escaped or not.) As for the real issue, the mock build log may have more details above the EXCEPTION. That's probably worth exploring before you spend too much time on how to reproduce the systemd-nspawn command. -- Todd
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
