Ubuntu
update-manager package

  1. Bug #54234
  2. Comment #16

Comment 16 for bug 54234

Revision history for this message
Matt Zimmerman (mdz) wrote : Re: [Bug 54234] Re: update-manager for edgy needs to upgrade dpkg/apt before calculating the upgrade to support the new "breaks" - otherwise the upgrade may fail

On Tue, Sep 26, 2006 at 02:18:24PM -0000, Michael Vogt wrote:
> 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?

Hmm, I didn't realize we didn't have support for arch-any upgrader tarballs
yet.

In light of this, and the beta release, I think we should take a
conservative approach and not use Breaks in main. It seems to be used in
only 3 packages at present, and these can be reverted to conflicts for now.

Both the fetching of backports from the network, and support for backports
in the tarball are useful features that we want, but we'll have to put them
on hold for Edgy.

Please ensure that we have upgrade instructions ready for inclusion in the
beta announcement, as this is our best chance for pre-release upgrade
testing.

--
 - mdz