[PROBLEM] Upgrading from a very old version (1.05a)

[syco]

(13th Jan, 2015 01:44 PM)mk01 Wrote:  @syco

is this really from A5 ?
Only TESTED (and originally prepared/designed) upgrade way from A5 was through A5->B1->B2->XXX.

XBian preB2 releases required strict DOWN-oneversion-UP policy when upgrading because specially xbian-update-magic (and content) was containing ONLY INCREMENTAL differences between those versions.
Only with B2 and higher previous/current state doesn't matter because none XBian package currently depends on it's predecessor (except for data of course).

Yes, that means that you should be able to upgrade from A5 to current with no issues - and yes, technically you can. What is holding you back are not aligned version dependencies currently valid with version ~4 generations old.
If you want to keep your A5 systems, update this hackerish way: force remove all XBian packages, install back.

so on running A5:

Code:

dpkg-query -W xbian\* | awk '$2 != "" ' | xargs -L1 dpkg --force-all -r
apt-get install -f
apt-get dist-upgrade
apt-get install -y --force-yes -o Acquire::Languages=none -o APT::Install-Suggests=0 \
                    -o APT::Install-Recommends=0 -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" \
                    net-tools firmware-ralink firmware-realtek firmware-atheros isc-dhcp-client policykit-1 \
                     xbian-package-kernel xbian-package-cec xbian-package-config-shell \
                     xbian-package-config-xbmc xbian-package-firmware xbian-package-initramfs-tools  \
                    xbian-package-libtag xbian-package-lirc xbian-package-samba xbian-package-shairplay \
                    xbian-package-splash xbian-package-upstart-xbmc-bridge xbian-package-usbmount \
                     xbian-package-vnc-server xbian-package-xbianhome xbian-package-xbmc \
                    xbian-package-xbmc-scripts xbian-package-zram-swap xbian-update

No, no, I do not want to stay on 1.05a. I want to upgrade to the newest version, either RC2 or RC3 ... and that is not working, as you can see following this thread history.