Cannot find the meld binary

[anon75791628]

I tried to use Meld first time.

First I installed Meld from Manjaro repo.
Then gave a command at a Terminal sudo DIFFPROG=meld pacdiff
Nothing happens, just empty line in Terminal.

Then I tried Meld installed from Flatpak.
Same command sudo DIFFPROG=meld pacdiff
Result is ==> ERROR: Cannot find the meld binary required for viewing differences.

Not a good start to trying to compare pacnew-files.
What shall I do to execute Meld?

@omano

Also please don’t make lot of replies, edit your post instead, select what you want to reply to, click quote, and continue the message. Multi posting in a row is generally not accepted in forums.

I try. Like this?

@omano

A package can get to a new version, then because of X reason (it can be a problem in this version, or the update got pushed by mistake, or whatever reason), they decide to get back to a previous version, and if you got the updated version before the package get reverted to previous version, you then have a version newer than what is in the repositories, and pacman throws a warning message about it.

Okay. So that mr. pacman is there again? This time it is not pacnew-files in question, but package versions?

@tux-86

If you want get rid those warnings, you can run sudo pacman -Syyuu. This command downgrade packages to same version as in repository.

Is this reply related what omano said?

[maycne.sonahoz]

Do you even have a *.pacnew or *.pacsave file to diff on?

[anon75791628]

I believe so, because I made pacman hook script.
Then I ran sudo pacman -Syu

Result :: Synchronizing package databases... core is up to date extra is up to date community is up to date multilib is up to date :: Starting full system upgrade... warning: gnome-shell-extension-unite: local (57-1) is newer than community (56-1) warning: zsh-theme-powerlevel10k: local (1.15.0+66+g3e515a7-1) is newer than community (1.15.0-2) there is nothing to do

Those warning are related to pacnew-files, I think.

[tux-86]

If you want get rid those warnings, you can run sudo pacman -Syyuu. This command downgrade packages to same version as in repository.

[jrichard326]

The following command works here:

sudo -H DIFFPROG=meld pacdiff

The binary should be found in /usr/bin/meld

change to directory and run ./meld

[maycne.sonahoz]

@anon75791628

Those warning are related to pacnew-files, I think.

No they don’t.
https://wiki.archlinux.org/title/Pacman/Pacnew_and_Pacsave

[omano]

@anon75791628

Nothing happens, just empty line in Terminal.

Because you have no .pacnew or .pacsave file.

What is output of pacdiff -o?

[anon75791628]

I am not sure if I want to get rid of those. First I want to understand a reason for what happened.

[omano]

Packages can get reverted to previous version in the repositories.

[anon75791628]

There is not meld in that directory.

[anon75791628]

Understood.

[anon75791628]

@omano

Because you have no .pacnew or .pacsave file.

Right.

@omano

What is output of pacdiff -o?

Just empty line.

[anon75791628]

@omano

Packages can get reverted to previous version in the repositories.

Not understand what you mean, sorry.
Actually I understand the words, but I don’t understand it really.

[mithrial]

Probably, it’s not installed:
pamac install meld

[anon75791628]

I tried again. Command still not working.

[omano]

@anon75791628

Just empty line.

You have no pacnew then.

@anon75791628

Not understand what you mean, sorry.
Actually I understand the words, but I don’t understand it really.

A package can get to a new version, then because of X reason (it can be a problem in this version, or the update got pushed by mistake, or whatever reason), they decide to get back to a previous version, and if you got the updated version before the package get reverted to previous version, you then have a version newer than what is in the repositories, and pacman throws a warning message about it.

Also please don’t make lot of replies, edit your post instead, select what you want to reply to, click quote, and continue the message. Multi posting in a row is generally not accepted in forums.

[maycne.sonahoz]

@anon75791628

I try. Like this?

He meant the successive posts he highlighted in his screenshot. Now this thread is getting confusing.

---

@anon75791628

@tux-86

If you want get rid those warnings, you can run sudo pacman -Syyuu. This command downgrade packages to same version as in repository.

Is this reply related what omano said?

Yes.

---

[HowTo] Fix package "is newer than ..."

Difficulty: ★☆☆☆☆ What does this error mean? This is not an error but only a warning, because it expresses an “abnormal” situation which may or may not be harmful. That situation is exactly as described by the message: the package installed on your system is a newer version than the one in the repositories. How did that happen? There are two major cases: You switched from the stable branch to another, in which newer versions of packages are tested. By updating from that branch, you can ge…

[NGr]

@anon75791628

Then gave a command at a Terminal sudo DIFFPROG=meld pacdiff
Nothing happens, just empty line in Terminal.

That means there aren’t any pacnew or pacsave files to view

[Yochanan]

@omano

Packages can get reverted to previous version in the repositories.

…especially when @philm makes a snapshot and doesn’t notice I pushed newer packages ahead of it.

None of the packages @anon75791628 mentioned were purposely downgraded.