Arch Linux

ianis

Member

Registered: 2016-09-29

Posts: 1

Major Python updates and AUR builds

We now have Python 3.14, which is wonderful, but causes a small issue with my pacman repository.

A python package directory is version dependent:

/usr/lib/python<version>/site-packages/<package>/

So, depending on the Python version I use, I will obtain different packages from the same PKGBUILD file. If I build a package from the AUR and upload it to my repository, it works fine until the Python update. Then I have to rebuild it and reupload it, which causes a signature conflict because the package version and release has not changed.

The simplest I can think of is to bump the release (the pkgrel field). I also see here that this is done for official packages.

This approach works for my own packages, but is fragile for foreign packages from the AUR because modifying their pkgrel can cause conflicts later on.

Can anybody recommend a better solution? Sorry if I am missing something obvious.

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 72,057

Re: Major Python updates and AUR builds

modifying their pkgrel can cause conflicts later on

You could offset the local pkgrel by 10000+n or so, so if the foreign release moves from *sigh* 6 to 7 *sigh* your local release moves 10006 to 10007, you than need to bump that for the python rebuild 10007 to 10008 (+10001) and the next foreign release bump from 7 to 8 translates to 10008 to 10009
The number doesn't matter, it just has to be (de facto) monotonic ("de facto" being provided by the huge offset from the lower movement)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 14,623

Re: Major Python updates and AUR builds

In similar cases I add .1 to the local version so 6 becomes 6.1 (or 6.2)
Aur maintainers typically increase pkgrel by 1 , so that gives 9 rebuild options before a conflict occurs with a new aur version.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Allan

Pacman

From: Brisbane, AU

Registered: 2007-06-09

Posts: 11,624

Website

Re: Major Python updates and AUR builds

In similar cases I add .1 to the local version so 6 becomes 6.1 (or 6.2)
Aur maintainers typically increase pkgrel by 1 , so that gives 9 rebuild options before a conflict occurs with a new aur version.

It gives far more...

allan@wsl ~
> vercmp 1-1 1-2
-1

allan@wsl ~
> vercmp 1-2 1-1
1

allan@wsl ~
> vercmp 1-1.10 1-1.9
1

.

---

PGP Key: F99FFE0FEAE999BD | I develop pacman - buy me a drink!

lilydjwg

Member

Registered: 2010-06-20

Posts: 64

Re: Major Python updates and AUR builds

This approach works for my own packages, but is fragile for foreign packages from the AUR because modifying their pkgrel can cause conflicts later on.

I operate a package repo and my strategy is to make sure pkgrel is updated: read old pkgver & pkgrel, fetch updates from AUR, read pkgver & pkgrel again, then change pkgrel to the largest one plus one if pkgver is unchanged. (This is done not manually but by a script of course.)