On Thu, 12 Jan 2023 01:02:06 -0600, J Leslie Turriff wrote:

Whoever decided to set it up this way obviously didn't think about migration testing or multiple server support, where both versions need to be available.

That is precisely our use case: Migration work and multiple server support.

Maybe (if you can locate them) talk to the folks who maintain update-alternatives and ask them to discuss it with the Python folks?

I would be delighted to do that. However I too am stuck by "if you can locate them". Does anyone here have any guidance or clues on how I might do that? Happy to follow any directions, just don't know of myself where they might be either! Late night here so I must crash for now but thank you all for your responses, and for any further guidance or information that you might have! Looking forward to anything else I can do when I return to consciousness. Glen

On 2023-01-12 01:29:52 Simon Lees wrote:

|On 1/12/23 17:32, J Leslie Turriff wrote: |> On 2023-01-12 00:59:11 Glen Barney wrote: |>> |On Thu, 12 Jan 2023 17:24:34 +1030, Simon Lees wrote: |>> |> Don't shoot the messenger, that's just the content of the bugreport. |>> | |>> |No shooting intended from here for sure! I'm very grateful for your |>> |sharing the contents of the bug report, and the history. |>> | |>> |> At a guess i'd say its related to the way someone would like it to |>> |> be implemented for package hub as they are probably using the same |>> |> package. |>> | |>> |So I guess same question: What options do I, as a lowly user, have to |>> |somehow move this along, and/or get it changed, and/or get some kind |>> | of workaround? I know I can build from source, but I really prefer |>> | the advantages of distro-provided packages if at all possible, not to |>> | mention the nice /etc/alternatives and related support that OpenSuse |>> | provides. |>> | |>> |Would it make sense, for example, to raise this on the opensuse-python |>> |list? Or is there some other action I could take to help facilitate? |>> | |>> |Apologies that I lack the organizational/political knowledge here - |>> | I've been a fan of OpenSuse from the v7 days and have always used it |>> | as my primary, but that confers zero knowledge about the people |>> | behind the decisions! |>> | |>> |Thanks for any insight or pointers anyone can provide! |>> | |>> |Glen |> |> Maybe (if you can locate them) talk to the folks who maintain |> update-alternatives and ask them to discuss it with the Python folks? | |In this case its not needed because the packages already don't conflict |so update alternatives wouldn't actually solve anything.

My point is that maybe the update-alternatives folks would be able to coerce the Python folks to relax the restriction. But maybe it's not the Python folks but the openSUSE packagers they need to talk to? Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 x86_64