TW: Springclean for Python (3.8 -> 3.10)
Morning, as TW has moved to python 3.10, my guess is that all python38-* became obsolete. As python36* is not removed automatically, what is the recommended way to get rid of the obsolete packages? Simply delete? Cheers Axel
On 04.07.22 09:45, Axel Braun wrote:
Morning,
as TW has moved to python 3.10, my guess is that all python38-* became obsolete.
As python36* is not removed automatically, what is the recommended way to get rid of the obsolete packages? Simply delete?
If you remove python38-base, zypper will take them with it. But be aware that if you need a certain python module for a script of yours, you might want to install the 310 variant first. There is no migration unless you packaged your script Greetings, Stephan
Dne 04. 07. 22 v 10:02 Stephan Kulow napsal(a):
If you remove python38-base, zypper will take them with it.
Don’t just blindly press yes, removing python38-base could have a tendency to remove more than you wish. If it happens to you, press 'N' and remove in smaller hunks (like remove few important packages until the number of python38-* packages becomes manageable). Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 History is something which should never happen again. -- heard on BBC program Germany: Memories of a Nation
I had a similar dilema and I did the following - *on* *a* *completely* *updated* *machine* : rpm -e --nodeps `rpm -qa | grep ^python38 | xargs` Then I run zypper verify. I remained with 14 packages and was able to remove them one after another. It included the corresponding libpython* Cheers F. On 04/07/2022 11:08, Matěj Cepl wrote:
Dne 04. 07. 22 v 10:02 Stephan Kulow napsal(a):
If you remove python38-base, zypper will take them with it.
Don’t just blindly press yes, removing python38-base could have a tendency to remove more than you wish. If it happens to you, press 'N' and remove in smaller hunks (like remove few important packages until the number of python38-* packages becomes manageable).
Matěj
W dniu 04.07.2022 o 09:45, Axel Braun pisze:
Morning,
as TW has moved to python 3.10, my guess is that all python38-* became obsolete.
As python36* is not removed automatically, what is the recommended way to get rid of the obsolete packages? Simply delete?
Cheers Axel
You might want to first check the output of # zypper se -i python38-* | grep "^i+" This way you can find packages that you installed explicitly. For example I had python38-docker-compose, which gives "docker-compose" command. I had to make sure all such tools are installed from python310-* variants and I could remove python38-*.
On 04.07.22 12:57, Adam Mizerski wrote:
This way you can find packages that you installed explicitly. For example I had python38-docker-compose, which gives "docker-compose" command. I had to make sure all such tools are installed from python310-* variants and I could remove python38-*.
I later had to install python310-keyring or osc would no longer access my keyring ;-) Probably everybody has one package he is missing afterwards ;-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
Am Montag, 4. Juli 2022, 21:02:49 CEST schrieb Stefan Seyfried:
On 04.07.22 12:57, Adam Mizerski wrote:
This way you can find packages that you installed explicitly. For example I had python38-docker-compose, which gives "docker-compose" command. I had to make sure all such tools are installed from python310-* variants and I could remove python38-*.
I later had to install python310-keyring or osc would no longer access my keyring ;-)
Probably everybody has one package he is missing afterwards ;-)
Indeed, natsort was it in my case. All stuff removed, carefully some single packages first, then python38-base, and up to now no issues detected Thanks Axel
participants (6)
-
Adam Mizerski -
Axel Braun -
Fridrich Strba -
Matěj Cepl -
Stefan Seyfried -
Stephan Kulow