Overview
[ 40s] error: /home/abuild/rpmbuild/SOURCES/gnu-compilers-hpc.spec: line 76: Too many levels of recursion in macro expansion. It is likely caused by recursive macro declaration.
Packaging glitch in suse-hpc's macros.hpc file. %__elflib_exclude_path does not exist anymore.
A possible fix is to change global tmp %__elflib_exclude_path to global tmp %?__elflib_exclude_path. Or just do away with the definition.
Request History
mlschroe created request
update to rpm-4.17.0
dimstar_suse set openSUSE:Factory:Staging:C as a staging project
Being evaluated by staging project "openSUSE:Factory:Staging:C"
dimstar_suse accepted review
Picked "openSUSE:Factory:Staging:C"
factory-auto added opensuse-review-team as a reviewer
Please review sources
factory-auto accepted review
Check script succeeded
dimstar accepted review
licensedigger accepted review
The legal review is accepted preliminary. The package may require actions later on.
dimstar_suse accepted review
Staging Project openSUSE:Factory:Staging:C got accepted.
dimstar_suse approved review
Staging Project openSUSE:Factory:Staging:C got accepted.
dimstar_suse accepted request
Staging Project openSUSE:Factory:Staging:C got accepted.
python38-base (package python38:base) seems no longer to provide
python(abi) = 3.8, which causes a lot of unresolvablesThe reason for this seems to be that python.attr has moved from rpm-build to rpm-build-python, where in a default buildroot we do not install rpm-build-python.
Is this move intentional? Do we need to extend the Required: field in prjconf to also install rpm-build-python?
Yes, it was intentional. That's the last bit of python we had in the base rpm packages. Everything pythonish is in rpm-build-python. (We might want to completely split this off from rpm in the future.)
rpm-build contains this requires:
Requires: (%{name}-build-python if python3-base)This should be enough to get rpm-build-python into all builds that build python stuff. The exception seems to be the python build itself, maybe a
in the spec file would be enough to resolve this.
(I can of course also revert the change)
sr#924860 - let's see what the python maintainers say
local build of python38-base with rpm-build-python injected added the python(abi) provides as expected
Last one seems to be vagrant:
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:Staging:C/vagrant/standard/x86_64
The
%{?load:->{load:is the easy part, but then it fails on expanding{ruby:3 < 3.1}https://build.opensuse.org/package/live_build_log/home:dimstar:Factory/vagrant/Staging_C/x86_64
I'm pretty sure that this is a packaging bug. Old rpm versions simply ignored everything after the ':'. With rpm-4.17 this is no longer the case.
So the question is, what is the intention of that BuildRequires in the vagrant package?
Thanks for the pointer!
In this case, I assume the correct thing would be
%{ruby} < 3.1- %{ruby} being expanded to the ruby package name used (ruby3.0 or ruby2.7)sr#926803