AUR keeps reverting to the old version even if the package is upgraded

Hello,

I’ve released a version (a new tag with the prefix v ) in my repo’s releases list. And I have upgraded the AUR package. But when I install the AUR, it installs the old version instead of new version.

I’ve checked several times the PKGBUILD , created .SCRINFO , everything is correct, and I am still confused. I think it was pkgrel , but I could not figure the unknown reason for past loop.

I have been searching “Arch AUR keeps reverting to the old version” and “Arch AUR keeps installing the old version” on DuckDuckGo, Google, Arch Linux, Endeavour OS and Manjaro forums and subreddits, and I got no result in this case. I tried with https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_function.

I am not sure exactly what you are asking but please feel free to post your question.

If it is in the wrong place, we can just move it. :smile:

See the example of my question I posted on Reddit: https://www.reddit.com/r/linuxquestions/comments/i440l8/aur_keeps_reverting_to_the_old_version_even_if/

Ah, I knew you before. You were one who helped someone to solve AUR issues in another forum.

Just open a new topic and ask your question. :rofl:

I am just following EndeavourOS’ rules. Better I be waiting for the moderators’ answers before I post my new topic to make sure I can or I can not.

So, are you saying the version in your private repo causes you to have a lower version than what is in AUR or that the AUR version installs a lower version than you expect?

Either way, your AUR package should probably be using a pgver() function since it is pulling the latest from git.

@dalto is a mod…oh yea so am I. :hugs:

2 Likes

You can definitely post your question or just edit the title/content of this post to have your actual question.

We aren’t that strict here.

The posting volume here isn’t large enough to have separate categories for every type of issue but that doesn’t mean you can’t ask. Always feel free to ask.

Both

I am still confused. The pkgver=4.0 seems totally correct in both PKGBUILD and .SCRINFO.

OK, I will update this topic.

Can you post a link to the binary package so we can look at that as well.

Of AUR or GitHub repo?

AUR: https://aur.archlinux.org/packages/yaru-plus-git
GitHub: https://github.com/Bonandry/yaru-plus (go to releases and the tag came from the branch gusbemacbe)

Binary package of GitHub: https://github.com/Bonandry/yaru-plus/archive/v4.0.tar.gz

The AUR package pulls straight off of master which hasn’t been updated in 6 months.

If you want the AUR package to pull from your branch, you need to change the source to reference your branch. Alternatively, if you want to reference a specific tag you could do that as well.

Yes, I have dedicated a lot to fix the owner’s project because he broken the proejct, it took months to fix the project.

I prefer to reference a specific tag, because the branch gusbemacbe comes with latest commits that may have bugs, etc. I did not merge from the branch gusbemacbe into the branch master yet because I needed to release to AUR, Void Linux Package, etc. before.

Althought git -C ${pkgname/-git/} describe --long --tags | sed 's/\([^-]*-g\)/r\1/;s/-/./g;s/^v//' seem totally correct because it catches the tag.

But that snippet doesn’t effect what you are pulling.

This is what you are pulling:

source=("git+${url}.git")

If you want to pull a specific tag, you should probably remove the pkgver() function and change the source line to something more like this:

source=("git+${url}.git#tag=${pkgver}")

EDIT: As a side note, you probably shouldn’t be testing your PKGBUILDs by uploading them to AUR. You should get them working locally with makepkg and only push them once you have tested them.

2 Likes

I changed to source=("git+${url}.git#tag=v${pkgver}") because of the prefix v.

I always thought the command git -C ${pkgname/-git/} describe --long --tags | sed 's/\([^-]*-g\)/r\1/;s/-/./g;s/^v//' helped to download the tag, but I did not know it did not seem to work. I thought it was blame of something else on the file.

Thank you for your counsel.