Here is a list of the steps that needs to be taken to make sure that a "arch != all" dist-upgrader works. The good thing about this is that it can be done in parallel to the current (working) implementation that fetches the backports from the net.
Steps: - add new "UpgradeToolBaseURI" key to the meta-release file at http://changelogs.ubuntu.com/meta-release that contains the base-path to the upgrader - change DistUpgradeFetcher.py in update-manager--dapper to honor the new UpgradeToolBaseURI from the meta-release file and add "binary-$(dpkg --print-architecture)/current" to it - patch soyuz to accept raw-dist-upgrade uploads that are not arch==all and move them to "edgy/dist-upgrader/binary-$arch/$version" (+ keeping a current symlink) - change the dist-upgrader to check/use the backports in the tarbal - change the build-system of the dist-upgrader to make sure to include the right backported binary bits - change the update-notifier dist-upgrader on cdrom detection to search for CDROM_ROOT/dists/stable/dist-upgrader/binary-$(arch) - change the cd-build script (tools/edgy/upgrade.sh) to place the tarball into the CDROM_ROOT/dists/stable/dist-upgrader/binary-$(arch) subdir We can do all that in parallel to the current solution and only switch with the final update-manager backport upload. Does that sound ok? Cheers, Michael -- update-manager for edgy needs to upgrade dpkg/apt before calculating the upgrade to support the new "breaks" - otherwise the upgrade may fail https://launchpad.net/bugs/54234 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
