Arch Linux User Repository

@ciros apologies. Orphaned. :)

still broken and out of date, seems unmanaged. cloverskull: please orphan the package so somebody else can mantains it

The root cause seems to be that the setup.py install command doesn't have a --root argument at all, so it doesn't install to $pkgdir like it should. Here's a patch for the issue (apply with git am file.patch).

From 39dc6aaaee0beb96e2285441796a9d81a07060fa Mon Sep 17 00:00:00 2001
From: Matti Niemenmaa <matti.niemenmaa+git@iki.fi>
Date: Sat, 1 Oct 2022 17:02:09 +0300
Subject: [PATCH] Patch `setup.py install` to obey `$pkgdir`

And pass `--optimize=1` while we're at it.
---
 PKGBUILD                | 13 ++++++++++---
 python-setup-args.patch | 11 +++++++++++
 2 files changed, 21 insertions(+), 3 deletions(-)
 create mode 100644 python-setup-args.patch

diff --git a/PKGBUILD b/PKGBUILD
index bdaddea..b7bcf91 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,8 +9,15 @@ url="https://zakalwe.fi/uade"
 license=('GPL')
 depends=('libao' 'fuse2' 'bencodetools')
 install=uade.install
-source=("https://zakalwe.fi/uade/uade3/$pkgname-$pkgver.tar.bz2")
-md5sums=('57cb58c3da91c1fb2d391966c44d5739')
+source=("https://zakalwe.fi/uade/uade3/$pkgname-$pkgver.tar.bz2"
+        python-setup-args.patch)
+md5sums=('57cb58c3da91c1fb2d391966c44d5739'
+         'cefb1e0833fc3798201b73144eb693a7')
+
+prepare() {
+  cd $pkgname-$pkgver
+  patch < ../python-setup-args.patch
+}

 build() {
   cd $pkgname-$pkgver
@@ -20,6 +27,6 @@ build() {

 package() {
   cd $pkgname-$pkgver
-  make install
+  make install PYTHON_SETUP_ARGS_EXTRA="--root='$pkgdir' --optimize=1"
 }

diff --git a/python-setup-args.patch b/python-setup-args.patch
new file mode 100644
index 0000000..aa4de60
--- /dev/null
+++ b/python-setup-args.patch
@@ -0,0 +1,11 @@
+--- Makefile.in.orig   2022-06-03 22:49:26.000000000 +0300
++++ Makefile.in    2022-10-01 16:53:34.973132636 +0300
+@@ -77,7 +77,7 @@
+   $(MAKE) -C write_audio
+ 
+ writeaudioinstall:
+-  {PYTHON_INTERPRETER} setup.py install {PYTHON_SETUP_ARGS}
++  {PYTHON_INTERPRETER} setup.py install $(PYTHON_SETUP_ARGS_EXTRA) {PYTHON_SETUP_ARGS}
+   install -m 755 write_audio/write_audio "$(UADECOREDIR)"/
+   install -m 755 write_audio/generate_amiga_oscilloscope_view "$(BINDIR)"/
+ 
-- 
2.37.3

yep. broken for me too. same error as below.

Broken.

install "uadecore" "/home/rvalles/.cache/yay/uade/pkg/uade/usr/lib/uade"/
make[1]: Leaving directory '/home/rvalles/.cache/yay/uade/src/uade-3.02/src'
Setting umask 0022 for setup.py
/usr/lib/python3.10/site-packages/setuptools/dist.py:531: UserWarning: Normalizing '3.02' to '3.2'
  warnings.warn(tmpl.format(**locals()))
running install
/usr/lib/python3.10/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/usr/lib/python3.10/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
error: can't create or remove files in install directory

The following error occurred while trying to add or remove files in the
installation directory:

    [Errno 13] Permission denied: '/usr/lib/python3.10/site-packages/test-easy-install-1603967.write-test'

The installation directory you specified (via --install-dir, --prefix, or
the distutils default setting) was:

    /usr/lib/python3.10/site-packages/

Perhaps your account does not have write access to this directory?  If the
installation directory is a system-owned directory, you may need to sign in
as the administrator or "root" account.  If you do not have administrative
access to this machine, you may wish to choose a different installation
directory, preferably one that is listed in your PYTHONPATH environment
variable.

No, i meant first run has the error [1] ALSA lib pcm_dmix.c:1090:(snd_pcm_dmix_open) unable to open slave Can not open ao device: 1 and it starts to playback mods after it.

so, you could playback mods with uade only 2 times and then never again? that's odd.

no restrictions like these here, but i also did not modify any of my .confs, after all. still, i need "sudo" to get uade running without device / uadecore errors.

streamripping mods to wav like this is quite frustrating, as the resulting files are all admin addressed only...

i try always use sudo, but in case with uade it does not work from the user.

also after reboot uade started only at second time:

sudo uade123 jingle5.mod
[1] ALSA lib pcm_dmix.c:1090:(snd_pcm_dmix_open) unable to open slave

Can not open ao device: 1

uadecore: No more songs to play.

~/.../muzax/chip >>> sudo uade123 jingle5.mod

                     [1]

Song: jingle5.mod (24312 bytes)

uadecore: filter type: 1, force 0Playing time position 0.0s in subsong 1 (all suPlaying time position 6.0s in subsong 1 (all subs 17.4s)

uadecore: No more songs to play.

interesting.

but for playing back jingle5.mod you still make use of "sudo"?

this is exactly what i try to get rid of :) it should perfectly work without admin rights and give no errors at all.