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
Some dumb questions, I am sure you have thought about this but I don't see anything in the macros:
This may eventually build fully for Staging:N. But when it goes into the Tumbleweed repository, what will happen for users? Won't all python3-foo packages cease to exist? Don't we need the python3?-foo packages have a Provides: and Obsoletes:, for distribution updates to work? And as a result of that, will the python36-foo and python38-foo create numerous "have choice" unresolvables in the openSUSE Build System and yast/zypper?
Some dumb questions, I am sure you have thought about this but I don't see anything in the macros:
This may eventually build fully for Staging:N. But when it goes into the Tumbleweed repository, what will happen for users? Won't all python3-foo packages cease to exist? Don't we need the python3?-foo packages have a
Provides:
andObsoletes:
, for distribution updates to work? And as a result of that, will the python36-foo and python38-foo create numerous "have choice" unresolvables in the openSUSE Build System and yast/zypper?Originally posted by @bnavigator in #65 (comment)
The text was updated successfully, but these errors were encountered: