On Tue, 2021-12-14 at 18:10 +0100, Ben Greiner wrote:
The solution was to remove the dependency. I believe this was ill- advised. If python is installed, I expect 'rpm --eval %{python_version}' to work.
That's the worst example. Considering the singlespec system, which version should this command return?
Outside the build environment: the system's primary version. And that's what it does, AFAICT. Granted, it's not important. But it was my expectation.
The fact that the dependency has now been added to the rpm package instead makes no sense to me. What did we gain in the end by moving this dependency from python3-base to rpm?
python-rpm-macros is a package used during building. Why should python3-base pull it in for user installations?
The discussion here was about SLE15/Leap15. python3-base has pulled in python-rpm-macros for >3y on this "stable" code base. It's no surprise that packages rely on that, and it should be no surprise that people are annoyed that their package builds suddenly break because the dependency was silently dropped in a maintenance update. So far there was no requirement to use explicit BuildRequires on python-rpm-macros (I'm not talking about python modules / singlespec, just about an application that happens to be written in python). On TW it's implicitly pulled in via rpm-build -> rpm-build-python, but no such chain exists for Code 15. Martin