Also note that extremely old hardware (lets say more than 15- years old) might become problems with the very latest kernels, because they are optimised for new hardware and at some point drivers for old hardware get removed. And since it is a rolling release you cannot stay forever on an old kernel forever, so for extremely old hardware manjaro/arch would not be the first choice.
But anything up to 10-15 years should be ok.
Actually, it is not that much different in a non rolling release distro: Ubuntu has up to 5 years support, and here the kernel lasts pretty much that time too. But the rest of the system will be with newer packets in manjaro.
For example, i had a 2011 model thinkpad. It ran fine with ubuntu 14.04, than with 16 and 18, it had something small to fix on the 20.04 and it could not boot on the 22 release…probably some minor issue with a driver but i ditched the laptop anyway so i did not bother debugging, but it was not plug and play anymore.
I would recommend to always look at the log when installing/updating anything (the arrow near the apply button). It actually says if there are pacnews. But the tool is also nice. It is actually meant for people who do not like reading… logs, forum, tutorials…and need something “in the face”.
Well, there’s always Debian Archaic and Debian Prehistoric.
That’s Stefano, one of the lead developers. But no, it doesn’t automate the process — that’s not possible — but it will notify you when there are .pacnew files and will let you merge them.
The package is called manjaro-pacnew-checker and it’s in the repository.
That’s not going to work for people who update their system by way of the pamac GUI — which they shouldn’t, but hey, go and try changing culture…
The best way to update your system is always from a tty, while completely logged out of the GUI environment. That way, there will be fewer shared libraries in use that would be overwritten. And you must first always update the system packages, and only afterwards the AUR stuff, Snaps, FlatPaks and whatever else have you.
I don’t have so much experience with meld as a program, but as for the pacman changes themselves, the new file is the way to go. Community repo is gone and the signature requirement only causes problems sometimes so it got removed from the default config too. So you did right deleting the green stuff.
This is pretty confusing to me.
It sounds like your suggesting to keep the new Pacnew and remove the old file.
Taking a closer look at the files side by side in Meld, I think you merge the new file (on the right) changes to the old file (on left) and save. This way all of the changes are now incorporated into the old (and “proper”) filename.
Sorry for having to ask so many questions, I am not a Linux-Jedi but I am making a concerted effort to learn.