You are not logged in.
Here is a list of AUR packages I follow where the pkgrel inexplicably decreased by 1. There's no sensible reason for this decrease because I maintain some of these and know that I did not do that. Besides, it never makes sense to decrease the pkgrel while keeping the pkgver the same.
clup cdu cla gtk-theme-config lib32-pangox-compat mkinitcpio-colors-git nautilus-data opentk opentk-docs setcolors-git tchrome
gnome-search-tool-no-nautilus
What happened? How can the pkgrel be corrected?
Last edited by colinkeenan (2017-02-07 17:55:31)
Offline
What makes you think that the pkgrel decreased? Can you check your local git repository that you push from, and see which commits (if any) are not currently pushed?
I find the setcolors-git package odd, as it has a Last Updated date of 2016-08-14 22:10, but the last commit is from 2015-06-21, I'm not sure what has happened there.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
I use nvchecker to check for new releases and it suddenly told me all these packages needed to be "upgraded" because the pkgrel was different (actually, one lower). I double checked the installed version of some of these and realized it was one higher than what AUR says.
Double checking my local git repo though, I realize the problem is with nvchecker and not AUR. The reason my installed pkgver is one higher is because I package these for archlinuxcn and had increased the pkgrel by one for various reasons (but most because of an issue with my key). In the past, nvchecker did not report the discrepancy, but now, for no good reason, it thinks the lower pkgrel on AUR is an issue.
I will report the bug with archlinuxcn. Thanks.
Offline