Hi everyone - there is something funny I don’t understand about Manjaro repos’ and I’d like to pick your brains.
I have an updated system on the stable branch. If I run the upgrade routine through either pacman or pamac I get no new package to be installed. Yet, if I manually download package metadata with yay -G it will download a PKGBUILD that actually contains a newer version of the software, one that I can then build just fine with makepkg.
An example of this happening - today, in fact - is owncloud-client. The community version is reported to be 126.96.36.19955-1; however, if I get the PKGBUILD with yay -G owncloud-client and than build it I successfully end up with the most recent version which is 188.8.131.5296-1.
community/owncloud-client 184.108.40.20655-1 (2.0 MiB 5.0 MiB) (Installed: 220.127.116.1196-1)
ownCloud client based on mirall
AUR stuff tends to be more bleeding edge than the packages in the official repositories for Manjaro Stable, because the AUR was essentially created for Arch Linux, and Arch Stable corresponds to Manjaro Unstable.
Manjaro is a curated rolling release, and as such, the packages we take over from Arch are first properly tested (and patched if necessary) via Manjaro Unstable and Manjaro Testing before they land in Manjaro Stable.
That client is packaged by Arch and redistributed by Manjaro: Packages. yay also is able to get the sources like PKGBUILDs, either from the AUR or the gitlab from Arc Linux, as yay is a tool designed for Arch Linux.
If you look at our packages list, you may find out that we actually redistribute the version you have from stable branch and the newer versions you may find in other branches like testing and unstable. You can switch between branches: Switching Branches - Manjaro
The stable branch currently gets very few updates as we are in preparation of the next Install Media release, which also brings newer packages like Gnome 44 series and latest Python.