Arch Linux User Repository

@willemw Can we get rid of line 32 (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=ffmpeg-normalize#n32) so we're not running the full test suite on each upgrade?

For me it worked better to install directly from PyPi with pipx; no other dependencies but ffmpeg itself.

@npreining: Thanks again.

@willemw it is still broken in 1.33.1-3 You are missing this

--- a/PKGBUILD
+++ b/PKGBUILD
@@ -22,13 +22,13 @@ sha512sums=('ee83d9ab48cf2a2e4e16e1fb1b9442e9a4b247fb4535de75c03ca823422d24d1a08
 build() {
   cd $pkgname-$pkgver
   #python -m build --no-isolation --wheel
-  uv --no-cache --offline build --no-build-isolation --out-dir=dist --wheel .
+  uv --no-cache --offline --no-managed-python build --no-build-isolation --out-dir=dist --wheel .
 }

 check() {
   cd $pkgname-$pkgver
   uv venv --no-managed-python --system-site-packages
-  uv --no-cache --offline pip install --link-mode=copy --no-deps dist/*.whl
+  uv --no-cache --offline --no-managed-python pip install --link-mode=copy --no-deps dist/*.whl
   PATH=".venv/bin:$PATH" ./.venv/bin/python -m pytest tests
 }

Otherwise it still uses the uv in .local if there is one.

@npreining: Thanks. Will add it.

It would be nice if there are some official packaging guidelines around using "uv".

The package fails to build if uv has already some managed python packages installed.

You must call

uv venv --system-site-packages --no-managed-python

to ensure that the system provided python is used, otherwise the one in .local/share/uv/python/ is used.

Adding this --no-managed-python ensures that the system python is used for creating the venv, and then the tests run through.

I can't confirm that at the moment. It worked for me with version 0.8.13-1. But I didn't have anything from ux installed beforehand. Neither the Python package nor the normal ux, and that was the whole problem for me. Now that it's there, it works with pamac and also with makepkg.

I can confirm. Does not build with the older "uv" 0.8.13-1. Does build with "uv" 0.8.14-1.

Also successfully built the package with pamac-cli. Although pamac-cli skipped running check(), which it should.

I think uv_build is built into "uv". Maybe with "uv" version 0.8.14 the package will build in Manjaro.

I have corrected the prepare() mentioned below, but I probably won't add it to the PKGBUILD file.

@willemw

I tested a few things again and revisited my initial idea, because Python itself does not recognise uv_build on my system either.

$ python
Python 3.13.7 (main, Aug 15 2025, 12:34:02) [GCC 15.2.1 20250813] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import uv_build as backend
Traceback (most recent call last):
  File "<python-input-0>", line 1, in <module>
    import uv_build as backend
ModuleNotFoundError: No module named 'uv_build'

After that, I have now actually entered the dependency python-uv-build in your current PKGBUILD.

And after that, the build worked without any problems.

So I would suggest that, if you have no objections, you add the dependency.