Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

python- sub-packages not handled correctly #15

Closed
afaerber opened this issue Mar 30, 2018 · 1 comment · Fixed by #75
Closed

python- sub-packages not handled correctly #15

afaerber opened this issue Mar 30, 2018 · 1 comment · Fixed by #75

Comments

@afaerber
Copy link
Member

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.

Example: https://build.opensuse.org/package/show/home:a_faerber:branches:devel:tools:statica/z3

@afaerber
Copy link
Member Author

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}.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant