# review and purge older kernel if the new one boots properly do apt purge $(deborphan -n | grep -v python-is-python2) done While deborphan -n | grep -v python-is-python2 | grep -q. Rm -f /etc/apt//testing.list &Īpt purge $(dpkg -l | awk '/^rc/ ') # purge removed packagesĪpt purge $(deborphan -guess-dummy | grep -v python-is-python2) Rm -f /etc/apt/preferences /etc/apt/preferences.d/* & : Check for pinned, on hold, packages, and possibly disable & Perform any pending upgrade and clear out old pins: puppet agent -disable "running major upgrade" & home/anarcat/src/koumbit-scripts/vps/clean_conflicts & : look for dkms packages and make sure they are relevant, if not, purge. ![]() Tar cfz /var/backups/pre-bullseye-backup.tgz /etc /var/lib/dpkg /var/lib/apt/extended_states /var/cache/debconf $( & echo /var/lib/aptitude/pkgstates ) &ĭpkg -get-selections "*" > /var/backups/dpkg-selections-pre-bullseye.txt &ĭebconf-get-selections > /var/backups/debconf-selections-pre-bullseye.txt Sudo ttyrec -e screen /var/log/upgrade-bullseye.ttyrec Sudo chmod 600 /var/log/upgrade-bullseye.ttyrec & Sudo touch /var/log/upgrade-bullseye.ttyrec & : create ttyrec file with adequate permissions & Sudo apt install ttyrec screen debconf-utils deborphan apt-forktracer & Preparation: : reset to the default locale Privilege of having a console), you may want to upgrade SSH firstĪs it has a longer downtime period, especially if you are on a flaky IMPORTANT: if you are doing this procedure over SSH (I had the Then those changes get appliedĪfter a reboot. Upgrade process (without it, configuration file changes stop the I use aĬlean-conflicts script to do this all in one shot to shorten the In particular, it runs almost completely unattended: configurationĬhanges are not prompted during the upgrade, and just not applied atĪll, which will break services in many cases. It has been crafted byĪnd for experienced system administrators that have dozens if not Do NOT follow this procedure unless you are familiar with theĬommand line and the Debian upgrade process. This procedure is designed to be applied, in batch, on multiple ![]() The other documents can be found in the parent Personal, living document that I have started keeping back when I It does not hope to replace the official documentation: it is a New version, issues I have stumbled upon (and possibly fixed), and This document contains my upgrade procedure, notable changes in the Update: this procedure was tested first on my workstation This time I feelĪlmost late because it seems we'll be releasing in almost a month now To upgrade slightly before or during the freeze. It's Debian major upgrade time again! My personal policy is generally
0 Comments
Leave a Reply. |