Arch Linux User Repository

PSA: Like most of the PKGBUILDs that I (co-)maintain, I host prebuilt packages for this in my user repository and all its dependencies for those who wish to install it using pacman without messing around with building from the AUR. Issues or contributions are welcome either in comments below or via this GitHub repository.

PSA: Like most of the PKGBUILDs that I (co-)maintain, I host prebuilt packages for this in my user repository and all its dependencies for those who wish to install it using pacman without messing around with building from the AUR. Issues or contributions are welcome either in comments below or via this GitHub repository.

Thanks for the alert @djmattyg007. Please see my extended comments in this issue report and the related upstream bug report. I've posted temporary fixes so this builds in a clean chroot now.

This package currently fails to build because python-setuptools-scm isn't listed as a make dependency:

https://archlinux.org/packages/community/any/python-setuptools-scm/

It may look like pip is the missing make dependency, but this isn't the case. It's only trying to use pip because the real dependency is missing.

it is against current AUR guidelines to bump release just because they need rebuilding due to library updates in official repos

Where did you read this? I think it's plainly obvious that this isn't the case given the sheer number of packages that DO get pkgrel bumps in the first 48 hours after a new version of python is released.

Sadly makepkg -fi or yay --rebuild is your friend here.

I don't use yay, nor do I use makepkg directly. I use aurutils, which helps me run an actual package repository for all the machines in my house, so that I only have to compile the software once. This relies on pkgrel bumps to trigger updates on all machines.

Isn't python-pip a (make)depend? I couldn't build this package without.

@djmattyg007 As much as I disagree with the policy of treating AUR pkgrel's different than ones in [community] in this regard, it is against current AUR guidelines to bump release just because they need rebuilding due to library updates in official repos. Sadly makepkg -fi or yay --rebuild is your friend here.

Could you please bump the pkgrel to force a rebuild for python3.9?

I still don't understand what is actually going on, but the issues with --check here are similar to what I just ran into with python-ufo2ft — the check function is actually trying to build something or other and wants an old version of fonttools.

Wow there IS something funky with this build. I can build this in a clean CHROOT but cannot on my host system! I think the test suite must be doing something really wonky looking for packages and adding tests if and only if the host system has extra things available. That's crazy pants but it's happening.

@thrasibule: Thanks for the add. I just normalized a few things following Arch's Python guidelines on the wiki and checked the build in a clean CHROOT.

@yochananmarqos I added you to the -git package, you probably mistook it for this one.