Why all these questions in the package manager asking if I want to keep the old instead of the new?

[cscs]

Sorry, guess I mixed it with another poster that had mentioned english was not first language.

[phmo]

My Kernel is now:

6.1.71-1-MANJARO

[anon6547204]

@cscs

But I really dont know what else to offer.

How about this (meld required):

sudo DIFFPROG=meld pacdiff

It displays all pacnew-files one after the other and offers options.

[phmo]

Oh, I am sorry. Now I have updated it.

[cscs]

Because its fundamentally wrong.

pacdiff -s passes sudo, actually sudoedit to temporary files and applies the changes using sudo afterwards …

What you are doing would be going around for no reason and all drawback
(such as feeding sudo itself to the environment variable, and eventually the graphical application)

You can sudo meld file1 file2 … but you shouldnt.

Just the same as you shouldnt sudo kate and have really no reason to.
(besides the mortal sin of starting a gui application with sudo … kate will ask for permissions if you try to save to a privileged location, so ‘sudo kate’ would be double silly)

Use the tools.

pacdiff -s

[phmo]

No problemo !

[anon6547204]

Hm, then please tell me a better solution. I have been able to organize the pacnew-files quite well in Arch, EndeavourOS and Manjaro over the last 4 years. I’m open to suggestions …

[cscs]

@anon6547204

I’m open to suggestions …

Its above you a dozen or more times.
Set the environment variable.
Run

pacdiff -s

Which also means if you cant be bothered to set it permanently you can just as well do

DIFFPROG=/usr/bin/meld pacdiff -s

Or in your version without the full path

DIFFPROG=meld pacdiff -s

I really dont understand whats so difficult.

Cheers all.

[phmo]

@anon6547204

How about this (meld required):

sudo DIFFPROG=meld pacdiff

It displays all pacnew-files one after the other and offers options.

Yes, I think I need meld in my system and have now installed it.

[cscs]

I was already leaving, but … gah…

@cscs

The fast and correct way, including my own opinions, would be

Ensure meld is installed

sudo pacman -Syu meld

Set the DIFFPROG environment variable

echo "DIFFPROG=/usr/bin/meld" | sudo tee -a /etc/environment

Source the environment file to be sure

source /etc/environment

Run pacdiff

pacdiff -s

Use ‘v’ to view, compare, edit, and merge new code.

(note the same file will be presented again after merge/save/close … if satisfied with the marge you can then ‘r’ for remove. Or just ‘s’ to skip … retaining the file for next pacdiff check, such as after a reboot)

The focus is to preserve configurations while adding in the new standards.

Now really. You all are on your own unless something needs clearing up. Ta.

[phmo]

Ok, I will do the instruction above and come back later.

Thanks cscs !

[anon6547204]

Good, and as we have just learned from @cscs , it is better to use DIFFPROG=meld pacdiff -s. Ashes on my head …

[phmo]

==> pacnew file found for /etc/pacman.conf
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] M
→ Unable to find a base package.
:: (V)iew, (M)erge, (S)kip, (R)emove pacnew, (O)verwrite with pacnew, (Q)uit: [v/m/s/r/o/q] o
[sudo] password for philip:
renamed ‘/etc/pacman.conf.pacnew’ → ‘/etc/pacman.conf’
[philip@Aspire7 ~]$ sudo pacman -Syu
:: Synchronizing package databases…
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade…
there is nothing to do

Community repo now seems gone.

[cscs]

@cscs

PS.
If you refuse to take the time to learn what this all means and, for example, simply overwrite all current files wit their pacnew counterparts do expect your system to break.

The upstream default for pacman.conf will be acceptable to overwrite in this case, though the fact it created a pacnew tells me you added some repo or otherwise augmented that file, or else the pacnew would not have been created, and by overwriting it you will lose this additional configuration you made.

This will not break your system, but may have been unexpected.

(ex: if you added chaotic-aur before … thats why the pacnew … and now it will not be there)

If you repeat this process on other files … such as /etc/shadow … then you will be met with a broken system.

I will repeat:

@cscs

The focus is to preserve configurations while adding in the new standards.

[andreas85]

@phmo

If I don’t know what to answer, I can hang the system, so that it cannot be used or that it does not start up as it should.

And if the system decides for you, and decides wrong, It can hang the system, so that it cannot be used or that it does not start up as it should.

And you would know nothing about it

[Ste74]

@cscs

PS.
If you refuse to take the time to learn what this all means and, for example, simply overwrite all current files wit their pacnew counterparts do expect your system to break.

This is why when program start it show this:

So if the user don’t know what happen his can open WIKI, or ask in the our Forum what happen

[cscs]

I dont speak italian, but it translates in english to

Remember:
you have to be aware of your choices. If you are unsure, please inquire using our social channels such as our support forum.

PS.
I guess the first “you” should be capitalized?