[MB Premium Twin HD] Upgrade packages available immediately after an upgrade

[birdman]

I've just done an on-line update to 4.1.009 and having done so I'm being told that there are updates available, namely:

root@mbtwin:~# opkg list-upgradable
oe-alliance-base - 5.3-r1 - 5.3-r2
avahi-daemon - 0.6.32-r0 - 0.6.32-r1

 

[birdman]

And an attempt to actually do those 2 updates produces:

root@mbtwin:~# opkg upgrade
Upgrading oe-alliance-base from 5.3-r1 to 5.3-r2 on root.
Downloading http://www.openvix.co.uk/feeds/openvix/release/4.1/inihdx/inihdx/oe-alliance-base_5.3-r2_inihdx.ipk.
oe-alliance-base: unsatisfied recommendation for kernel-module-msdos
oe-alliance-base: unsatisfied recommendation for kernel-module-nls-cp437
oe-alliance-base: unsatisfied recommendation for kernel-module-nls-iso8859-15
oe-alliance-base: unsatisfied recommendation for kernel-module-vfat
oe-alliance-base: unsatisfied recommendation for kernel-module-nls-iso8859-1
oe-alliance-base: unsatisfied recommendation for kernel-module-fat
oe-alliance-base: unsatisfied recommendation for kernel-module-exportfs
Upgrading avahi-daemon from 0.6.32-r0 to 0.6.32-r1 on root.
Downloading http://www.openvix.co.uk/feeds/open.../mips32el/avahi-daemon_0.6.32-r1_mips32el.ipk.
* Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon
...fail!
To remove package debris, try `opkg remove avahi-daemon`.
To re-attempt the install, try `opkg install avahi-daemon`.
Upgrading avahi-daemon from 0.6.32-r0 to 0.6.32-r1 on root.
* Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon
...fail!
To remove package debris, try `opkg remove avahi-daemon`.
To re-attempt the install, try `opkg install avahi-daemon`.
Collected errors:
* pkg_run_script: package "avahi-daemon" prerm script returned status 1.
* prerm_upgrade_old_pkg: prerm script for package "avahi-daemon" failed
* pkg_run_script: package "avahi-daemon" prerm script returned status 1.
* prerm_upgrade_old_pkg: prerm script for package "avahi-daemon" failed

None of those recommended modules exists in OpenVix (presumably they are built-ion, rather than being modules), but they are only supposed to be recommendations (surely?)!

I've actually switched off the avahi daemon on my system, which might explain the stop failure, but the code should be able to handle that anyway.

 

[Bazzer]

I've just done an on-line update to 4.1.009 and having done so I'm being told that there are updates available, namely:

root@mbtwin:~# opkg list-upgradable
oe-alliance-base - 5.3-r1 - 5.3-r2
avahi-daemon - 0.6.32-r0 - 0.6.32-r1

Just updated my Mutant and nothing showing updates available and all working well

 

[twol]

And an attempt to actually do those 2 updates produces:


None of those recommended modules exists in OpenVix (presumably they are built-ion, rather than being modules), but they are only supposed to be recommendations (surely?)!

I've actually switched off the avahi daemon on my system, which might explain the stop failure, but the code should be able to handle that anyway.

Maybe something to do with the oe-alliance update on May 6th (Schimmelreiter )

 

[Huevos]

Make a backup and then do flash and restore.

 

[birdman]

A fresh flash has fixed the issue, thanks. No idea why an update from 4.1.004 should have failed.

I did have an issue along the way, though, as the reboot after the flash ended up with both the hdd and usb mounted as /media/hdd. So there was no backup to restore to get back to expectations...
I've sorted it out (at least I know what is going on and what to do about it, and it has happened on a few previous occasions), but there does some to be an issue related to the handling of boot-time hardware device discovery.