AUR version should not have precedence over repo pkgs

[oberon-manjaro]

Yesterday I created new packages sndio and sidplay2-libs which both exist in the AUR.
Since they are new in the repo, I am using pkgrel 1 although AUR versions have higher pkgrel.
Now while all is well with pacman and yaourt, pamac turns the try icon to red and shows these packages under 'updates'. While it is impossible for us to keep track of AUR versions of all our packages, people shouldn't be encouraged to install AUR versions over repo versions anyway.

$ sudo pacman -Syu
:: Synchronising package databases...
 core is up to date         0,0   B  0,00B/s 00:00 [----------------------]   0%
 extra is up to date        0,0   B  0,00B/s 00:00 [----------------------]   0%
 community is up to date    0,0   B  0,00B/s 00:00 [----------------------]   0%
 multilib is up to date     0,0   B  0,00B/s 00:00 [----------------------]   0%
:: Starting full system upgrade...
 there is nothing to do

$ yaourt -Syua
[sudo] password for xfce: 
:: Synchronising package databases...
 core is up to date         0,0   B  0,00B/s 00:00 [----------------------]   0%
 extra is up to date        0,0   B  0,00B/s 00:00 [----------------------]   0%
 community is up to date    0,0   B  0,00B/s 00:00 [----------------------]   0%
 multilib is up to date     0,0   B  0,00B/s 00:00 [----------------------]   0%
 Foreign packages: | 16 / 16

[guinux]

Ok do not change pkgrel so I can test and fix it.

[oberon-manjaro]

Thank you! I won't touch it 😉 👍

[oberon-manjaro]

On my end the behaviour has suddenly disappeared after some package updates. Not sure why... Just had a few package updates but nothing that would seem connected.

[oberon-manjaro]

I think the reason was that I had the two packages installed in the chroot locally, before they were added to the repo. I now just built another package and the chroot db got updated. Now the issue has disappeared.
In any case I don't think it's urgent to change anything. 😉

[guinux]

Yes it's certainly the fact you built the packages on your system because I just realized that sndio was installed this morning from repos on my system when I upgraded vlc-nightly and pamac doesn't show any updates.

[oberon-manjaro]

Yes. Funny thing just was that removing the packages from the system and removing the actual packages from the cache before re-installing was not enough. Only when the chroot database got updated, pamac stopped complaining 😉

[oberon-manjaro]

Now pamac is again acting up on me about package versions in the AUR. Can't really figure out why:

[oberon-manjaro]

This time it seems the update mesasge was triggered by a (legitimate) AUR update for skypeforlinux-bin.

[philmmanjaro]

what happens if you search for vlc-nightly? on my end it says it doesn't exist in the AUR, even we know it does 😄

Looks fine on my end. Only AUR packages and no conflicts with installed binaries having the same name ...

[oberon-manjaro]

True! pamac thinks vlc-nightly only exists in the repo and not in AUR, while in reality it exists in both.

[oberon-manjaro]

And it's the same for all the packages it wants to update for me. mugshot, xcurosr-breeze, ...

[guinux]

Pamac doesn't show a package from AUR if it's also available in a repo.
Pamac checks for an update from AUR only if the package is not provided by a repo.
It seems related to your local repo, does pamac find mugshot (for example) in the repos ?

[oberon-manjaro]

Yes, pamac lists all these packages as available from repos. At the same time the update page shows the higher pkgrels in AUR:

[oberon-manjaro]

pkg and iso chroots are up-to-date. none of these packages have been locally installed or installed to the chroot locally.

[philmmanjaro]

And when you try to update it uses the AUR packages? Is it just a display error or does it try to install the "newer" packages from the AUR?

[oberon-manjaro]

No. It doesn't update anything. I get stuck in a loop, where 'Apply' remains the only available button:

[guinux]

I have to say I can't find why you experienced this trouble.

[petsam]

Could that behavior have been caused because of mirror differences or the sequence of checking them in pamac?

[andruska]

I can report the same issue. Pamac offers AUR updates over packages in community repo. Particular packages are palemoon, mugshot and xcursor-breeze.