Public bug reported: Binary package hint: update-manager
During the upgrade process (update-manager -d) my network connection died and instead of the regular contents some 'helpful' HTML page from the wireless router ended up being written there. When I reconnected and restarted update-manager it wouldn't find Maverick beta even if it did before. The problem can be replicated by writing random garbage to /var/lib /update-manager/meta-release-development (possibly other similar files as well). Looks like update-manager/do-release-upgrade should re-download a meta- release file if it contents is not in the right format. In short: ~# export DEBUG_UPDATE_MANAGER=true ~# rm /var/lib/update-manager/meta-release-development ~# echo "FOO" > /var/lib/update-manager/meta-release-development ~# do-release-upgrade -d Checking for a new ubuntu release MetaRelease.__init__() useDevel=True useProposed=False /etc/update-manager/meta-release: http://changelogs.ubuntu.com/meta-release /etc/update-manager/meta-release: http://changelogs.ubuntu.com/meta-release-lts /etc/update-manager/meta-release: -development /etc/update-manager/meta-release: -proposed metarelease-uri: http://changelogs.ubuntu.com/meta-release-development MetaRelease.download() result of meta-release download: 'HTTP Error 304: Not Modified' reading file '/var/lib/update-manager/meta-release-development' have self.metarelease_information MetaRelease.parse() current dist name: 'lucid' current dist not found in meta-release file No new release found ~# rm /var/lib/update-manager/meta-release-development ~# do-release-upgrade -d Checking for a new ubuntu release MetaRelease.__init__() useDevel=True useProposed=False /etc/update-manager/meta-release: http://changelogs.ubuntu.com/meta-release /etc/update-manager/meta-release: http://changelogs.ubuntu.com/meta-release-lts /etc/update-manager/meta-release: -development /etc/update-manager/meta-release: -proposed metarelease-uri: http://changelogs.ubuntu.com/meta-release-development MetaRelease.download() have self.metarelease_information MetaRelease.parse() current dist name: 'lucid' found distro name: 'warty' found distro name: 'hoary' found distro name: 'breezy' found distro name: 'dapper' found distro name: 'edgy' found distro name: 'feisty' found distro name: 'gutsy' found distro name: 'hardy' found distro name: 'intrepid' found distro name: 'jaunty' found distro name: 'karmic' found distro name: 'lucid' found distro name: 'maverick' new dist: <UpdateManager.Core.MetaRelease.Dist object at 0x97b454c> ...and so on, the proper upgrade procedure started. Package version: $ apt-cache policy update-manager-core update-manager-core: Installed: 1:0.134.10 Candidate: 1:0.142.16 Version table: 1:0.142.16 0 500 http://gb.archive.ubuntu.com/ubuntu/ maverick/main Packages *** 1:0.134.10 0 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: update-manager-core 1:0.134.10 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 Architecture: i386 Date: Sat Oct 2 04:47:25 2010 InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1) ProcEnviron: PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: update-manager ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- Broken /var/lib/update-manager/meta-release-development file is not re-downloaded https://bugs.launchpad.net/bugs/653412 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
