| ▲ | nbernard 5 hours ago | |
FYI, for the next time: with Debian, while rolling back is not supported, it often works. I had issues too with Trixie on a laptop (after upgrade everything became unbearably slow, probably due to an Intel graphic chip which was dropped by Mesa or some other library) and did a rollback to bookworm. IIRC, I only had to put back the old apt source entries then apt update and apt dist-upgrade... | ||
| ▲ | tremon 2 hours ago | parent [-] | |
> IIRC, I only had to put back the old apt source entries then apt update and apt dist-upgrade... The problem with rollbacks is not the packages themselves, that usually works without issues. The problem is with configuration and data items: if a package changes configuration format on upgrade (e.g. move from pkg.conf to pkg.conf.d), a downgrade will not restore the old version (e.g. rebuild pkg.conf from the .d snippets). Also, apt will not downgrade packages without prodding. At the very least, you would need --allow-downgrades. | ||