Ubuntu
update-manager package

update-manager problem when upgrading from Feisty to Gutsy

Bug #153958 reported by TZRick
8
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I used the update-manager app from the Feisty GUI to update to Gutsy. However, during the "Preparing for Upgrade" phase, the process errored-out and told me to report a bug for update-manager and provide the files located in /var/log/dist-upgrade (not sure how to do that quite yet.

My current Feisty system is relatively plain vanilla. I've only really been experimenting with the networking aspect and Samba to try to set up a home file-sharing network. I also use a nVidia Geforce II GTS card, which is ancient, but works decently enough for now...I know there were always driver issues with these older cards.

So...ideas?

Thank you!

Tags: feisty2gutsy
Revision history for this message
TZRick (t-rick-geo) wrote :

main.log:

2007-10-18 11:26:39,832 INFO release-upgrader version '0.81' started
2007-10-18 11:26:41,382 DEBUG lsb-release: 'feisty'
2007-10-18 11:26:41,383 DEBUG _pythonSymlinkCheck run
2007-10-18 11:26:44,845 DEBUG checkViewDepends()
2007-10-18 11:26:44,847 DEBUG getRequiredBackports()
2007-10-18 11:29:20,595 ERROR IOError in cache.update(): 'Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/free/binary-i386/Packages.gz 302 Found
Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/non-free/binary-i386/Packages.gz 302 Found
Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/free/source/Sources.gz 302 Found
Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/non-free/source/Sources.gz 302 Found
'. Retrying (currentRetry: 0)
2007-10-18 11:29:42,899 ERROR IOError in cache.update(): 'Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/free/binary-i386/Packages.gz 302 Found
Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/non-free/binary-i386/Packages.gz 302 Found
Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/free/source/Sources.gz 302 Found
Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/non-free/source/Sources.gz 302 Found
'. Retrying (currentRetry: 1)
2007-10-18 11:30:08,298 ERROR IOError in cache.update(): 'Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/free/binary-i386/Packages.gz 302 Found
Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/non-free/binary-i386/Packages.gz 302 Found
Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/free/source/Sources.gz 302 Found
Failed to fetch http://medibuntu.sos-sts.com/repo/dists/feisty/non-free/source/Sources.gz 302 Found
'. Retrying (currentRetry: 2)
2007-10-18 11:30:08,299 ERROR doUpdate() failed complettely
2007-10-18 11:30:16,439 DEBUG marking 'release-upgrader-apt' for install
2007-10-18 11:30:16,673 DEBUG marking 'release-upgrader-dpkg' for install
2007-10-18 11:38:48,702 DEBUG pre-requists item: '<pkgAcquire::ItemIterator object: Status: 3 Complete: 0 Local: 0 IsTrusted: 1 FileSize: 1924684 DestFile:'/tmp/tmpCq_q9m/backports/partial/release-upgrader-dpkg_1.14.5ubuntu11.2_i386.udeb' DescURI: 'http://us.archive.ubuntu.com/ubuntu/pool/main/r/release-upgrader-dpkg/release-upgrader-dpkg_1.14.5ub'
2007-10-18 11:38:48,703 DEBUG pre-requists item: '<pkgAcquire::ItemIterator object: Status: 3 Complete: 0 Local: 0 IsTrusted: 1 FileSize: 1307096 DestFile:'/tmp/tmpCq_q9m/backports/partial/release-upgrader-apt_0.6.46.4ubuntu10.3_i386.udeb' DescURI: 'http://us.archive.ubuntu.com/ubuntu/pool/main/r/release-upgrader-apt/release-upgrader-apt_0.6.46.4u'
2007-10-18 11:38:48,705 ERROR no backports found but setupRequiredBackports() called??!

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you try removing the medibuntu line from '/etc/apt/sources.list' and then try upgrading? Thanks in advance.

Revision history for this message
Thomas Borchsenius (thomas-borchsenius) wrote :

It seems suggestion in the last post works. I had the same problem, and I applied the "fix" and now I've passed the "Preparing the upgrade"-stage.

Revision history for this message
dejerk (tiagodenczuk) wrote :

I think that's because Medibuntu repositories have moved to a new place
http://www.medibuntu.org/
You should update your sources list...
More about it at
https://help.ubuntu.com/community/Medibuntu#head-7486ed038a9becc1dff10a24cc07a38a00d70e9f

Revision history for this message
TZRick (t-rick-geo) wrote :

Brian,

Your advice worked like a charm. I am now writing this after a successful upgrade to Gutsy! Thank you!

Dejerk: Thanks for the tip on Medibuntu's new location. I tried re-enabling the old location (modified for Gutsy) but it didn't work. Your correction works. Thank you as well!

Revision history for this message
TZRick (t-rick-geo) wrote :

FYI: I think for the next release, external sources should be disabled until the new O/S is running, and then the external sources can be re-enabled. I think this would be a good feature request...what do you think?

Revision history for this message
Brian Murray (brian-murray) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

In regards to your feature request - unknown repositories are disabled during upgrades with Gutsy.

Changed in update-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.