@SinClaus
Version numbering changed?
I have aur/rdarktable-git v0.0.0.r187.g70c875b2d-2 (+4 0.04) (Installed: v0.0.0.r215.g06cd53f71-1)
i.e. installed more new than in repo.
That's normal. This is a -git development package. Last time I updates the PKGBUILD in the AUR repository, the master branch was up to r187. However, when you do an update, the makepkg process will check what is the latest version available in git, and use that (in your case, it was r215). This is different to non-development packages with no -git suffix, which pull a specific point release from git rather than the latest HEAD of the master branch.
The Ansel developer is currently not doing point releases, and expects users to pull from the latest master HEAD. This may change later when Ansel becomes more stable.
Notes:
Please make exposure graph as line (like in Art/RawTherapee) I can't understand how to work with masks - they are too sprcific.
These types of remarks should be addressed to the upstream project, not to the package maintainer: https://github.com/aurelienpierreeng/ansel/issues
Pinned Comments
AlynxZhou commented on 2024-01-03 11:36 (UTC) (edited on 2024-01-03 11:37 (UTC) by AlynxZhou)
For people who are not familiar with AUR and
-git
package:-git
package does not have a fixed version tag, instead it will always checkout the latest master commit when you re-run the build command (for examplemakepkg -sif
). Considering the Ansel upstream is actively refactoring, you may need to re-run the build command to get the latest commit when you get some problem.PKGBUILD here only needs to be updated if there are changes of building steps, so the "Last Updated" doesn't mean the version of software you could build.
Don't bother upstream devs with words like "the AUR package ansel-git is last updated at 1 week/1 month ago please update it to latest commit" in GitHub issues or Matrix chatroom, I've explained that only thing you need to do is to re-build the package.
However, if you are really sure there are problems in the PKGBUILD, feel free to comment HERE, because upstream devs may not be a Arch user and they don't maintain this PKGBUILD. I'll try to fix it.