While upgrading tonight, I got the following error:
serious bugs of libc6 (2.40-7 → 2.41-2) <Resolved in some Version>
b1 - #1099166 - libc6: Cannot co-install at least amd64 and i386 instances (Fixed: glibc/2.41-3)
Sounds like it’s not applicable on the reform to me, but if I’m wrong, might be tragically bad.
I opted-out of continuing. Is anyone else seeing this, or does anyone know if it’s OK to install with the reported bug?
I upgraded and I haven’t had any issues. I wouldn’t worry about it unless you are trying to install libcs for multiple architectures side by side. This isn’t an error.
Apt appears to be holding libc6 and libc6:i386 back for me.
It was applicable if you installed foreign architecture versions of libc6 and then only if you installed the wrong combinations. If you had done so, dpkg would’ve complained about file conflicts.
Luckily, the problem was quickly taken care of and a version that has this bug fixed should now be in unstable.
I never went out of my way to do so, but maybe a podman install could have pulled it in?
In any case, @josch you are correct, it seems to have been corrected, an attempt this morning went by without that error.
(There is a chromium bug listed, but that feels much easier to recover from if it goes badly, so I just did it)
You can always use the bug number that you are shown and go to https://bugs.debian.org/BUGNUMBER, replacing BUGNUMBER by the seven digit number you are shown but without the hash in front of it. This will get you to the bug description and you can check if the issue is one that you might be affected by or not.
Neat, I usually live in the rpm/dnf world, so I didn’t know about that. Thank you.
Quick similar question: There are an increasing number of packages that are marked “Not upgrading” I assume that there’s some dependency that is holding those back as well, is there an easy way to look those up too? (There is no number jumping out at me)
Can you give more context? What is the command you are running?
sudo apt update ; sudo apt upgrade ;
... (nothing out of the ordinary looking) ....
42 packages can be upgraded. Run 'apt list --upgradable' to see them.
Notice: Missing Signed-By in the sources.list(5) entry for 'https://mntre.com/reform-debian-repo'
Notice: Some sources can be modernized. Run 'apt modernize-sources' to do so.
Upgrading:
evince evince-common gstreamer1.0-plugins-good gstreamer1.0-pulseaudio libevdocument3-4t64 libevview3-3t64
Not upgrading:
libkf6colorscheme6 libkf6iconwidgets6 libqt6dbus6 libqt6qml6 libqt6quickwidgets6 libqt6waylandcompositor6 minetest-data qt6ct
libkf6configwidgets6 libkf6windowsystem6 libqt6gui6 libqt6qmlmodels6 libqt6sql6 libqt6widgets6 qt6-gtk-platformtheme
libkf6globalaccel6 libkirigamiplatform6 libqt6network6 libqt6quick6 libqt6sql6-sqlite libqt6wlshellintegration6 qt6-qpa-plugins
libkf6iconthemes-bin libqt6concurrent6 libqt6opengl6 libqt6quickcontrols2-6 libqt6svg6 libqt6xml6 qt6-svg-plugins
libkf6iconthemes6 libqt6core6t64 libqt6printsupport6 libqt6quicktemplates2-6 libqt6waylandclient6 minetest qt6-wayland
Summary:
Upgrading: 6, Installing: 0, Removing: 0, Not Upgrading: 36
Download size: 4,231 kB
Space needed: 524 kB / 1,831 GB available
Let me know if I can clarify anything.
You are running unstable. In contrast to running Debian stable, large package transitions are the norm. apt upgrade takes care not to remove any packages, so you will not be able to fully upgrade a Debian unstable system with apt upgrade. Instead use apt full-upgrade for Debian unstable. That’s the same command you would use to upgrade from one Debian stable release to the next.
Ah, thanks. I didn’t understand the difference between the two. Learning new things every day. That’s why I jump into some of these things.