I sent my other email and then saw this:

On Thu, 12 Jan 2023 16:26:48 +1030 , Simon Lees wrote:

>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?expand=1

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

So it seems that this bug is the same problem I'm having?  I read and

appreciated your explanation about the bug system.  Is it possible to

perhaps add me to that bug, or at least add the information I've sent

to the bug to help the maintainers fix this?

>As with many fun things in life, its a Legacy software issue. Currently

>we are still using a bugzilla instance from the Novell era. It has some

>unfortunate settings that are very hard to change, many that any bug

>thats listed for SUSE Partners becomes closed. That bugzilla instance

>has so many patches that its very hard to work on or update.

change to the list system was made, my primary address somehow ended up

banned systemwide (and no, I had not offended anyone ever or even come close

to it as far as I know!) but I was unable to subscribe myself to or remove

myself from ANY OpenSuse lists - and I had no idea who to contact to fix

that.  I ended up just creating a new freemail address just so I could get

these support requests through - but there are certainly problems in the

Mailman3 system as well, FWIW...

Thanks again for any information or assistance!