Ubuntu 24.04 upgrade: Difference between revisions

Latest revision as of 15:08, 17 April 2025

Your current OS release must be up-to-date:

mh-update-ubuntu
# (ensure all repos are working)
# reboot

Now you can kick it off:

# you can connect via direct proxmox shell (not ssh) but seems robust either way
sudo do-release-upgrade

Typical selections:

sudo do-release-upgrade
# mail server: none
# change sudoers? N (default)
# Keep local sshd_config
# remove local packages? Y
# restart? Y

Steps to perform on all boxes

move new /etc/systemd/networkd.conf out of the way so we can stow our (IMPORTANT) version:

sudo su -
cd /etc/systemd
mv mv networkd.conf networkd.conf.orig-24.04
Ctrl-D
setup_stow.sh # should create /etc/systemd/networkd.conf symlink
sudo service networkd-dispatcher restart

re-add custom apt repos via setup_stow.sh
- NOTE: all custom apt repos are removed by upgrade, but it kindly replaces jammy with noble so they can often easily be re-enabled
- Always edit files in config/ubuntu/*/etc/apt/sources.list.d then apply symlinks via setup_stow.h
- Always opt for sources file not list file when possible; see qtb notes below for a specific example

Upgraded boxes

matryoshka
morosoph
bandit
dev2 (GUI)
abtdev1 (GUI)
cast (GUI)

TODO:

positronic needs migration to postfix (from 13 > 17!) as v13 is deprecated now
glam, lots of goo there

NOTES

bandit

bandit do-release-upgrade seemed to go without any trouble, but it takes a WHILE... like, half an hour or more...

looks like i killed snapd on bandit, and that was preserved, yes!
re-add qbt apt repo - we should now use SOURCES not LIST, it is the more modern solution (has more metadata, including a key)

sudo su -
cd /etc/apt/sources.list.d
mv qbittorrent-team-ubuntu-qbittorrent-stable-jammy.list ~/backup
mv qbittorrent-team-ubuntu-qbittorrent-stable-jammy.sources qbittorrent-team-ubuntu-qbittorrent-stable-noble.sources
ne qbittorrent-team-ubuntu-qbittorrent-stable-noble.sources
# the upgrade already replaced jammy with noble, NICE - we just need to ENABLE IT!  SWEET!

AFTER ensuring setup_stow.sh and Samba are working (see above), re-add my custom qbt service:

sudo systemctl enable qbittorrent-nox.service
sudo systemctl start qbittorrent-nox.service

OLD notes

Upgrading gnome can be troublesome shit from command line. Do this:
- exit i3, boot into Gnome
- hit Alt, type Software Updater, go through options to upgrade

Either:

sudo do-release-upgrade

Or:

sudo apt install update-manager
sudo update-manager &

Nautilus crashes (yep, unreal right?); i tried alternatives and they are all BLOATed; currently using spacefm
- whoa, this appears to have been (maybe) because my VM host was not set to HOST - i found out when an ig container kept crashign with "bad CPU"

check Samba, it "broke bad" on bandit - but i fixed it by adding SMB to m user in hive UI, hrmmm, so I don't know why it broke with 24.04...

@@ Line 1: / Line 1: @@
-* Ensure all repos are available
+* Your current OS release must be up-to-date:
+ mh-update-ubuntu
+ # (ensure all repos are working)
+ # reboot
+* Now you can kick it off:
+ # you can connect via direct proxmox shell (not ssh) but seems robust either way
+ sudo do-release-upgrade
+* Typical selections:
+ sudo do-release-upgrade
+ # mail server: none
+ # change sudoers? N (default)
+ # Keep local sshd_config
+ # remove local packages? Y
+ # restart? Y
+=== Steps to perform on all boxes ===
+* move new /etc/systemd/networkd.conf out of the way so we can stow our (IMPORTANT) version:
+ sudo su -
+ cd /etc/systemd
+ mv mv networkd.conf networkd.conf.orig-24.04
+ Ctrl-D
+ setup_stow.sh # should create /etc/systemd/networkd.conf symlink
+ sudo service networkd-dispatcher restart
+* re-add custom apt repos via setup_stow.sh
+** NOTE: all custom apt repos are removed by upgrade, but it kindly replaces jammy with noble so they can often easily be re-enabled
+** Always edit files in config/ubuntu/*/etc/apt/sources.list.d then apply symlinks via setup_stow.h
+** Always opt for sources file not list file when possible; see qtb notes below for a specific example
+==== Upgraded boxes ====
+* matryoshka
+* morosoph
+* bandit
+* dev2 (GUI)
+* abtdev1 (GUI)
+* cast (GUI)
+TODO:
+* positronic needs migration to postfix (from 13 > 17!) as v13 is deprecated now
+* glam, lots of goo there
+== NOTES ==
+=== bandit ===
+bandit do-release-upgrade seemed to go without any trouble, but it takes a WHILE... like, half an hour or more...
+* looks like i killed snapd on bandit, and that was preserved, yes!
+* re-add qbt apt repo - we should now use SOURCES not LIST, it is the more modern solution (has more metadata, including a key)
+ sudo su -
+ cd /etc/apt/sources.list.d
+ mv qbittorrent-team-ubuntu-qbittorrent-stable-jammy.list ~/backup
+ mv qbittorrent-team-ubuntu-qbittorrent-stable-jammy.sources qbittorrent-team-ubuntu-qbittorrent-stable-noble.sources
+ ne qbittorrent-team-ubuntu-qbittorrent-stable-noble.sources
+ # the upgrade already replaced jammy with noble, NICE - we just need to ENABLE IT!  SWEET!
+* AFTER ensuring setup_stow.sh and Samba are working (see above), re-add my custom qbt service:
+ sudo systemctl enable qbittorrent-nox.service
+ sudo systemctl start qbittorrent-nox.service
+=== OLD notes ===
-Fucking google key needs bump:
- curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key --keyring /usr/share/keyrings/cloud.google.gpg add -
 * Upgrading gnome can be troublesome shit from command line.  Do this:
 ** exit i3, boot into Gnome
 ** hit Alt, type Software Updater, go through options to upgrade
+Either:
+ sudo do-release-upgrade
+Or:
+ sudo apt install update-manager
+ sudo update-manager &
-OLD Notes from 22.04, for review...
+* Nautilus crashes (yep, unreal right?); i tried [https://wiki.gentoo.org/wiki/File_managers alternatives] and they are all BLOATed; currently using spacefm
+** whoa, this appears to have been (maybe) because my VM host was not set to HOST - i found out when an ig container kept crashign with "bad CPU"
-* these were replaced (i put old ones in ~/backup/) and need review:
- /etc/systemd/networkd.conf
- /etc/sudoers
- /etc/ssh/sshd_config
- /etc/i3/config
- /etc/i3/config.keycodes
-After fixing networkd.conf, you should restart the service, but that isn't enough, you need to disconnect from wired and reconnect to wired before changes are applied.
-/etc/i3/config.keycodes has some newer foo that I need to vet against my i3 config.  Esp this:
+* check Samba, it "broke bad" on bandit - but i fixed it by adding SMB to m user in hive UI, hrmmm, so I don't know why it broke with 24.04...
- # Start XDG autostart .desktop files using dex. See also
- # https://wiki.archlinux.org/index.php/XDG_Autostart
- exec --no-startup-id dex --autostart --environment i3