DietPi-Software | Shairport Sync: Install fails on ARMv6 images

[keesma]

DietPi-Software | Shairport Sync: Install fails on ARMv6 images

[Joulinar]

hmm you are running quite old Debian Buster system, which we will drop support on upcoming release.

Anyway, maybe we need to check dependency as we build the package ourselves.

@MichaIng I tested on ARMv6 RPi image on my RPi3B+ and it seems RPi repository is behind Debian repository

Bookwoorm

The following packages have unmet dependencies:
 shairport-sync : Depends: libglib2.0-0 (>= 2.74.6-2) but it is not going to be installed

root@DietPi3:~# apt show libglib2.0-0
Package: libglib2.0-0
Version: 2.74.6-1

On Bullseye it seems to be fine. For Buster I don't have a test system anymore.

[Joulinar]

uhhh it seems I deleted a comment by mistake

Reply from @keesma

I solved it with:
sudo dpkg --configure -a
sudo apt-get install -f
apt --fix-broken install
and a reboot

[MichaIng]

We can test this nicely here 😉: https://github.com/MichaIng/DietPi/actions/runs/7493666412

I wonder whether we should just remove the dependencies' version requirements for our packages. In theory, library versions need to match those the package was compiled against, but practically Debian very rarely ships breaking changes on a stable version, and the other way round we regularly face(d) issues between Debian and Raspbian with the versions added. We do already remove +bN, +rptN and +rpiN suffixes for this reason, but as can be seen, we'd need to remove debNuN and even -N as well, and still won't be sure to catch all cases.

The alternative would be to strictly install only ARMv6 packages on Raspbian, so the versions are assured to be available, since we compile ARMv6 packages on Raspbian containers (of course). But the benefit of smaller binaries and others thanks to NEON would be lost on ARMv7 capable RPi models.

In a perfect world, we would define exactly those minimum versions which really are required based on the library functions used and when breaking changes affected them, but this is something we can impossibly maintain.

[MichaIng]

EDIT: Ah dammit, not so easy to test on GitHub, since these are either Raspbian containers with ARMv6 arch hardcoded (hence the ARMv7 packages are not installed) or ARMv7 arch on Debian, where the latest library versions are available 🙈. At least we can see in the logs which library version was installed. I'll patch the packages on the server for now.

[MichaIng]

Should be fixed for Buster and Bookworm (no issue on Bullseye), please try again.