Description of problem: python-rpmfluff fails to build on armv7hl. Version-Release number of selected component (if applicable): 0.5.7.1-6.fc33 How reproducible: always Steps to Reproduce: 1. $ fedpkg build --nowait --scratch --arches armv7hl Actual results: Build fails. Expected results: Build succeeds. Additional info: Traceback (most recent call last): File "rpmfluff.py", line 342, in do_make log = subprocess.check_output(command, stderr=subprocess.STDOUT).splitlines(True) File "/usr/lib/python3.8/subprocess.py", line 411, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.8/subprocess.py", line 512, in run raise CalledProcessError(retcode, process.args, subprocess.CalledProcessError: Command '['rpmbuild', '--define', '_topdir /builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1', '--define', '_rpmfilename %%{ARCH}/%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm', '-ba', '--target', 'arm', 'test-rpmbuild-test-add-commiter-0.1-1/test-add-commiter.spec']' returned non-zero exit status 1. During handling of the above exception, another exception occurred: Traceback (most recent call last): File "rpmfluff.py", line 1607, in test_add_commiter self.rpmbuild.make() File "rpmfluff.py", line 276, in make self.do_make() File "rpmfluff.py", line 344, in do_make raise RuntimeError('rpmbuild command failed with exit status %s: %s\n%s' RuntimeError: rpmbuild command failed with exit status 1: ['rpmbuild', '--define', '_topdir /builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1', '--define', '_rpmfilename %%{ARCH}/%%{NAME}-%%{VERSION}-%%{RELEASE}.%%{ARCH}.rpm', '-ba', '--target', 'arm', 'test-rpmbuild-test-add-commiter-0.1-1/test-add-commiter.spec'] b'warning: Found bdb Packages database while attempting sqlite backend: using bdb backend.\nBuilding target platforms: arm\nBuilding for target arm\nExecuting(%prep): /bin/sh -e /var/tmp/rpm-tmp.q9ZOtU\n+ umask 022\n+ cd /builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1/BUILD\n+ RPM_EC=0\n++ jobs -p\n+ exit 0\nExecuting(%build): /bin/sh -e /var/tmp/rpm-tmp.BKGDYS\n+ umask 022\n+ cd /builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1/BUILD\n+ RPM_EC=0\n++ jobs -p\n+ exit 0\nExecuting(%install): /bin/sh -e /var/tmp/rpm-tmp.YTu3IW\n+ umask 022\n+ cd /builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1/BUILD\n+ \'[\' \'/builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1/BUILDROOT/test-add-commiter-0.1-1.%{_arch}\' \'!=\' / \']\'\n+ rm -rf \'/builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1/BUILDROOT/test-add-commiter-0.1-1.%{_arch}\'\n++ dirname \'/builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1/BUILDROOT/test-add-commiter-0.1-1.%{_arch}\'\n+ mkdir -p /builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1/BUILDROOT\n+ mkdir \'/builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1/BUILDROOT/test-add-commiter-0.1-1.%{_arch}\'\n+ rm -rf \'/builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1/BUILDROOT/test-add-commiter-0.1-1.%{_arch}\'\n+ mkdir \'/builddir/build/BUILD/rpmfluff-0.5.7.1/test-rpmbuild-test-add-commiter-0.1-1/BUILDROOT/test-add-commiter-0.1-1.%{_arch}\'\n+ /usr/lib/rpm/check-buildroot\nxargs: invalid number "%{_smp_build_ncpus}" for -P option\nTry \'xargs --help\' for more information.\n+ /usr/lib/rpm/redhat/brp-ldconfig\n+ /usr/lib/rpm/brp-compress\n+ /usr/lib/rpm/brp-strip /usr/bin/strip\nxargs: invalid number "%{_smp_build_ncpus}" for -P option\nTry \'xargs --help\' for more information.\nerror: Bad exit status from /var/tmp/rpm-tmp.YTu3IW (%install)\n\n\nRPM build errors:\n Found bdb Packages database while attempting sqlite backend: using bdb backend.\n Bad exit status from /var/tmp/rpm-tmp.YTu3IW (%install)\n' https://koji.fedoraproject.org/koji/taskinfo?taskID=44872219
Hello Mirek. Could you please take a look into this issue (I have seen you commenting in possibly relevant bug 1836108)? Looks like I'm not able to build on ARM: https://koji.fedoraproject.org/koji/buildinfo?buildID=1586790 while it works otherwise: https://koji.fedoraproject.org/koji/buildinfo?buildID=1586770 Please do you have any idea on what does this error mean?
Mirek as in Mirek Suchý? He's not CCed here.
(In reply to Jan Hutař from comment #1) > Hello Mirek. Could you please take a look into this issue (I have seen you > commenting in possibly relevant bug 1836108)? Looks like I'm not able to > build on ARM: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1586790 > > while it works otherwise: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1586770 > > Please do you have any idea on what does this error mean? Oops, forgot to needinfo Mirek.
The culprit is: /usr/lib/rpm/check-buildroot\nxargs: invalid number "%{_smp_build_ncpus}" for -P option So during it seems that %{_smp_build_ncpus} expands to something else than number.
Hello Panu! Could you please take a look at the failed build? Looks like this %{_smp_build_ncpus} macro is defined in file provided by rpm package (although I only checked on my laptop and not on ARM host). Failed build (reproducible): https://koji.fedoraproject.org/koji/buildinfo?buildID=1586790
> "invalid number "%{_smp_build_ncpus}" for -P option" That means "%{_smp_build_ncpus}" is the literal value passed to -P, which means it's not defined at all. Which means the platform macro definitions are not being loaded. Uh-oh. This rings a bell, koji sets --target explicitly by some logic of its own, and on arm that value is wrong. At least sometimes. Note this: > '--target', 'arm' So it's calling "rpmbuild -ba --target arm [...]" but there is no such platform as "arm" (or "arm-linux", which that gets expanded to) defined on Fedora, just these: armv3l-linux armv4b-linux armv4l-linux armv5tejl-linux armv5tel-linux armv5tl-linux armv6hl-linux armv6l-linux armv7hl-linux armv7hnl-linux armv7l-linux armv8hl-linux armv8l-linux Basically this is a dupe of bug 1096480 but as that one is EPEL and I don't know if this is a code, configuration (or both) thing, leaving it up to koji maintainers...
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
So, I see there is a successfull build in f34? Is this solved, or is there other conditions under which it would fail? I do see that this is a noarch package...
(In reply to Kevin Fenzi from comment #8) > So, I see there is a successful build in f34? Is this solved, or is there > other conditions under which it would fail? > > I do see that this is a noarch package... Hello Kevin. Are you talking about this build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1589928 ? According to log below, it was not running on ARM: https://kojipkgs.fedoraproject.org//packages/python-rpmfluff/0.6.1/1.fc34/data/logs/noarch/hw_info.log
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Also happens on Fedora 34, 35 and 36. > I do see that this is a noarch package... Yes, the build fails when Koji uses a armv7hl builder.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.