MX Linux Forum

Sorry for late reply.

What stood out to me is the statement "MX broke on me few times on pretty much fresh install while doing full apt upgrade" which means running an "apt full-upgrade"/"apt-get dist-upgrade" and hoping for the best. From man apt-get(8), which of course we all have memorized ...

Actually, MX broke on me few times on pretty much fresh install while doing full apt upgrade with +300 upgradable packages, with zero involvment from my side, nor even touching repos.
And by other repos, I mean debian sid and trixie.

Don't get me wrong, MX Is amazing distibution, that I still have ...

I recently realized that very little thought is given to APT's inner configuration by most distributions. Many users have unintentionally rendered their systems unusable because APT, due to a lack of proper configuration, mistakenly identifies critical packages as unnecessary and removes them ...

Oh, right!

Thanks, it appears that are responsible for corresponding paths :)
Thanks alot

Hey, which packages are responsible for and ?

Thanks

That would be cool, and I'll definetly gonna have some suggestions regarding recommended packages :)

Well I already have tons of stuff done up to v6, and porting that would take some considerable time, while v6 is also perfectly healthy and fine with all it has at the moment.
Edit: I actually pretty much already ported entire v7 onto healthy previous version, so it was month to create, and only 3 ...

Thanks fehlix .

I think I will actually listen to your advice and start again.
(Im building distro out of MX23.2 Minimal, and Im already at Alpha v7, so starting over again from healthy Alpha v6 is not that big of a deal. I'd loose only a month or so of work, but at least i learned very very ...

To be fair.
I suspect both trying to add Ubuntu's PPA's, and trying to add Debian testing...
Im using both apt-get and nala (instead of apt).

Once when i tried to install some newer version of package that was supposedly available in debian testing, I came across this very weird behavior from nala ...

The thing is im not sure what caused the issue to begin with, probably adding some broken repos, and now its stuck this way.
I literally transplanted healthy files from source os, and it still won't get over this issue.

Trying to repeat the action that broke it to analyze is pretty much impossible ...