RoonBridge 2.71 (build 1683) update fails on (some) DietPi Installations due to new libicu dependency

Edit: Changed dietpi version referenced.

I have four Raspberry Pi 4bs running DietPi (10.6.2 Trixie) with all packages kept up to date.

On three of these Raspberry Pis, the update to RoonBridge 2.71 proceeded without issue.

However, on the 4th Raspberry Pi, post install the RoonBridge service failed to run. Looking at the logs, there was a dependency upon a missing library - libicu.

Installing libicu using “apt install libicu76” allowed me to successfully start the Roon Bridge service on this fourth Raspberry Pi.

Thus it appears that RoonBridge 2.71 introduces a new dependency that the update process does not accommodate.

F.Y.I. The Raspberry Pi in question runs a pretty minimal install of DietPi with, essentially, just RoonBridge , Samba client and server and Dietpi-dashboard installed. In addition it employs a USB connected DAC whereas the other three Raspberry Pis (with fairly similar minimal DietPi installs but with Samba client and server) all use an audio HAT of one type or another and all had libicu76 already installed - presumably because other installed packages had a dependency on libicu - which allowed the RoonBridge update to proceed without issue.

Edit: Note. The install of libicu76 was required because my Dietpi installation was based on Debian Trixie. libicu does not appear to be available for Bookworm and so, on Bookwork based installs, the libicu package to be installed is likely to be libicu74 rather than libicu76.

Edit: it turns out that I was wrong about the packages installed on the Dietpi system for which the Roon Bridge update failed. It did not have the Samba client or server installed,

1 Like

This information was highly appreciated and crucial.
How is this even possible since this has been announced, beta-tested and debated since May?

Not even Ropieee developer was aware and i am convinced Harry and other developers were prepared for the forthcoming update. Jeez…

Edit: libicu76 was already installed on my DietPi CM5, but seem not to be included in the ARM v8 build of DietPi for the 3B+.

1 Like

Did this system have Samba client and/or server installed?

Did this system have Samba client and/or server installed?

I have discovered that, on my DietPi (Trixie) install on the RPI 4’s, Samba has a dependency upon samba-libs which in turn has a dependency on libicu76. Whilst the actual libicu version may differ, I suspect that other dietpi installations would pull in one libicu version or another when the Samba server and/or the client were installed.

The reason that the Roon Bridge update to 2.71 failed on one DietPi installation is because that particular installation did not include the Samba client or server whereas the other three did.

1 Like

No, not Samba, but it might be a dependancy for GMediaRenderer:

I used to have that on my Pi3B+'s as well, but recently removed it.
(I occasionally use JPLAY for playback)

They are all om Trixie btw, and up to date, 10.6.2