Harry,
This is feedback just after an update action: 8627c41906270011
Best regards, Jochem
Hi Jochem,
I know what the issue is which prevents the update to being applied.
2 ways to solve this:
Wait for the next stable release (where this is resolved), or switch to the beta channel.
Thanks for the feedback!
Hi Harry,
I switched to the beta channel, but the problem remains - I stay at 2.450 beta.
This is the feedback after pressing the update button: c031682996ebaa7b
Best regards,
Jochem
Thanks @Jochem_Herrmann
Ok, as you’re on the beta channel we can now try to fix this…
I’ll put out an update later today that might solve it.
Regards,
Harry, I’ve started the update, but after 30 minutes the update was still busy.
Perhaps this feedback will help you: bd587d12504d9d36.
Until now I did not try to reboot by a power off cycle…
Jochem
Thanks for the feedback.
You can power cycle it, because it can not resolve some dependancies.
I’ve pushed another update to the beta channel that might solve it.
Regards,
Harry,
A power cycle didn’t help - still at 2.450 beta. I tried to apply the update again, but it doesn’t complete within reasonable time. See feedback cdbd930ef4884690
Thanks for you support!
Jochem
Are you familiar with SSH?
Because something is going wrong, but the logs are missing the essential bit i need.
If you give me instructions, I’ll give it a try…
ok, login with SSH (username: root, password: root) and run the following command:
pacman -Syu
Send me the output of that command (do not confirm the choice).
Oops - not what you wanted…
[root@Woonkamer ~]# pacman -Syu
:: Synchronizing package databases…
error: failed to update ropieee-beta (unable to lock database)
error: failed to update core (unable to lock database)
error: failed to update extra (unable to lock database)
error: failed to update community (unable to lock database)
error: failed to update alarm (unable to lock database)
error: failed to synchronize all databases
[root@Woonkamer ~]#
ok, try again:
rm -f /var/lib/pacman/db.lck
pacman -Syu
:: Synchronizing package databases…
ropieee-beta is up to date
core is up to date
extra is up to date
community is up to date
alarm is up to date
:: Starting full system upgrade…
warning: firmware-raspberrypi: local (6-1) is newer than alarm (4-1)
:: Replace gmrender-ropieee with ropieee-beta/upmpdcli-ropieee? [Y/n]
Y or n?
ok good. Please continue by pressing enter or ‘y’
warning: raspberrypi-bootloader: local (20191211-1) is newer than alarm (20180810-1)
warning: raspberrypi-bootloader-x: local (20191211-1) is newer than alarm (20180810-1)
warning: raspberrypi-firmware: local (20191211-1) is newer than alarm (20180730-1)
resolving dependencies…
:: There are 2 providers available for libx264.so=152-32:
:: Repository extra
- libx264 2) libx264-10bit
Enter a number (default=1):
Ok. This is strange. Because this should be fixed…
Don’t confirm it (do a CTRL-C)
Can you run
pacman -Syu ropieee-xl
I just received a message that the system is going down for a reboot…
Broadcast message from root@Woonkamer (Sun 2020-07-12 21:04:00 CEST):
The system is going down for reboot at Mon 2020-07-13 03:04:00 CEST!
Yeah no problem. That’s what it scheduled for tonight 
Sorry - I pressed enter to get a command prompt, and now the installation is running.
Let’s see what that brings
The UI now tells it is running 2.551 beta, and
Update is being downloaded… Do not turn the device off!