> > # apt remove -s libc6 > > DO NOT do this. > > Downgrade it. DO NOT remove it and then hope to reinstall it later. > Removing libc6 will break everything. > > You seem to be flailing, so let me spell this out as explicitly as > possible. When I say "downgrade a library package", I mean: > > 1) Download the .deb file for the bookworm(-security) version of the > library package. > > 2) Run "dpkg -i libc6_whatever.deb". > > 3) When you inevitably get dependency conflicts, download the additional > library packages that need to be downgraded at the same time, and add > them to the list. > > 4) dpkg -i libc6_whatever.deb libwhomever.deb .... > > 5) Repeat until it works. > > 6) Helpful post-mess cleanup commands include "dpkg --configure -a" and > "apt-get -f install". (Yes, that last one has install with no package > names.) > > Apt is NOT built for downgrading. If you happen to get any positive > results from an apt command that involves downgrading, you can consider > that a pleasant surprise. Usually you need to invoke dpkg directly.
Ah I see, I did not realise that's what you meant by downgrading it, thanks. So once I've done this dpkg -i to install a package, I can do that without removing the old one first? And, once I've hammered a package into place with dpkg, in the future, will apt take it into account as a dependency of things already installed even though apt itself didn't install or rather downgrade the package itself? The fact that I am dpkg installing it over a package that apt itself installed, perhaps this keeps apt happy? Thanks for your help. I use apt all the time to do upgrades but rarely do I ever need to get into weeds with it. It's a bit of a black box to me.
signature.asc
Description: PGP signature
