Tumbleweed - Review of the week 2020/08
Dear Tumbleweed users and hackers, This week we managed to do the impossible: despite missing one snapshot 0220), we STILL published 7 snapshots (0217, 0218, 0219, 0221, 0222, 0223, and 0224). Of course, this just happens by coincidence, as 0217 could only be released late evening and 0224 happens to come out already before writing the weekly review. And what did those snapshots bring us? See for yourself: * KDE Plasma 5.24.1 (0217) & 5.24.2 (0224) * KDE Frameworks 5.91.0 * Linux kernel 5.16.10 (simpledrm disabled again) * systemd 249.10 * systemd packaging changes: systemd-sysvinit will be renamed to systemd-sysvcompat: most users won’t need it (sysv support is minimized anyway, and Tumbleweed no longer ships any sysv init script) * Mozilla Firefox 97.0.1 * expat 2.4.6 * tigervnc 1.12.0: the ‘vncserver’ script no longer exists, see https://github.com/TigerVNC/tigervnc/blob/master/unix/vncserver/HOWTO.md That’s pretty cool and everything reported last week as coming (except the gcc12 and python long-lasting efforts) have thus been delivered. As usual, we don’t stop there, and staging projects are already prepared with these updates: * Linux kernel 5.16.11 (also addressing build fails with gcc12) * Mesa 21.3.7 * Python 3.6 interpreter will be removed (We have roughly 45 python36-FOO packages left) * Python 3.10 as the distro default interpreter (a bit down the line, after py36 is done) * GCC 12 introduction has started to be as ready as possible for when the upstream release happens. Cheers, Dominique
Am 25.02.22 um 18:34 schrieb Dominique Leuenberger / DimStar:
* systemd packaging changes: systemd-sysvinit will be renamed to systemd-sysvcompat: most users won’t need it (sysv support is minimized anyway, and Tumbleweed no longer ships any sysv init script)
Since I didn't have anything in /etc/init.d/, I removed the package altogether. But then reboot landed my in a rescue shell. Reason: the default target was still set to runlevel5.target, which no longer existed. I can't remember changing the default target, but my installation goes back a few years. So who knows. So as a recommendation for all who consider removing this package: check first whether you have /etc/systemd/system/default.target and what it points to, alternatively run "systemctl get-default". If it's something like graphical.target or multi-user.target you should be safe, if it's something like runlevel*.target, change it to one of the former or just remove it (then systemd will use /usr/lib/systemd/system/default.target -> graphical.target). Aaron
On 26.02.22 16:52, Aaron Puchert wrote:
So as a recommendation for all who consider removing this package: check first whether you have /etc/systemd/system/default.target and what it points to, alternatively run "systemctl get-default". If it's something
systemctl get-default is not useful in this case (leap 15.3 example): server:~ # systemctl get-default multi-user.target server:~ # ls -l /etc/systemd/system/default.target lrwxrwxrwx 1 root root 40 Dez 21 2013 /etc/systemd/system/default.target -> /usr/lib/systemd/system/runlevel3.target server:~ # ls -l /usr/lib/systemd/system/runlevel3.target lrwxrwxrwx 1 root root 17 Feb 1 23:06 /usr/lib/systemd/system/runlevel3.target -> multi-user.target So it's probably worth a bug report that removing systemd-sysvcompat leaves old systems unbootable. -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
Am 28.02.22 um 08:51 schrieb Stefan Seyfried:
systemctl get-default is not useful in this case (leap 15.3 example):
server:~ # systemctl get-default multi-user.target server:~ # ls -l /etc/systemd/system/default.target lrwxrwxrwx 1 root root 40 Dez 21 2013 /etc/systemd/system/default.target -> /usr/lib/systemd/system/runlevel3.target server:~ # ls -l /usr/lib/systemd/system/runlevel3.target lrwxrwxrwx 1 root root 17 Feb 1 23:06 /usr/lib/systemd/system/runlevel3.target -> multi-user.target
Thanks for pointing this out! It should have occurred to me though that this looks through symlinks recursively. (Of course not if the targets are gone, which is why I didn't see it anymore.)
So it's probably worth a bug report that removing systemd-sysvcompat leaves old systems unbootable.
Filed <https://bugzilla.opensuse.org/show_bug.cgi?id=1196567>. Fully agreed, this should be easy to safeguard against, and it appears that >1 installations still use a runlevel* target as default target for whatever reason. Aaron
participants (3)
-
Aaron Puchert -
Dominique Leuenberger / DimStar -
Stefan Seyfried