Tumbleweed - Review of the week 2022/09
Dear Tumbleweed users and hackers, Another week, filled with snapshots, is coming to an end. Tumbleweed has been rolling full speed ahead, bringing you 6 snapshots in 7 days (0225, 0226, 0227, 0228, 0301, and 0302). The snapshots contained, amongst others, these changes: * ModemManager 1.18.6 * Mesa 21.3.7 * freerdp 2.6.0 * Nodejs 17.5.0 * Linux kernel 5.16.11 * Python 3.6 interpreter has been removed for good now * firewalld 1.1.0 * screen 4.9.0: CVE-2021-26937: possible denial of service via a crafted UTF * NetworkManager 1.36.0 * pipewire 0.3.47 * Ruby 3.1.1 With all these changes done, the staging projects are almost empty now. OBS is getting bored. Keep your changes coming! Anyway, ‘almost’ empty is key here: we have these changes currently to be tested: * KDE Gear 21.12.3 * Poppler 22.03.0: poppler being poppler, breaking left and right (Staging:M) * Rust 1.59 * go 1.16.15 & 1.17.8 * Binutils 2.38 (Staging:A) * GCC 12 Cheers, Dominique
Dominique, Previous weeks in review included this line about Python 3.10 becoming the default distro but I noticed that was removed. Has something occurred to delay the switch to Python 3.10? * Python 3.10 as the distro default interpreter (a bit down the line, after py36 is done)
On Sat, 2022-03-05 at 22:30 +0000, Joe Salmeri wrote:
Dominique,
Previous weeks in review included this line about Python 3.10 becoming the default distro but I noticed that was removed. Has something occurred to delay the switch to Python 3.10?
* Python 3.10 as the distro default interpreter (a bit down the line, after py36 is done)
right - it's indeed been delayed a bit further, mainly due to https://github.com/dask/distributed/issues/5460 Cheers, Dominique
Dominique, Thanks for that link. If it's not too much trouble, would you please consider adding it back to your week in review as I used that to keep track of how many outstanding issues there were left before python 3.10 will become the default python. Question for you... If I were to install python 3.10 but leave /usr/bin/python3 still pointing to the python 3.8.12 installation, when Python 3.10 is finally released as the default python3 installation for the distribution, would the zypper dup which makes that change remove the python 3.8.12 installation and change the symlink to point to 3.10? I ask because a few years ago I had an older TW install and back when that machine was setup the install included python2 and python3 but when I built my new machine and did a fresh install python2 was not installed anymore so I'm trying to understand how the zypper dup process handles the transition to a new version. Thanks. Joe
Hi Joe, Am 07.03.22 um 17:56 schrieb Joe Salmeri:
If I were to install python 3.10 but leave /usr/bin/python3 still pointing to the python 3.8.12 installation, when Python 3.10 is finally released as the default python3 installation for the distribution, would the zypper dup which makes that change remove the python 3.8.12 installation No. Only if you remove orphans. and change the symlink to point to 3.10?
Yes. Note that we are talking about the system interpreter and its sitelibs. So all rpm packages depending on the primary python3 flavor should (TM) automatically follow the move and the rpm dependency management will install the dependencies of correctly flavored python packages. All single-spec multiflavor packages installed stand-alone will be unaffected. - Ben.
Unless I am misinterpreting your reply you are saying that if I install Python 3.10 but leave the default install as 3.8.12 that when TW decides to make 3.10 the system default it will LEAVE 3.8.12 installed but it will change /usr/bin/python3 to point to 3.10 at that time? Did I understand you correctly? If so, then if I do NOT install python 3.10 then when TW decides to move to 3.10 will it remove 3.8.12 and then install 3.10 or will it leave 3.8.12 like you said it would if I had installed it? I have been testing my python3 code with 3.10 in a VM to look for any issues but so far everything has worked but I only use 2 packages which are not included in the base python installation. Joe Thanks!
Dne 08. 03. 22 v 1:38 Joe Salmeri napsal(a):
Unless I am misinterpreting your reply you are saying that if I install Python 3.10 but leave the default install as 3.8.12 that when TW decides to make 3.10 the system default it will LEAVE 3.8.12 installed but it will change /usr/bin/python3 to point to 3.10 at that time?
Yes, that's the idea.
If so, then if I do NOT install python 3.10 then when TW decides to move to 3.10 will it remove 3.8.12 and then install 3.10 or will it leave 3.8.12 like you said it would if I had installed it?
The hope is for the former, but we have never tested it yet.
I have been testing my python3 code with 3.10 in a VM to look for any issues but so far everything has worked but I only use 2 packages which are not included in the base python installation.
Great! Basically the main hold-up before switching to 3.10 is https://github.com/dask/distributed/issues/5460 and I am just investigating whether we could overcome it somehow. Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 If only there were evil people somewhere insidiously committing evil deeds, and it were necessary only to separate them from the rest of us and destroy them. But the line dividing good and evil cuts through the heart of every human being. And who is willing to destroy a piece of his own heart? -- Aleksandr Solzhenitsyn: The Gulag Archipelago
On Mär 08 2022, code@bnavigator.de wrote:
No. Only if you remove orphans.
zypper dup removes orphans itself, due to the weakremover provides. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
On Tue, 2022-03-08 at 12:25 +0100, Andreas Schwab wrote:
On Mär 08 2022, code@bnavigator.de wrote:
No. Only if you remove orphans.
zypper dup removes orphans itself, due to the weakremover provides.
While that is true, this won't be a valid statement for Python 3.8 at the point we switch to python 3.10. I doubt we will drop all py 3.8 packages right away. So regular systems will install py 3.10 in parallel to the py 3.8 packages, and make /usr/bin/python3 point to /usr/bin/python3.10. At this time, users will have to remove py 3.8 manually (keep in mind that py 36 just fell out of TW these last days, so the weakremover logic will likely be a bit out) Cheers, Dominique
participants (5)
-
Andreas Schwab -
code＠bnavigator.de -
Dominique Leuenberger / DimStar -
Joe Salmeri -
Matěj Cepl