-
Notifications
You must be signed in to change notification settings - Fork 20
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_module problems when flavors python2 and python3 are disabled #33
Comments
The python-backports.* series have even stranger errors
https://build.opensuse.org/package/live_build_log/home:jayvdb:py3only/python-backports.functools_partialmethod/openSUSE_Tumbleweed/x86_64
|
This is a result of the packages not having any flavor at all, so they get unresolvable, we didn't solve this out as those packages will mostly need to be just deleted anyway because they serve no purpose on the product as they are having all the targets disabled. The message can be improved but as we plan to just kill them all in one batch it is kinda pointless to tweak the message. |
This issue is probably complete obsolete with new versions of this package, isn't it? |
No response, closing this. Please, feel free to reopen with the additional information. |
I have a hacky project conf which eliminates py2 from the project
https://build.opensuse.org/project/prjconf/home:jayvdb:py3only
The most obvious ugly side effect is py2-only packages become "unresolvable" (great!), but the reason is "nothing provides STOP-setuptools, nothing provides MACRO"
e.g.
https://build.opensuse.org/project/monitor/home:jayvdb:py3only?arch_x86_64=1&defaults=0&repo_openSUSE_Tumbleweed=1&unresolvable=1
currently bz2file, ipykernel & ipython
I guess the
nothing provides STOP-setuptools
is caused by https://github.com/openSUSE/python-rpm-macros/blob/d9968ab7b3c753a3cc82ec0b1d8fab1a249a09c1/buildset.inIf there isnt an easy way around that, I guess it could be made a bit prettier by replacing
STOP
withpy0
"nothing provides MACRO" may be the same cause; i'm not sure.
The text was updated successfully, but these errors were encountered: