But almost all these packages (except openvpn3) had been installed on my system from official/community/extra manjaro packages, so this makes no sense. See some examples:
Even you can see pulseaudio-ctl AUR does not even show up as an option when searching… The expected / previous behavior (in my opinion) would be that pamac would suggest updates, when available, but always from the same source. Like pkg → pkg, or aur → aur, but never pkg → aur.
This started after the major update from this week:
I can confirm my system is fully updated at the moment of posting via command line:
~$ sudo pacman -Syyu
[sudo] password for antonioprates:
:: Synchronizing package databases...
core 168.6 KiB 86.9 KiB/s 00:02 [####################################] 100%
extra 1923.3 KiB 431 KiB/s 00:04 [####################################] 100%
community 6.6 MiB 91.8 KiB/s 01:14 [####################################] 100%
multilib 177.4 KiB 30.0 KiB/s 00:06 [####################################] 100%
:: Starting full system upgrade...
there is nothing to do
I am running manjaro stable. And all other details about my computer are on my profile, if ever they could have any relevance for this particular issue.
So as I understand, pamac displays possible updates, but pacman does not?
The cause of this is that pamac and pacman don’t share the same temporary database.
sudo pacman -Syyu is the same as pamac update --force-refresh
However… I guess the name AUR is here wrong. For example brave is the same name on “Updates” and on “Search”. AUR Packages are called brave-bin, brave-dev-bin and so on. So offically it is not AUR, even if it is marked somehow as AUR.
Hey @Evernow , yes, I do have the “Check for updates from AUR” option toggled on in Pamac settings, but these packages have not even been installed via AUR, so that is the part that does not really make sense to me…
@megavolt , I didn’t know pamac had it’s own database, for sure, that must have been the issue: pamac database got into some weird state! I clicked on the tree dots, then I clicked “Refresh databases”, and that was the trick. Great thanks.
@Bruno_Goncalves , you might be right, there seems to be something wrong about brave pkg. All other packages I had issue with on pamac have been fixed by “Refresh databases”, but today pamac started nagging me to update brave again (and just brave this time), and seems to be wanting to use AUR again (although it has been installed from official repos on my system). I have not updated so far and will wait and see if I can find more information about that specific one, maybe I will try to reinstall it later today.
Packages pulseaudio-ctl and python-pulsectl are in both Community repository and AUR with the same package names
But AUR packages have later version numbers
@nikgnomic have you tried “Refresh databases”? that fixed the inconsistency for me regarding these packages, and many others… except for brave, as the problem is a different one.
I do not use the 2 packages mentioned so it is no problem for me
I do not see any problem of inconsistency pamac search for pulseaudio-ctl and python-pulsectl shows the packages are present in community repository and AUR
but Manjaro packages have not yet been updated to the version available in AUR
so pamac is suggesting updating to the AUR packages to get the latest package versions
So, in the end I uninstalled the official brave package and ended up with AUR brave-bin, which works perfectly fine. Thanks for pointing me to the reason regarding brave.
I just updated pulseaudio-ctl, apparently we missed that one.
python-pulsectl is the same version in both the Manjaro repos and AUR. The AUR version appears newer because it’s using an epoch. That was not necessary for the Manjaro repo version.
