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 Fri, Sep 29, 2006 at 10:02:52AM -, Andreas Constantinides wrote: > will trying to upgrade (gksu "upgrade-manager -c -d") from dapper to edgy I > got this error: This is unrelated to this bug; please avoid discussing other problems in this bug report as it causes confusion for other users who may read it. -- - mdz -- 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
[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
thanks I'll try removing that. -- 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
[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
Solution : Remove the "libgl1-mesa-dri" package from Beerorkid repository "deb http://www.beerorkid.com/compiz/ dapper main" which breaks the update. gksu "upgrade-manager -c -d" should then work. -- 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
[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
hi will trying to upgrade (gksu "upgrade-manager -c -d") from dapper to edgy I got this error: "could not calculate the upgrade" I am attaching the bugreport can you help? I just want to try the new release ** Attachment added: "apt.log" http://librarian.launchpad.net/4541422/apt.log -- 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
[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
Removed the beta-blocker tag. We do not ship any package that uses Breaks so this is not required for the dapper->edgy upgrade. ** Changed in: update-manager (Ubuntu) Target: ubuntu-6.10-beta => None -- 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
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 -, 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 -- 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
[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
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
[Bug 54234] 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 Fri, Sep 22, 2006 at 11:12:04PM -, Michael Vogt wrote: > Here is the current status for this bug: > - a new version of the dist-upgrader is uploaded. it supports fetching of > selected backports from arbitrary sources.list fragments (e.g. > dapper-backports) > - it will get and unpack those packages into a tempdir and modify > PATH,LD_LIBRARY_PATH and PYTHONPATH to make sure that the updated versions > are used > - it will re-exec itself once the update is fetched to support the new > libraries > - it will still work with --cdrom, even if no updates are found on the cdrom > if a network is used > > Still todo: > 1. get the backports into the official dapper-backports > 2. add the backports to the CD > 3. make dist-upgrader look for the backports on CD first (to support upgrades > without network) I don't like the idea of relying on dapper-backports for this; I think we should ship the upgrader complete and independent of any external packages. -- - mdz -- 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
[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
@mdz: If we would ship the updated tools in the tarball that would indeed solve the problems. To do this, we would still need to build a backported libapt/dpkg on a dapper system (because of new glib2.4 symbols it won't run on dapper when build on edgy) and put that in the tarball. The tarball itself would need to be placed in edgy/dist- upgrader-$(ARCH). Currently soyuz custom upload-format code for this is not able to deal with a arch-dependant dist-upgrader unfortunately. The update-manager assumes a ARCH=all as well (but this would be trivial to fix and put into dapper-updates). My current solution for this is outlined above. To me it looks not optimal either way. Putting it all into a tarball make the code easier but it involves more work with the build-system and additional soyuz work. I would appreciate your input on this (which of the two poisons to pick). 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
[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
Here is the current status for this bug: - a new version of the dist-upgrader is uploaded. it supports fetching of selected backports from arbitrary sources.list fragments (e.g. dapper-backports) - it will get and unpack those packages into a tempdir and modify PATH,LD_LIBRARY_PATH and PYTHONPATH to make sure that the updated versions are used - it will re-exec itself once the update is fetched to support the new libraries - it will still work with --cdrom, even if no updates are found on the cdrom if a network is used Still todo: 1. get the backports into the official dapper-backports 2. add the backports to the CD 3. make dist-upgrader look for the backports on CD first (to support upgrades without network) ** Changed in: update-manager (Ubuntu) Status: Confirmed => In Progress -- 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
[Bug 54234] 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
So, following discussion on IRC, as I understand it the things that still need to be done are: * Put apt/dpkg/python-apt into dapper-backports; AIUI we have the appropriate sources for these packages ready and we have (or can easily have) binary builds for testing - for now, the update-manager can download these from people.u.c or similar, and this will be rectified when soyuz backports are fixed. * Arrange for update-manager to look on the CD for these files, as well as being able to download them (the latter is already done). * Arrange for the CD build to contain these files in the appropriate place on the CD as required by update-manager. Ian. -- 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
[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
This is precisely the reason why we ship the upgrader as a tarball rather than as a package. If it requires additional tools which aren't available in the old version, they should be shipped with the upgrader. This would seem to address all of the issues described here. Note that shipping an updated apt and dpkg in -updates has exactly the same issues as doing a partial upgrade first, in that it is irreversible. Furthermore, this upgrade would be applied for users even if they never upgraded, in which case it is unnecessary. -- 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
[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
Next problem. For CDROM upgrades (that should be done without network) we won't be able to get a backported apt from the net. Solutions: a) don't have packages with "Breaks" on the CD b) put a backported apt/python-apt onto the CD -- 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
