Hello, I just started clean archlinux container to see what's up with the dependencies. Seems like it is more than just aubio missing. I got to this list before hitting high enough wall: depends=('ffmpeg' 'avahi' 'pulseaudio' 'python-pyaudio-git' 'python-voluptuous' 'python-rpi-ws281x' 'python-uvloop' 'python-pillow' 'python-zeroconf') makedepends=('git' 'python-setuptools' 'python-wheel' 'python-pip' 'portaudio' 'ffmpeg') But then it also looks for python-tcp-latency, which does not exist in AUR. Also the python-voluptuous package is set to voluptuous~=0.12.1 in requires.txt but the version in Arch community repo is already 0.13.1. I still use ledfx but I think it is simpler to run this one in virtualenv. I will orphan it so you can possibly hunt down all the dependencies and create packages for missing python modules. Best regards, Jānis On Thu, Feb 9, 2023 at 12:42 AM Polarian <polarian@polarian.dev> wrote:

Hello,

I would like to point out the idea of -git packages are to build the latest commit to upsteam, their version are never bumped, and thus the "package being out of date" is an invalid reason for an orphan.

I noticed you only reported this issue recently, and the previous flag out of date is invalid, therefore there is no timeline to this orphan, and thus a TU is unlikely to accept it.

Have you attempted to contact the packager, do that and ask if he will fix the issue.

If he does not reply within a few weeks, then it is likely the package orphan request might be accepted.

I believe it is 90 days which is given before it is automatically orphaned.

I am not a TU, this is just some advice.

Good luck! -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev

I have opened an issue on the LedFX github and they don't seem to be the authors of the aur package. https://github.com/LedFx/LedFx/issues/304#issuecomment-1423339854 Lets see if the author responds soon and can update the package. On Thu, 9 Feb 2023, 00:29 Polarian, <polarian@polarian.dev> wrote:

Hello,

The issue here is, you got to give the current maintainer time to solve it themselves, you are not the maintainer of this package, and you can't request an orphan because you want to own it.

However, you could request the maintainer to add you as a co-maintainer.

Otherwise your only option is to prove the current maintainer is not actively maintaining the package, and thus warrants a orphan.

Hope this help, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@polarian.dev