Help with pacnew handling

[Aragorn]

@Vidar

But aren’t both manjaro-pacnew-checker and pacnew-chaser configured to work only with meld, or rather, to pass to meld?

manjaro-pacnew-checker probably is, but on my system, pacnew-chaser invokes diffuse. Which is strange, because I have…

DIFFPROG=/usr/bin/kompare

… in /etc/environment.

@Vidar

How do you achieve the same thing with kompare?

That’s a good question. I haven’t messed with the .desktop file yet, but perhaps it could be added there.

---

@mkb

@FreddyX

The safest way is to run sudo pacman -Syyu in a tty.

I have read notes/warnings in the past (like this one from @Aragorn) that -Syuu is not the way to go

Note that you misread @FreddyX’s post. He was talking of -Syyu, while you are talking of Syuu.

Those options are very different, but they both do exist for a reason. The idea, then, is of course to use them when necessary only.

• For regular updates, use -Syu.

• If you decide to switch branches — e.g. from Stable to Testing or Unstable, or in the other direction — then you should use -Syyu, which will refresh all databases even if they are up-to-date. It also used to be recommended in the event of refreshing the mirrors, but that is no longer the case. It is either way not recommended for regular package updates because it will put an extra load on the servers.

• If there are any packages which for whatever reason have been downgraded again — for instance because a package with a newer version was erroneously pushed from Testing to Stable and was then pulled again — then you would use -Syuu, which allows for downgrading.