Should pkgrel of Python packages be bumped?

daniel_shub · 2023-05-08 15:17:14

Whenever a new version of Python is released, AUR python packages generally need to be rebuilt against the new version. Often, nothing needs to be changed in the PKGBUILD and all the user needs to do is rerun makepkg. It is not really that easy since pacman will not know the rebuilt package is a new release if the pkgver and pkgrel do not change. Of course the user can force pacman to "reinstall" the package. One solution I have seen requested on the AUR is to bump the pkgrel even though nothing changes. The packaging guidelines (https://wiki.archlinux.org/title/Python … guidelines) do not address this issue. Things get further complicated because some of the AUR helpers detect the Python version change and rebuild the AUR packages and other do not, I think.

Is there guidance someplace about what to do with AUR python packages when the Python version changes?

Scimmia · 2023-05-08 15:37:25

I used to, but I don't anymore. You mention pacman not knowing that the rebuilt package is different really isn't an issue, pacman doesn't treat it any differently. You tell it to install it, it installs it.

The main reason I don't, more generally, not just python, is that you really don't know the state of the user's OS. Are they using the {kde,gnome}-unstable repos? testing/community-testing? Are they on a different distro that moves slower? There's no way of predicting when you should bump the pkgrel.

V1del · 2023-05-08 15:41:35

Ultimately AUR packages are the responsibility of the user and they should be aware enough of this need to do that, if you are a maintainer and want to do it to inform people using helpers you are free to do so, but it's not really a strict requirement.

AUR helpers in general aren't considered supported, do how they handle this individually shouldn't factor in

Last edited by V1del (2023-05-08 21:40:53)

C0rn3j · 2025-02-07 11:32:39

> Is there guidance someplace about what to do with AUR python packages when the Python version changes?

I do not believe there is anything official, but you should bump it when Arch bumps major Python versions, as a courtesy.

As Scimmia pointed out, you will still get people on some derivatives ending up with partial upgrades if they hold things back, but it's *Arch* User Repository, so while unfortunate, it's not a concern that should be taken.

Usually checkrebuild from the rebuild-detector package would find a partial upgrade like this, but unfortunately not for Python libraries since they don't usually actually link against things.

I don't think there's a better solution for this outside of becoming a Package Maintainer and moving your packages out of AUR.

Users can also have all AUR packages be rebuilt on every system upgrade, which solves this and other related issues, albeit it's quite annoying to do.

Scimmia · 2025-02-07 13:14:01

C0rn3j wrote:

I do not believe there is anything official, but you should bump it when Arch bumps major Python versions, as a courtesy.
As Scimmia pointed out, you will still get people on some derivatives ending up with partial upgrades if they hold things back, but it's *Arch* User Repository, so while unfortunate, it's not a concern that should be taken.

Please don't necrobump, it's against the forum rules, but especially to give bad advice. And don't simplify my argument into something that it wasn't.

WorMzy · 2025-02-07 13:28:35

As noted, this is an old topic. Pleaese don't necrobump.

https://wiki.archlinux.org/title/Genera … bumping%22

Closing.

Arch Linux

#1 2023-05-08 15:17:14

Should pkgrel of Python packages be bumped?

#2 2023-05-08 15:37:25

Re: Should pkgrel of Python packages be bumped?

#3 2023-05-08 15:41:35

Re: Should pkgrel of Python packages be bumped?

#4 2025-02-07 11:32:39

Re: Should pkgrel of Python packages be bumped?

#5 2025-02-07 13:14:01

Re: Should pkgrel of Python packages be bumped?

#6 2025-02-07 13:28:35

Re: Should pkgrel of Python packages be bumped?

Board footer