Arch Linux User Repository

@otreblan: As a follow-up to what @patlefort mentioned, python-uv-build replaces python-setuptools as the build backend.

Also, since we have 0.12.3, it will fail unless the dependency is relaxed. I tested with no issues:

  # Relax uv_build dependency
  sed -i 's/uv_build>=0.11.4,<0.12/uv_build>=0.11.4/g' pyproject.toml

Missing python-uv-build in makedepends.

@otreblan: The upstream URL is now https://github.com/legendary-gl/legendary.

The same thing @gbr points out in their last comment is happening again. The pkgrel must be bumped to make it compatible with Python 3.13.

Thank you.

Please bump pkgrel to trigger a rebuild for users, and to make it compatible with Python 3.12. Because if you had this package installed before the 3.12 update, legendary won't launch:

$ legendary
Traceback (most recent call last):
  File "/usr/bin/legendary", line 5, in <module>
    from legendary.cli import main
ModuleNotFoundError: No module named 'legendary'

Thank you.

Clean chroot build fails. Python-installer package is missing from build dependencies. @otreblan please have a look at @yochananmarqos comment. His PKGBUILD has correct dependencies.

0.20.33-3 doesn't build anymore for me:

  -> Extracting legendary-0.20.33.tar.gz with bsdtar
==> Sources are ready.
legendary-0.20.33-3: parsing pkg list...
==> Making package: legendary 0.20.33-3 (dom 06 ago 2023 04:14:47)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting build()...
/usr/bin/python: No module named build
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'legendary-0.20.33-3': 
error: packages failed to build: legendary-0.20.33-3

Neither python-setuptools nor python-wheel are runtime dependencies. Most of the optional dependencies are duplicates of python-pywebview's optional dependencies. See my improved PKGBUILD.

ModuleNotFoundError: No module named 'filelock'

After Arch upgraded to Python 3.11, previous installations of legendary don't launch anymore:

$ legendary --help
Traceback (most recent call last):
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 563, in from_name
    return next(cls.discover(name=name))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/legendary", line 33, in <module>
    sys.exit(load_entry_point('legendary-gl==0.20.32', 'console_scripts', 'legendary')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/bin/legendary", line 22, in importlib_load_entry_point
    for entry_point in distribution(dist_name).entry_points
                       ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 981, in distribution
    return Distribution.from_name(distribution_name)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 565, in from_name
    raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for legendary-gl

I understand it's just a matter of rebuilding the package, but perhaps you could intentionally bump pkgrel to force a rebuild for non-tech savvy users.