==> Making package: python-pep517 0.13.0-1 (Sat 23 Sep 2023 10:34:42)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found python-pep517-0.13.0.tar.gz
-> Found a29513a03d60a90c048ad9281dd7e897bd6f40b1.patch
==> Validating source files with sha256sums...
python-pep517-0.13.0.tar.gz ... Passed
a29513a03d60a90c048ad9281dd7e897bd6f40b1.patch ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
-> Extracting python-pep517-0.13.0.tar.gz with bsdtar
==> Starting prepare()...
/var/tmp/pamac-build-tracy/python-pep517/PKGBUILD: line 19: patch: command not found
==> ERROR: A failure occurred in prepare().
Apparently it is needed by one of the few AUR packages I have installed, and this is an update for the existing package.
Which one? There are very few that still require it as the PEP517 project is deprecated now in favor of pyproject-hooks (
pacman -Qi python-pep517 | grep 'Required By\|Optional For'
I don’t know. I’ll have a look. But if it’s deprecated that probably explains the missing commands needed to build it.
Nothing depends on it apparently. It’s gone.
For future reference, you seem to be missing
That doesn’t appear to affect any other AUR packages. Mullvad VPN, for example, updates with no issues. So not going to worry at this time.
It affects every PKGBUILD that uses
patch command. Same for anything else in base-devel.
That would indicate that the AUR packages, like Mullvad VPN, that I care about, don’t use the ‘patch’ command.
Good to know.
Don’t see how it’s interesting.
It’s like you have 3 scripts, one of them has
htop in them and the other two don’t and you don’t have
htop installed. Is it interesting that other two scripts ran fine because they don’t have
htop in them?
New information is always interesting.
base-devel is a prerequisite for using the AUR. Period. No ands, ifs or buts.