8 years ago
This tutorial explains how to upgrade LMDE 1 "Debian" to LMDE 2 "Betsy".
It is assumed that:
As usual, please make sure to:
First, we need to point the computer at the LMDE 2 "Betsy" repositories.
As root, edit /etc/apt/sources.list.d/official-package-repositories.list to make it look like this:
deb http://packages.linuxmint.com betsy main upstream import
deb http://http.debian.net/debian jessie main contrib non-free
deb http://http.debian.net/debian jessie-updates main contrib non-free
deb http://security.debian.org jessie/updates main contrib non-free
deb http://www.deb-multimedia.org jessie main non-free
deb http://extra.linuxmint.com betsy main
Now, we update the cache (and upgrade repository keyrings) so the computer is aware of what's available in Betsy. In a terminal, type:
apt install debian-archive-keyring deb-multimedia-keyring
To avoid conflicts during the upgrade, we install a few packages prior to upgrading. In a terminal, type:
apt install sysvinit-core adwaita-icon-theme blueberry
In the MATE/Cinnamon settings, it is recommended to turn off anything that might trigger the screensaver. By the time the upgrade is downloaded, the screen might be locked when it's time to upgrade the screensaver itself.. this is usually ok, but you never know, it's better to be safe than sorry :)
Now that we're all ready, we can perform the upgrade. In a terminal, type:
Review the information in details. In particular pay special attention to the list of packages being removed. If that looks ok, confirm the command and go for it.
First, check that the upgrade finished completely. Type:
It should tell you that everything is now up to date. If it doesn't, it means the system isn't fully updated yet.
The command below also is useful, if you're stuck with conflicts and want to resolve the APT cache:
apt install -f
Finally, make sure you've a core set of packages installed, depending on your edition you can perform either of these commands:
apt install mint-meta-debian-cinnamon
apt install mint-meta-debian-mate
Don't forget to reboot the computer after everything is finished.
I followed the steps above. Indeed took a long time, and I ended up with a system that booted - ssh and VNC into it were OK - but the display/X/video side on the console was trashed. Since my / and /home are on separate partitions it ended up being simpler - and quicker - to install LMDE 2 afresh. So far I have only had to re-install a few things, and the net result is that my system has experienced some long overdue "spring cleaning".
It is tempting to go back to pure Debian, but it is also really nice to have my video and audio Just Work in Mint, with out the typical Debian non-free twiddling. Probably a question for the forums, but what components in Mint/LMDE prevent the truly rolling/continuous updates that are part of core Debian?
Perfect tutorial, thank you!
After a few envisaged glitches with the nVidia driver, and manually installing mint-info-debian-mate ('lsb_release -a' did not reflect the new version) I have a perfectly working system!
I find it much more responsive than LMDE 1!
It's a pleasure working on this laptop again!
LMDE 2, 32bit, Mate
I have done this upgrade yesterday (26/07/16) Although it went well at the end of the day, it was really a painful process and took me hours to complete. I had to fix broken packages, uninstall things, reinstall others, play with the NVIDIA drivers, etc. but I did survive! Everything seems to be working just fine! Happens to be the very first time that I have done an actually working upgrade! Thanks Clem!
In my experience, upgrading is usually a bad idea. I tried this upgrade yesterday (July 9, 2016). After a reboot, there were errors in the startup log and the login page never appeared. My next step was to clean install LMDE 2 and restore my files (well, some of the data files at least) from backup.
The good news? With LMDE 2 installed, the unsolvable problem I had with the GIMP on LMDE 1 seems to have been fixed.
The upgrade procedure works like charm. Although the first attempt failed due to the lack of space, I could boot the old kernel, free some space and restart the upgrade. Which then was successfully completed.
thank you very much for your howto. Everything was going nice -- apt reported it wants to use 1.4G of my ~4G at the moment available space, and in no time the HD was used up completely -- upgrade terminated with errors. But the worst thing is that I followed a suggestion from your blog
and used Redo for backing up my system... I backed up my system partition only, because I was not going to mess up neither with /home nor with /windows. It turned however out that Redo can only backup one single partition but it can not restore this partition to the destination partition of user's choice. So an easy restore will not work now. :-) Please, modify you blog post and remove any mentioning of this Redo software because it is not practical with today's TB sized hard drives.
Does this or would this also pertain to the KDE versions as well? Can this be done to say;
Qiana to Rafaella....great work btw.....been a long while....cheers mate! :D
It seems Software Selection app is broken; if I select any other mirror server (or click Restore default...), it rewrites official-package-repositories.list file so its sources again points to "debian" instead of "betsy" and "testing" instead of "jessie" repos.
As it now obviously pointed to the wrong repos, apt complained about InRelease being over 500 days old and refused to use the sources. The only cure was of course to replace again all that sources to those posted in this article.
Finally a tutorial that tells me that my sources should be updated first.
I followed the tutorial to upgrade from LMDE1 to LMDE2. I couldn't get Grub to use the new 3.16.0-4 linux image (probably because I've used wheezy-backports previously to do an upgrade). I restored the system back to LMDE1 and repeated all the steps except 'dist-upgrade'. What are the main implications if I just do a general package upgrade (after changing the repo to betsy and jessie) without a corresponding dist-upgrade?
@lmsluz: mintupdate-debian is auto-replaced with mintupdate on upgrade
@jomaed: various parts of systemd (parts that are not related to the init system) are always installed in modern Mint systems.
What you need to check is whether you have systemd-sysv package installed - that makes systemd the init system.
It looks great but I have an isue... I don't know why/how but I have systemd installed in my LMDE 1, and I have not done anything to change my init. So, I guess I'll have to wait a way to upgrade with systemd or do a fresh install.
Instead of apt there is enough apt-get?
Very good, all went fine. Thanks Clem and all the LM team.
You are a wise devoloper ... You start mint project ... and what You write is always right ... good work ...
Is there all that much value in an upgrade? With a separate home partition, and a list of installed packages (`dpkg --get-selections > installed_packages.txt`) I can have a clean install up-to-speed in a hour or so; I can't help feeling that this would take longer and be more likely to throw up issues I'd have to dig into. Just throwing it out there as an option some folk might consider, if they've not already.
good job Clem :D
Here we go, the path is now open. Sorry it took long. Good luck everybody.
Some troll even demotes Clem's article :-D