Morganamilo
commented
12 hours ago It's a bit unfortunate the way it works. But it makes sense so I don't consider it a bug per say. Just something that coul dbe handled better.
I have to wonder why you use -uu with any regularity though. There's almost no reason to every use it.
In one of my shell aliases for paru using double u's, I noticed keep getting dev package bluez-alsa-git reinstalled continually upon every run, and I see it even happens with --nodevel switch.
I narrowed it down to the double u's as said, and that the installed version is different irregardless of the cached pkgbuild has same pkgver as installed version(updated from previous pkgver() run) and I don't select cleanbuild.
So, with --nodevel switch(and said double u's), then is continually reinstalled as regular package. Without --nodevel(and double u's), then also reinstalled as regular package continually, until new commit, which then gets installed(correctly) as dev package(I tested with flipping char in devel.toml).
Latest paru/libalpm i.e. 2.0.3/14.0.0.
Many thanks in advance.
(Same issue for yay, reported here: https://github.com/Jguer/yay/issues/2484)
Edit: I learned Paru uses .SRCINFO, which pkgver() doesn't update unfortunetly, hence above issues, partly, as still the issue left of double u's and --nodevel making it still down-grade devel packages, surely a bug atleast. For former(not using --nodevel), I'll add --needed, and just waste some slight extra time, plus get install/uninstall'ed make-deps more annoyingly). Thanks.