Hi! I have a question regarding https://wiki.archlinux.org/title/Arch_User_Repository#Updating_packages. The package maintainer of https://aur.archlinux.org/packages/gdown commented "Please do not flag for rebuilds." and quoted above wiki entry. I flagged gdown because it failed for me. The reason was that it was installed for Python 3.12, and in the meantime Arch was upgraded to 3.13. Of course a simple rebuild fixed the issue for me. But, since I keep my system up to date with yay, a simple increase of pkgrel would have fixed the issue without me noticing. So here is the question: Wouldn't it be nice of the maintainer to just increase the pkgrel value to force a rebuild on update, even if it's not required? Or is there a deeper reason for the above paragraph? Thanks -- g
On 1/23/25 9:51 AM, Gonsolo wrote:
Hi!
Hi!
I have a question regarding https://wiki.archlinux.org/title/Arch_User_Repository#Updating_packages. The package maintainer of https://aur.archlinux.org/packages/gdown commented "Please do not flag for rebuilds." and quoted above wiki entry. I flagged gdown because it failed for me. The reason was that it was installed for Python 3.12, and in the meantime Arch was upgraded to 3.13. Of course a simple rebuild fixed the issue for me. But, since I keep my system up to date with yay, a simple increase of pkgrel would have fixed the issue without me noticing.
yay is unsupported, so the fact that you keep your system up to date with it is irrelevant here.
So here is the question: Wouldn't it be nice of the maintainer to just increase the pkgrel value to force a rebuild on update, even if it's not required? Or is there a deeper reason for the above paragraph?
It *could* be nice I guess, but isn't required and would actually be unexpected in some specific cases. There's no deeper reasoning than what's written in the wiki entry. AUR packages are unsupported and it's therefore your responsibility to rebuild them if needed. There's no reason to force a rebuild for _everybody_ if _you_ need it (other people might still be on python 3.12, or have rebuilt the package on their side already for instance).
Thanks -- g
-- Regards, Robin Candau / Antiz
Jan 23, 2025 03:52:28 Gonsolo <gonsolo@gmail.com>:
Hi!
I have a question regarding https://wiki.archlinux.org/title/Arch_User_Repository#Updating_packages. The package maintainer of https://aur.archlinux.org/packages/gdown commented "Please do not flag for rebuilds." and quoted above wiki entry. I flagged gdown because it failed for me. The reason was that it was installed for Python 3.12, and in the meantime Arch was upgraded to 3.13. Of course a simple rebuild fixed the issue for me. But, since I keep my system up to date with yay, a simple increase of pkgrel would have fixed the issue without me noticing.
So here is the question: Wouldn't it be nice of the maintainer to just increase the pkgrel value to force a rebuild on update, even if it's not required? Or is there a deeper reason for the above paragraph?
Thanks -- g
1. AUR helpers such as yay are frowned upon when it comes to issues with the AUR, as most said issues don't occur if you manually build AUR packages. 2. It isn't the AUR maintainer's responsibility to make sure you rebuild python-related things on the AUR every time Python releases a new minor version and Arch packages it. 3. You can't reasonably expect to make every AUR maintainer commit and push a new PKGBUILD when literally nothing broke and the user just needs to rebuild it. The whole point of pushing an update to a PKGBUILD on the AUR is when what you maintain has a new version or no longer builds with the current recipe. 4. AUR maintainers are volunteers anyways and the more annoying little pointless tasks you ask of them the less likely they are to be willing to continue to donate their time to maintain the build recipe for everyone. The other person who replied a little before me pretty much covered every other point that could be made as well. Kusoneko.
Hi, have you considered using https://archlinux.org/packages/extra/any/rebuild-detector/ and its hook? Am 23.01.25 um 10:20 schrieb Kusoneko: > Jan 23, 2025 03:52:28 Gonsolo <gonsolo@gmail.com>: > >> Hi! >> >> I have a question regarding >> https://wiki.archlinux.org/title/Arch_User_Repository#Updating_packages. >> The package maintainer of https://aur.archlinux.org/packages/gdown >> commented "Please do not flag for rebuilds." and quoted above wiki >> entry. >> I flagged gdown because it failed for me. The reason was that it was >> installed for Python 3.12, and in the meantime Arch was upgraded to >> 3.13. >> Of course a simple rebuild fixed the issue for me. >> But, since I keep my system up to date with yay, a simple increase of >> pkgrel would have fixed the issue without me noticing. >> >> So here is the question: Wouldn't it be nice of the maintainer to just >> increase the pkgrel value to force a rebuild on update, even if it's >> not required? >> Or is there a deeper reason for the above paragraph? >> >> Thanks >> -- >> g > 1. AUR helpers such as yay are frowned upon when it comes to issues with the AUR, as most said issues don't occur if you manually build AUR packages. > > 2. It isn't the AUR maintainer's responsibility to make sure you rebuild python-related things on the AUR every time Python releases a new minor version and Arch packages it. > > 3. You can't reasonably expect to make every AUR maintainer commit and push a new PKGBUILD when literally nothing broke and the user just needs to rebuild it. The whole point of pushing an update to a PKGBUILD on the AUR is when what you maintain has a new version or no longer builds with the current recipe. > > 4. AUR maintainers are volunteers anyways and the more annoying little pointless tasks you ask of them the less likely they are to be willing to continue to donate their time to maintain the build recipe for everyone. > > The other person who replied a little before me pretty much covered every other point that could be made as well. > > Kusoneko.
Ey, You can force a rebuild with most AUR helpers by simply reinstalling the package. -- Cheers, Aᴀʀᴏɴ
participants (5)
-
Aaron Liu
-
funny0facer
-
Gonsolo
-
Kusoneko
-
Robin Candau