You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine a base package foo which has a sub-package python-foo.
The %python_subpackages macro generates packages python2-foo and python3-foo so that the build succeeds, but their metadata (description, Provides/Obsoletes) is copied from foo.
Expection would be that python*-foo metadata gets derived from python-foo.
This also appears to be the explanation why python-foo-bar sub-package does not result in python3-foo-bar etc. sub-packages getting defined, causing an error from %{python_files bar}.
Imagine a base package
foo
which has a sub-packagepython-foo
.The
%python_subpackages
macro generates packagespython2-foo
andpython3-foo
so that the build succeeds, but their metadata (description, Provides/Obsoletes) is copied fromfoo
.Expection would be that
python*-foo
metadata gets derived frompython-foo
.Example: https://build.opensuse.org/package/show/home:a_faerber:branches:devel:tools:statica/z3
The text was updated successfully, but these errors were encountered: