{"id":33518,"date":"2025-07-27T13:29:56","date_gmt":"2025-07-27T13:29:56","guid":{"rendered":"https:\/\/garfnet.org.uk\/cms\/?p=33518"},"modified":"2025-08-18T21:02:34","modified_gmt":"2025-08-18T21:02:34","slug":"upgrade-debian-12-bookworm-to-debian-13-trixie","status":"publish","type":"post","link":"https:\/\/garfnet.org.uk\/cms\/2025\/07\/27\/upgrade-debian-12-bookworm-to-debian-13-trixie\/","title":{"rendered":"How to upgrade Debian 12 (Bookworm) to Debian 13 (Trixie)"},"content":{"rendered":"

Debian version 13, aka Trixie is due to be declared “stable” 2025-08-09. I’ve been using Trixie as “testing” for a couple of years now and have found it very good indeed. So much so that we are already upgrading our Bookworm machines to Trixie. In all cases so far, this has proven a relatively smooth and straightforward process. So if you are considering giving this upgrade a try, here’s a good way to do it…<\/strong><\/p>\n

Important<\/h2>\n
    \n
  1. Back-up your data. Debian upgrades are generally pretty reliable but better safe than sorry<\/em>.<\/li>\n
  2. This process requires you to have sudoers rights.<\/li>\n
  3. This article assumes you have a standard Debian stable installation with no third party repositories. If you are using third party software, then you should check with the aforementioned third parties that it has a version of its software available for the new version of Debian. For example, at time of writing, there is no version of ISPConfig<\/a> for Debian Trixie yet. Though I would wager that Till Brehm<\/a> and his team are hard at work on it.<\/li>\n
  4. I’m also assuming you are running the KDE Plasma desktop. If you are running some other desktop, then the parts at the end relating to KDE may not apply to you.<\/li>\n<\/ol>\n

    Also note that your dialogues and windows may look slightly different from mine, but the operations you need to undertake are exactly the same.<\/p>\n

    Preparing for Upgrade<\/h2>\n

    Firstly you need to ensure that your current Debian is up to date. So open a terminal window (Konsole or similar), type the following and hit the return key. It will ask you for your sudoers password…<\/p>\n

    sudo apt update && sudo apt full-upgrade<\/pre>\n
    Once that is complete, some<\/em> people like to reboot at this stage. Generally I don’t bother unless there was a kernel upgrade when I ran the last apt full-upgrade.<\/p>\n
    Edit your sources file<\/h2>\n
    Then you need to open and edit your \/etc\/apt\/sources.list file. You may use virtually any text editor with root permissions, including nano, gedit or my personal favourite: kate. However, if you use kate, you do not<\/strong><\/em> actually open the file as root because kate will not run as root. Instead you will be given the option to save<\/em> the file with root privileges when you actually save it, c\/w a password dialog.<\/p>\n
    Once you have opened \/etc\/apt\/sources.list you need to replace every instance of the string “bookworm” with “trixie”, then save the file. One of the reasons I like kate is because I can use its integral find and replace<\/em> feature to perform tasks such as this:-<\/p>\n
    \"Editing<\/a>
    Editing \/etc\/apt\/sources.list in kate, and using its ‘find and replace’ feature.<\/figcaption><\/figure>\n
    When you save the file in kate, you will be presented with a standard password dialogue similar to this:-<\/p>\n
    \"Kate<\/a>
    Kate (KDE Advanced Text Editor) save as root dialogue, asking for root privileges, in order to save the file.<\/figcaption><\/figure>\n
    Once your modified \/etc\/apt\/sources.list file is successfully saved, you need to tell your system to look at the new repositories:-<\/p>\n
    sudo apt update<\/pre>\n
    When you do this, you should notice all the former mentions of “bookworm” have been replaced with “trixie”. If that is the case then you may move on to the next stage, a simple upgrade.<\/p>\n
    Perform simple upgrade<\/h3>\n
    Simply type the following into a terminal and hit return:-<\/p>\n
    sudo apt upgrade<\/pre>\n
    It will now download all the debian packages required for this part of the upgrade. Depending on your internet connection, this may take some time and could involve over 1000 *.deb packages. Once the packages have downloaded the screen will show a long list of changes in a section called “apt-listchanges”. You may wish to read this. Once you have finished reading simply press “q” (for quit) to continue<\/em> with the upgrade. This may seem a little counter intuitive. But you are actually quitting the “apt-listchanges”, not<\/strong><\/em> the actual upgrade.<\/p>\n
    As the basic upgrade continues, you may observe a number of ‘dpkg warnings<\/em>‘. Don’t panic. Debian upgrades are quite chatty. They are also remarkably good at sorting themselves out. It may also ask you if you want to restart various services and daemons automatically. If you are upgrading locally, you may select “yes”. If you are upgrading remotely, it is generally better to select “No”:-<\/p>\n
    \"Command-line<\/a>
    Command-line dialogue asking if you wish to restart services automatically?<\/figcaption><\/figure>\n
    Perform full upgrade<\/h2>\n
    Assuming the basic upgrade completes successfully, you may now continue to the full upgrade:-<\/p>\n
    sudo apt full-upgrade<\/pre>\n
    During this process it may ask you if you wish to replace configuration files with maintainer’s versions. Generally it is safest to select the default, i.e. keep<\/strong><\/em> your existing modified config file, unless you have a very good reason not to.<\/p>\n
    Clearing up<\/h2>\n
    Assuming the previous stage completed successfully, we now need to clear-up. This involves removing redundant packages from the system. Debian provides a first-class tool for doing this. However it’s up to you whether you do this now, or after you reboot the machine. To autoremove all the redundant old packages and free-up some hard-disk space, use this command:-<\/p>\n
    sudo apt autoremove<\/pre>\n
    Reboot<\/h2>\n
    Almost there – now you really do need to reboot…<\/p>\n
    sudo reboot<\/pre>\n
    Almost there<\/h2>\n
    Your machine should reboot normally, albeit a bit slower than normal, as it sorts itself out. Boot speed should return to normal during subsequent reboots. If you are running Gnome or some other desktop, then you can probably stop here. However if you are running KDE Plasma, then it’s likely you may have some extra work to do. That’s because this Debian upgrade includes a massive<\/strong> upgrade to KDE Plasma, from version 5.x to version 6.x. This KDE upgrade has proven significantly less problematic than earlier upgrades. Nevertheless there are still a few annoyments. The following link explores and fixes the issues I encountered…<\/p>\n
    Issues upgrading to KDE Plasma 6 from Plasma 5<\/a><\/p><\/blockquote>\n