MX Linux Forum

If you see there is an update of +1900 packages, please DON'T upgrade. Its upgrades to buster which breaks your whole system. It removes systemd-shim, lightdm, netwwork-manager, and other important packages. If you do, don't logout before reinstalling the removed packages.

Here are few resent issues:
viewtopic.php?f=104&t=51379#p513797

viewtopic.php?f=97&t=51377

This only applies if you have MANUALLY changed "stretch" to "stable" in the debian.list sources file. which isn't an MX issue. Please so edit your original post title.

if a user has manually changed "stretch" to "stable" in their sources, then just change it back. If they did it once, they can do it again.

People should update, what they don't need to do is muck up with their sources. Then the Debian warranty applies "if you break it, you get to keep the two pieces" -- which is not that bad as it sounds it's a re-install with preserving the /home so at most a 20-30 min. affair but again, not recommended and self-inflicted.

MODERATOR

Please change your post title. It implies that users should not update which is not correct unless a user has manually changed his repo list as detailed in post #2

richb wrote: Mon Jul 08, 2019 2:41 pm MODERATOR
Please change your post title.

Done.

I genuinely want to know.. why did you change that source to "stable"? What was the thought pattern to do this?

Not being condescending, I am just trying to understand so maybe we can prevent others from doing this.

Eadwine Rose wrote: Mon Jul 08, 2019 3:02 pm I genuinely want to know.. why did you change that source to "stable"? What was the thought pattern to do this?

Not being condescending, I am just trying to understand so maybe we can prevent others from doing this.

I remember we had MX 16 users that had the same exact self-inflicted system borking back when Stretch became Stable. Note to self: put out a warning for MX 20 users in 2-3 years just before Bullseye goes to Stable.

LOL, but once MX 19 comes out with Buster repos, can't we just change the current MX 18.3 mx.list to match it and just jump to MX 19?

Read the explanation here as to why you are taking a big risk if you just switch repos after MX19 based on Buster is released.

https://mxlinux.org/mx-repos/

Master wrote: Tue Jul 16, 2019 6:05 am LOL, but once MX 19 comes out with Buster repos, can't we just change the current MX 18.3 mx.list to match it and just jump to MX 19?

You can if you want to break your system. Buster's changed from GTK2 to GTK2 among other things, and MX-19 will change from Xfce 4.12 to 4.14. Buster-based distros are not compatible with their Stretch-based counterparts, which is what caused problems for people who had modified their repositories so they said "debian stable" instead of the original "debian stretch". Once Buster became the new Debian Stable and they ran an update their systems were hosed. You'll need to install MX-19 from scratch (but you can preserve /home when you do.)

Please read https://mxlinux.org/blog/debian-stable-is-now-buster/

Mamma mia, this updating stuff is scary!

Sparky wrote: Tue Jul 16, 2019 7:52 am Mamma mia, this updating stuff is scary!

Not really. It just takes staying within the default repositories. And if using MXPI using the MX test repo for individual packages.

richb wrote: Tue Jul 16, 2019 7:55 am

Sparky wrote: Tue Jul 16, 2019 7:52 am Mamma mia, this updating stuff is scary!

Not really. It just takes staying within the default repositories. And if using MXPI using the MX test repo for individual packages.

+1
On the other hand updating my router can bring me out in a cold sweat!

The Bios does that for me *giggle*

I don't think that a reinstall, saving your home, for an upgrade plus installing other packages and local files from lists generated by aptik-gtk really takes much longer than an in-place upgrade, though I might try an in-place when MX 19 is released, just to see how much smoke comes out.