Arch Linux User Repository

I am still seeing this. Is there a packaging encapsulation leak or something that is preventing the new way from working?

Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/usr/lib/python3.11/site-packages/installer/__main__.py", line 98, in <module>
    _main(sys.argv[1:], "python -m installer")
  File "/usr/lib/python3.11/site-packages/installer/__main__.py", line 86, in _main
    with WheelFile.open(args.wheel) as source:
  File "/usr/lib/python3.11/contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/installer/sources.py", line 162, in open
    with zipfile.ZipFile(path) as f:
         ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/zipfile.py", line 1284, in __init__
    self.fp = io.open(file, filemode)
              ^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/nfs/home/65a/.cache/yay/python-jaxlib/src/jax-jaxlib-v0.4.18/dist/jaxlib-0.4.18-*.whl'

@65a There is no issue anymore. The issue existed in transition from 0.4.15 to 0.4.16 because JAX maintainers changed release and versioning machinery by adding JAXLIB_RELEASE envvar to get release version. Now python-jaxlib builds perfectly fine because I included corresponding envvar to PKGBIUILD.

Any fix for this coming soon? I've had to build it locally lately to prevent package updates from burning CPU.

Well, you've pushed 0.4.17 and didn't go to a release build, so clearly the dev build was the intended behavior. You had the opportunity to address it, and you didn't.

@segin It is not a fix. https://aur.archlinux.org/packages/python-jaxlib#comment-935718

It is not just dash or dot. The issue is that that package version should be release build

$ python -c 'from jaxlib.version import __version__; print(__version__)'
0.4.16

not a nightly build like this.

$ python -c 'from jaxlib.version import __version__; print(__version__)'
0.4.16.dev20231001

@daskol It's a fix. Trust me. Apply it and watch the magic work.

Between "0.4.16" and "dev...", you're using a - when the actual real file on disk will have a . in that place.

Line 38 (excerpted) on the PKGBUILD has "jaxlib-$pkgver-.whl" - instead here do "jaxlib-$pkgver..whl"

Why?

FileNotFoundError: [Errno 2] No such file or directory: '/home/segin/.cache/yay/python-jaxlib/src/jax-jaxlib-v0.4.16/dist/jaxlib-0.4.16-*.whl'

Because the actual file on disk doesn't have a - after the 16, it has a .:

segin@installation-00[10:09]:{~}% ls -l /home/segin/.cache/yay/python-jaxlib/src/jax-jaxlib-v0.4.16/dist/jaxlib-0.4.16.*.whl
-rw-r--r-- 1 segin wheel 71560446 Oct  1 10:07 /home/segin/.cache/yay/python-jaxlib/src/jax-jaxlib-v0.4.16/dist/jaxlib-0.4.16.dev20231001-cp311-cp311-manylinux2014_x86_64.whl
segin@installation-00[10:09]:{~}%  

Literally the issue is a malformed wildcard. I change that one single - to a . and look, ls finds the file!

@segin No, it is not fix. In this case jax.version.__version__ is not $pkgver. Initial intent was to catch dirty releases since lately many packagers ranging from huggingface to google changes release pipelines, way how to version is assigned to package, or makes unfortunate mistakes. If release version is $pkgver then the package must expose the same version $pkgver consistently.

Here's a ONE CHARACTER fix for this bug:

Replace the dash (-) between the package version and the wildcard with a period (.)

In my case, the generated wheel filename is jaxlib-0.4.16.dev20230926-cp311-cp311-manylinux2014_x86_64.whl but the wildcard is trying for jaxlib-0.4.16-*.whl

Right there in the wildcard after the 16 is a - when it should be a .

There, fixed by changing one single byte in the PKGBUILD.

@h3ss I see. I guess the issue is that jaxlib is built with bazel. Its build directory actually is in ~/.cache/bazel and it is not cleans with makepkg -C. I'll try to move ~/.cache/bazel in $srcdir in the future.