Arch Linux User Repository

Here are the required changes in case you are too lazy to figure it out.

diff --git a/PKGBUILD b/PKGBUILD
index 8f24a27..6ff29a7 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -16,19 +16,24 @@ _pydeps=(cbor2
          yaml)
 depends=(python
          "${_pydeps[@]/#/python-}")
-makedepends=(python-setuptools)
+makedepends=(python-build python-installer python-wheel python-poetry-core)
 options=('!emptydirs')
 _archive="$pkgname-$pkgver"
 source=("https://files.pythonhosted.org/packages/source/${pkgname::1}/$pkgname/$_archive.tar.gz")
 sha256sums=('1cb2d4de31763bbac175f0e493e195568f956318caa70ac3359ff794932628cf')

+prepare() {
+   cd "$_archive"
+   rm -rf dist/
+}
+
 build() {
    cd "$_archive"
-   python setup.py build
+   python -m build --wheel --no-isolation
 }

 package() {
    cd "$_archive"
-   python setup.py install --root="$pkgdir" --optimize=1 --skip-build
+   python -m installer --destdir="$pkgdir" dist/*.whl
    install -Dm0644 -t "$pkgdir/usr/share/licenses/$pkgname/" LICENSE
 }

This version broken. The source archive does not have setup.py any more, and therefore does not build.

==> Making package: remarshal 0.16.1-1 (Mon 24 Jul 2023 13:07:30)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading remarshal-0.16.1.tar.gz...

==> Validating source files with sha256sums...
    remarshal-0.16.1.tar.gz ... Passed
==> Extracting sources...
  -> Extracting remarshal-0.16.1.tar.gz with bsdtar
==> Removing existing $pkgdir/ directory...
==> Starting build()...
python: can't open file '/home/x/aur/remarshal/src/remarshal-0.16.1/setup.py': [Errno 2] No such file or directory
==> ERROR: A failure occurred in build().
    Aborting...

https://wiki.archlinux.org/title/Python_package_guidelines https://github.com/remarshal-project/remarshal/tree/v0.16.0

As you probably already know, this outputs a warning. It should be updated to not use setup.py as the warning says. In fact, the upstream GitHub repository does not use setup.py at all, it appears to have been added to the archive by pypa/pythonhosted.org

==> Starting package()...
running install
/usr/lib/python3.11/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!

        ********************************************************************************
        Please avoid running ``setup.py`` directly.
        Instead, use pypa/build, pypa/installer or other
        standards-based tools.

        See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
        ********************************************************************************

!!

Thanks for the add. I just did an overhaul and fixed the source location, dependency, and build process issues I could see. I've confirmed it works in a chroot with nothing but it's currently mark dependencies.

@alaskanarcher On the contrary, setuptools should never be needed at runtime! That was either an upstream bug or improper build on the part of this package (probably the latter). I don't think it was getting built at all, it was trying to run from a source version not the final state setuptools should have produced. That should be fixed now and I've moved the dep back where it belongs and confirmed the tooling works without.

Also I just had a look at the build sequence and the whole wheel routine should be skipped. Following the Arch package guidelines this should be downloaded from PiPy but using the special pythonhosted URLs that have predictable patterns. Then this can be built and install directly without as much song and dance.

This has several packaging problems and does not build cleanly is a chroot. Setup tools should not be a regular dependency but a makedependes (if at all, it may not even be used). Meanwhile pip should not be a make dependency at all, instead whatever the package thinks it needs to use pip to download should be added directly as a dependency.

If you'd like me to help fix it up you can add me as a co-maintainer.

@gyscos fixed.

I think it requires cbor2, which doesn't seem to be available in the packages?

yaml2json is not shipped with haskell-yaml anymore. Does that resolve the conflict?