12 Jan
2023
12 Jan
'23
00:12
Hello Andrei - Thanks for your email... On Wed, 11 Jan 2023 09:42:38 +0300, Andrei Borzenkovwrote: >On Wed, Jan 11, 2023 at 8:29 AM Glen Barney 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 >- 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. I apologize, could I get some additional details on "edit the macro?" My goal here is simply to be able to install Python310 alongside the other versions, but the RPMs appear to prevent that quite aggressively. I know how to unpack and repack an RPM, but I am not familiar with "the macro" but if there is an edit I can make to the RPM to solve this I would love to understand what to do! >> 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. I apologize, I'm not able to parse this. I tried to go to that link, but got the "not authorized" message. I'm not sure why the public are not allowed to view bugs, but perhaps I am just ignorant of Suse's way of doing things? Would you or someone here be willing to paste in for me the appropriate info from this bug so that I can read it? And/or any other clues would be gratefully appreciated. Thank you! Glen