Posts: 1,425
Threads: 24
Joined: Jun 2022
Reputation:
51
The failure seems to happen in more than one case... maybe it's a bug...?
There is no way to reapply the update per-se, but I'd suggest this:
1. make a backup of your configuration, including the radio stations if you find that useful
2. flash the SDcard anew
3. restore from the backup, and voilà: a brand new 9.2.6 already configured as your previous version was.
Posts: 23
Threads: 6
Joined: Oct 2020
Reputation:
0
03-08-2025, 08:03 PM
(This post was last modified: 03-08-2025, 08:04 PM by wadada.)
MOODE Player 1:
20250308 205142 updater: Start 2025-03-07 update for moOde
20250308 205142 updater: ** Step 01-32: Remove package hold
20250308 205143 updater: ** Step 02-32: Update package list
20250308 205156 updater: ** Step 03-32: Update Linux kernel to 6.6.74
20250308 205156 updater: ** - Kernel is current, no update required
20250308 205156 updater: ** Step 04-32: Install moode-player=9.2.6-1moode1
20250308 205214 updater: ** Step failed
20250308 205214 updater: ** Exiting update
20250308 205214 updater: Install failed, update cancelled
MOODE Player 2:
....
20250308 205441 updater: ** - Remove unneeded APT archive files
20250308 205441 updater: ** Step 32-32: Sync changes to disk
20250308 205441 updater: Finish 2025-03-07 update for moOde
20250308 205442 updater: Update installed, restart required
....
Anyway, after reboot also Player 1 states:
moOde 9 series software is up to date
&&
moOde release = 9.2.6 2025-03-07
Posts: 32
Threads: 5
Joined: Feb 2021
Reputation:
2
The same here.
Tried to upgrade my 9.2.5:
Code: 20250308 201643 updater: Downloading package [update-moode9.zip]
20250308 201643 updater: Start 2025-03-07 update for moOde
20250308 201643 updater: ** Step 01-32: Remove package hold
20250308 201645 updater: ** Step 02-32: Update package list
20250308 201652 updater: ** Step 03-32: Update Linux kernel to 6.6.74
20250308 201652 updater: ** - Kernel is current, no update required
20250308 201652 updater: ** Step 04-32: Install moode-player=9.2.6-1moode1
20250308 201703 updater: ** Step failed
20250308 201703 updater: ** Exiting update
20250308 201703 updater: Install failed, update cancelled
Now it shows: This release is: 9.2.6 2025-03-07
And when I click Check, it says: moOde 9 series software is up to date
Posts: 14,140
Threads: 323
Joined: Mar 2018
Reputation:
578
The update script now has standard BASH condition code checking which means it's accurately reporting that a package install or other part of the script did not complete successfully.
The update process depends on solid network connections to the remote package repositories, and repos that aren't super busy (overcommitted with requests). That fact that there are success cases suggests the script is ok and the failure cases suggest a network, repo or other non-script issue thats preventing a successful package install.
Keep in mind that the earlier script just reported the installation step whether or not the underlying package install actually completed successfully. Not good.
If you want to try and run the update manually use the command below.
Code: sudo /var/www/util/system-updater moode9
Posts: 15
Threads: 3
Joined: May 2020
Reputation:
0
03-08-2025, 10:04 PM
(This post was last modified: 03-08-2025, 10:37 PM by Rees86.)
(03-08-2025, 09:22 PM)Tim Curtis Wrote: The update script now has standard BASH condition code checking which means it's accurately reporting that a package install or other part of the script did not complete successfully.
The update process depends on solid network connections to the remote package repositories, and repos that aren't super busy (overcommitted with requests). That fact that there are success cases suggests the script is ok and the failure cases suggest a network, repo or other non-script issue thats preventing a successful package install.
Keep in mind that the earlier script just reported the installation step whether or not the underlying package install actually completed successfully. Not good.
If you want to try and run the update manually use the command below.
Code: sudo /var/www/util/system-updater moode9
Hi Tim, in case it's helpful here is the output from running the manual update command. This is on a Raspberry Pi Zero 2
Host: Pi-Zero
RPiOS: 12.5 Bookworm 64-bit | Linux: 6.6.31 64-bit
Model: Pi-Zero 2 W 512MB
Audio: Pi HDMI 1
m o O d e a u d i o p l a y e r
Release 9.0.6 2024-08-03
© 2014 Tim Curtis
Code: rees@Pi-Zero:/var/www/util $ sudo /var/www/util/system-updater.sh moode9
Downloading package [update-moode9.zip]
**********************************************************
**
** This process updates moOde to the latest release.
** Reboot after the update completes.
**
**********************************************************
Start 2025-03-07 update for moOde
** Step 01-32: Remove package hold
moOde-apt-hold
Canceled hold on upmpdcli.
Canceled hold on alsa-cdsp.
Canceled hold on alsacap.
Canceled hold on bluez-alsa-utils.
Canceled hold on camilladsp.
Canceled hold on camillagui.
Canceled hold on caps.
Canceled hold on chromium-browser.
Canceled hold on chromium-browser-l10n.
Canceled hold on chromium-codecs-ffmpeg-extra.
Canceled hold on libasound2-plugin-bluez.
Canceled hold on librespot.
Canceled hold on mediainfo.
Canceled hold on minidlna.
Canceled hold on moode-player.
Canceled hold on mpd.
Canceled hold on mpd2cdspvolume.
Canceled hold on python3-camilladsp.
Canceled hold on python3-camilladsp-plot.
Canceled hold on python3-libupnpp.
Canceled hold on python3-camilladsp.
Canceled hold on python3-camilladsp-plot.
Canceled hold on raspberrypi-kernel.
Canceled hold on raspberrypi-bootloader.
Canceled hold on shairport-sync.
Canceled hold on squeezelite.
Canceled hold on trx.
Canceled hold on udisks.
Canceled hold on udisks-glue.
Canceled hold on upmpdcli.
** Step 02-32: Update package list
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease
Get:5 https://dl.cloudsmith.io/public/moodeaudio/m8y/deb/raspbian bookworm InRelease [9,657 B]
Fetched 9,657 B in 3s (3,317 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
213 packages can be upgraded. Run 'apt list --upgradable' to see them.
** Step 03-32: Update Linux kernel to 6.6.74
** - Updating...
dpkg-query: no packages found matching rtl88xxau-*
** - Prepare environment
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
chromium-browser : Depends: chromium
chromium-browser-l10n : Depends: chromium-browser (< 126.0.6478.164-rpt1.1~)
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
** Step failed
** Exiting update
Install failed, update cancelled
EDIT: Running "sudo apt --fix-broken install" did the trick, afterwards the update worked just fine
Posts: 14,140
Threads: 323
Joined: Mar 2018
Reputation:
578
(03-08-2025, 10:04 PM)Rees86 Wrote: (03-08-2025, 09:22 PM)Tim Curtis Wrote: The update script now has standard BASH condition code checking which means it's accurately reporting that a package install or other part of the script did not complete successfully.
The update process depends on solid network connections to the remote package repositories, and repos that aren't super busy (overcommitted with requests). That fact that there are success cases suggests the script is ok and the failure cases suggest a network, repo or other non-script issue thats preventing a successful package install.
Keep in mind that the earlier script just reported the installation step whether or not the underlying package install actually completed successfully. Not good.
If you want to try and run the update manually use the command below.
Code: sudo /var/www/util/system-updater moode9
Hi Tim, in case it's helpful here is the output from running the manual update command. This is on a Raspberry Pi Zero 2
Host: Pi-Zero
RPiOS: 12.5 Bookworm 64-bit | Linux: 6.6.31 64-bit
Model: Pi-Zero 2 W 512MB
Audio: Pi HDMI 1
m o O d e a u d i o p l a y e r
Release 9.0.6 2024-08-03
© 2014 Tim Curtis
Code: rees@Pi-Zero:/var/www/util $ sudo /var/www/util/system-updater.sh moode9
Downloading package [update-moode9.zip]
**********************************************************
**
** This process updates moOde to the latest release.
** Reboot after the update completes.
**
**********************************************************
Start 2025-03-07 update for moOde
** Step 01-32: Remove package hold
moOde-apt-hold
Canceled hold on upmpdcli.
Canceled hold on alsa-cdsp.
Canceled hold on alsacap.
Canceled hold on bluez-alsa-utils.
Canceled hold on camilladsp.
Canceled hold on camillagui.
Canceled hold on caps.
Canceled hold on chromium-browser.
Canceled hold on chromium-browser-l10n.
Canceled hold on chromium-codecs-ffmpeg-extra.
Canceled hold on libasound2-plugin-bluez.
Canceled hold on librespot.
Canceled hold on mediainfo.
Canceled hold on minidlna.
Canceled hold on moode-player.
Canceled hold on mpd.
Canceled hold on mpd2cdspvolume.
Canceled hold on python3-camilladsp.
Canceled hold on python3-camilladsp-plot.
Canceled hold on python3-libupnpp.
Canceled hold on python3-camilladsp.
Canceled hold on python3-camilladsp-plot.
Canceled hold on raspberrypi-kernel.
Canceled hold on raspberrypi-bootloader.
Canceled hold on shairport-sync.
Canceled hold on squeezelite.
Canceled hold on trx.
Canceled hold on udisks.
Canceled hold on udisks-glue.
Canceled hold on upmpdcli.
** Step 02-32: Update package list
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 http://archive.raspberrypi.com/debian bookworm InRelease
Get:5 https://dl.cloudsmith.io/public/moodeaudio/m8y/deb/raspbian bookworm InRelease [9,657 B]
Fetched 9,657 B in 3s (3,317 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
213 packages can be upgraded. Run 'apt list --upgradable' to see them.
** Step 03-32: Update Linux kernel to 6.6.74
** - Updating...
dpkg-query: no packages found matching rtl88xxau-*
** - Prepare environment
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
chromium-browser : Depends: chromium
chromium-browser-l10n : Depends: chromium-browser (< 126.0.6478.164-rpt1.1~)
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
** Step failed
** Exiting update
Install failed, update cancelled
EDIT: Running "sudo apt --fix-broken install" did the trick, afterwards the update worked just fine
Thanks. The driver below has not been part of the build for a couple years but it was still being checked during the kernel bump. It won't affect the bash condition code but I'll put on the TODO list to remove it from the script.
dpkg-query: no packages found matching rtl88xxau-*
Posts: 85
Threads: 15
Joined: Mar 2021
Reputation:
11
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
Posts: 14,140
Threads: 323
Joined: Mar 2018
Reputation:
578
(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.
Posts: 85
Threads: 15
Joined: Mar 2021
Reputation:
11
(03-08-2025, 11:59 PM)Tim Curtis Wrote: "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.
Thank you for considering this, Tim!
Posts: 589
Threads: 5
Joined: Mar 2020
Reputation:
33
Hi Tim,
Thanks you and all team for the last release (9.2.6). I have updated one of my systems without any problem.
thanks also for having modified the radio's URL: please note that a couple of them results not yet modified:
Code: Id Station Old URL New URL
4 6forty Radio http://54.173.171.80... http://radio.6forty.com:8000/6forty
95 Hi On Line - Pop (320K) http://mediaserv30... https://mediaserv33.live-streams.nl:8036/stream
If it is possible (and if you wish), please, take note for the 9.2.7 or 9.3.0 or, may be, 10.0.0.
Best regards and thanks again,
Francesco
|