7 months ago
This tutorial explains how to upgrade to LMDE 4.
To upgrade to LMDE 4 you need experience with APT and the command line.
Upgrading to a newer package base is not trivial and it should not be performed by novice users.
You need to know how to type commands and read their output.
You also need to be experienced with APT. During the upgrade you'll need to understand the output of APT commands. You'll need to understand if a package needs to be removed, if it blocks the upgrade, if it conflicts with another package etc...
To apply all updates:
If anything breaks or if anything goes wrong during the upgrade, you can go back in time and revert all changes by restoring your latest system snapshot. Whatever happens, you're covered. You'll be able to restore your operating to this current state, either from within LMDE, or by launching Timeshift from a live Mint session (live DVD or live USB).
To create a system snapshot:
The Unofficial Debian Multimedia repository (deb-multimedia.org) is no longer used in LMDE 4. To prevent any packages conflicts during the upgrade you need to remove it and downgrade its packages back to Debian versions.
To remove the deb-multimedia.org repository:
sudo xed /etc/apt/sources.list.d/official-package-repositories.list)
To downgrade the multimedia packages back to Debian versions:
To remove the remaining multimedia packages:
Note: This will remove mint-meta-codecs and that's OK for now.
To install the upgrade tool, open a terminal and type:
apt install mintupgrade
To simulate an upgrade, open a terminal and type:
Then follow the instructions on the screen.
This command temporarily points your system to the LMDE 4 repositories and calculates the impact of an upgrade.
Note that this command doesn't affect your system. After the simulation is finished, your original repositories are restored.
The output shows you if the upgrade is possible, and if it is, which packages would be upgraded, installed, removed and kept back.
It is extremely important that you pay close attention to the output of this command.
Keep using "
mintupgrade check" and do not proceed to the next step, until you're happy with the output.
To download the packages necessary to upgrade to LMDE 4, type the following command:
Note that this command doesn't actually perform the upgrade itself, but just downloads the packages.
Note also that this command points your system to the LMDE 4 repositories (if you want to go back to LMDE 3 after using this command, you still can, with the command "
Use the "
mintupgrade download" command until all the packages are successfully downloaded.
Note: This step is non-reversible. Once you perform it, the only way to go back is by restoring a system snapshot.
To apply the upgrades, type the following command:
nice mintupgrade upgrade
Some packages either no longer exist in LMDE 4, or have a lower version than in LMDE 3. To guarantee they function properly, they need to be downgraded.
If you cannot upgrade please perform a fresh installation.
Generic instructions on "fresh upgrades" are also available at https://community.linuxmint.com/tutorial/view/2
apt policy mintupgrade".
sudo touch /etc/timeshift.json".
So far cleaner LMDE upgrade I've experienced, thanks! Even though mintupgrade check in my case crashed due to some unexpected error on the last stage (probably I just have too many packages from buster and buster-backports already), the subsequent download and upgrade went just fine.
What exactly is the issue around servlet libraries? How is it fixed? Thanks.
> "E. Alternatives
> If you cannot upgrade please perform a fresh installation."
When fresh installing on top of the previous installation, do not FORMAT the root partition, which also has usually the HOME partition.
Installing then allows the settings of the old setup to continue, as usual. If there are "absent" applications, these can be re-installed again. The settings will then generally be the ones that were on the original settings.
An easier GUI-almost way to add, remove & debug the Linux operating system is to use SYNAPTICS PACKAGE MANAGER (SPM).
This has an inbuilt bug detector & remover: "BROKEN".
SPM or Linux will sometimes tell us what the necessary CLI code is to repair our broken operating system.
Generally I find these CLI codes are similar to all Linux operating systems, so are in a code-fix text file, to be done frequently. Often the suggested "SUDO" is not mentioned.
: if LINUX ERRORS (no harm done)
sudo dpkg --configure -a
echo Y | sudo apt-get autoremove
echo Y | sudo apt-get -f install
echo Y | sudo apt-get install -f
sudo apt --fix-broken install
Re 2) - upstream bug in libservlet3.1-java breaks the upgrade, see https://bugs.debian.org/947844
Remove it via apt though... it's not really good to introduce dependency problems in your system.
went through the tutorial and it's working if done right:
1) It might be important for users, to move the 1st note about using the using the main-mirrors to the preparations section. Or add at least a note to read the tutorial completly first (as an user at irc got seemingly trapped by a mirror being out of sync).
2) Idk if it's been my lmde3 vm (which is a default installation with only minmal adjustments spice-vdagent, vim and geany) but I noticed that some *javaservlet* had to be removed here using sudo dpkg -r --force-depends
3) And in the course of the upgrade I did see some warnings about "folder xyz cant be removed, still containing files" - if this does matter