Am 14.12.21 um 17:08 schrieb Martin Wilck:
Looks like this used to be pulled in by something but not anymore for multiple packages.
I maintain a python package which started failing on 15.2 and 15.3 due to lack of this macro. Thanks
Michal AFAIR it was intentional but reverted for Tumbleweed, apparently the reversal didn't make it into SLE15-SP2: https://build.opensuse.org/request/show/864328 talks about bsc#1180125, but that one is not available for us non-SUSErs.
IMHO you should explicitly require it if you are using definitions from it. 1180125 was a complaint that python3-base pulls in python-rpm-macros. Some people seem seriously concerned about 50kB worth of rpm macro code.
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? If you want to get the python version of the command currently in your path, use the python interpreter directly. If you want to know which python package is installed with the system packages use `zypper search --provides python(abi)` or `rpm -qf /usr/bin/python*`
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?