03-08-2025, 11:59 PM
(03-08-2025, 11:51 PM)jenzd Wrote: Hi all,
I experienced a similar issue when I updated my Pis from version 9.2.5 to 9.2.6. Just that in my case the update failed one step later in "** Step 05-32: Install bluez-alsa-utils=4.2.0-2moode1". The reason turned out to be the modified bluez-alsa package with added AAC support (https://moodeaudio.org/forum/showthread.php?tid=6724).
This is not a standard configuration, of course, so I cannot really expect any official support. It used to work in the previous versions, though, where the package was just left untouched (as 4.2.0-2moode1+aac technically is a higher version than 4.2.0-2moode1).
Would it be possible to gracefully handle this condition, so that the update script just ignores/skips the step if an installed package already has a higher version than the version intended by the update?
Note that I could still successfully perform the update after it failed by
1) Manually downgrading to Moode's original bluez-alsa package and the moode-player package in version 9.2.5:
Code:sudo apt install bluez-alsa-utils=4.2.0-2moode1 libasound2-plugin-bluez=4.2.0-2moode1 moode-player=9.2.5-1moode1
2) Running the normal in-place update to version 9.2.6 in the GUI again - where it succeeded now.
3) Finally reinstalling the modified bluez-alsa package from the local source:
Code:sudo apt install ./bluez-alsa-utils_4.2.0-2moode1+aac_arm64.deb ./libasound2-plugin-bluez_4.2.0-2moode1+aac_arm64.deb
Best regards
Jens
"Would it be possible to gracefully handle this condition, so that the update script just ignores/skips the step if an installed package already has a higher version than the version intended by the update?"
Prolly could do that since the aac package is pretty desirable :-)
I'll add to the TODO list.