Hm.. good point.
Never had this problem (with this package, at least), so I'd just naively assumed AUR helpers (like paru, in my case) checked for changes to checksums in the .SRCINFO and re-downloaded files accordingly.
To make all this less error prone, it would make sense to follow your hint, I guess, and do it the
"${pkgver}-${pkgrel}_patch_filename.patch::https://gitlab.com/whatever/patch_filename.patch"
# …
patch -p1 -i ../${pkgver}-${pkgrel}_patch_filename.patch
way in the next release – thanks!
Pinned Comments
lsf commented on 2025-01-01 21:28 (UTC)
Please refrain from abusing the flagging of a package as out of date for build issues. This is not what it is supposed to be used for.
I automatically get notified of comments to this package. I do not need to be notified of whatever build problems occur (whether they are an individual's problems or the actual package's problems) twice, and not via flagging it out of date.
Issues with this package can also be reported at https://codeberg.org/librewolf/issues/issues (as it is also maintained there, at https://codeberg.org/librewolf/arch, too).