Arch Linux User Repository

I cleaned up the PKGBUILD a little. The install file is unnecessary. See: https://framagit.org/elvirolo/aur-squeezelite-git

For some (and most probably completely unrelated) reason, I get sound with my version while I didn't with this one.

edit: FWIW, please note that the default output is Pulseaudio.

Do you need to add the "-M" flag to the useradd command?

pwck fails with the message "user 'squeezelite': directory '/home/squeezelite' does not exist" so I had to amend the user to change the home directory to root.

Can this package be run without the squeezelite user being in the audio group? I've tried without success. I'm asking because to get audio to work for other users, I then have to add them to the audio group as well, which the wiki discourages.

I see the -C option, which may allow other users to play audio if squeezelite is inactive, but that seems a bit kludgy.

Also the option LimitRTPRIO=99 in systemd service should be changed to LimitRTPRIO=98 99 is not possible for applications

==> Starting pkgver()... ==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace. ==> ERROR: pkgver() generated an invalid version: 1.9 0 1121

v v.a203cd2 ==> ERROR: Makepkg was unable to build squeezelite-git.

Since moving to Arch Linux ARM 14.6.x I've found that squeezelite on my Pogoplug V4 slows down the system to almost a lockup. Ssh login normally takes 1-3 sec, but take 15 sec or more, getting progressively worse with each session.

On a Pogoplug E02 the slowdown was not so noticeable. On both I noticed free memory much lower than with earlier kernels, and traced the issue down to squeezelite taking up a lot of the meagre memory on the v4, leaving barely any memory for anything else.

In the squeezelite.service file there's a line

LimitMEMLOCK=infinity

I commented out the line, and this issue has disappeared. Performance of squeezelite does not seem to have been affected. FYI, the Pogoplug V4 has 128MB of memory. The memory usage is now:

          total        used        free      shared  buff/cache   available

Mem: 119004 36992 2064 400 79948 76236

Previously buff/cache would be noticeable higher (free would be 300-400), and the buff/cache memory seemed to be locked.

Can anyone help me understand the LimitMEMLOCK directive for the service? Is it really required? Thanks.

Same here, thanks to you both

Thanks FabioLolix for fixing and adopting this package.

Thanks IanDury found it, blacklisted CFLAGS and used OPTS= instead