On 1/11/23 17:12, Andrei Borzenkov wrote:
On Wed, Jan 11, 2023 at 8:29 AM Glen Barney <gn56@hotmail.com> wrote: ....
In this situation, it becomes more clear that Python310 packages REQUIRE
the removal of Python39 - which is, as far as I can tell, the core issue.
Tue Feb 15 23:05:55 UTC 2022 - Matej Cepl <mcepl@suse.com>
- bsc#1195831 Obsolete older "most modern" versions of python packages (python39 for python310 and so forth). For next versions it is necessary just to edit the macro.
As far as I can tell, they "should not" require that - but they do. There
is that rule "Python310 obsoletes Python39" - but that should not be the case?
https://bugzilla.opensuse.org/show_bug.cgi?id=1195831 You are not authorized to access bug #1195831.
Welcome to the community distribution.
Bug 1195831 - python310 doesn't offer a migration path With the submitted python310 in Staging there is no submission path offered to do a removal of python39 and replace it with the newer version. This would lead to an orphaned package on migrations and customers not receiving the newer python310. I don't think that python310 can follow the guidelines and do a Provides and Obsoletes. An alternative might be to introduce a meta package for this development interpreter like it is done for rust: https://build.suse.de/package/view_file/SUSE:SLE-15-SP4:GA/rust/rust.spec?ex... or introducing a python39-obsolete, which Recommends the installation of python310. There might be other solutions to this as well, but we definitely require some fix for this migration/orphaned package issue. ------------------------------------------------------------------- An obsolete is not a conflict however, so this change doesn't explain them not being co install-able. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B