Upgrade to Gutsy fails with bzip2 error

Bug #156883 reported by impert
4
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

Tried to upgrade from Feisty to Gutsy on an AMD64 box, several times, using update manager. The server appeared to be overloaded the other day, but tonight the connection was working at between 60 and 260 kb/s. No other app's were open.
Failed to fetch http://security.ubuntu.com/ubuntu/dists/feisty-security/main/binary-amd64/Packages.bz2 Sub-process bzip2 returned an error code (2)
Failed to fetch http://security.ubuntu.com/ubuntu/dists/feisty-security/restricted/source/Sources.bz2 Sub-process bzip2 returned an error code (2)
I'll give it a try with the alternate CD tomorrow

Revision history for this message
impert (cwallace-free) wrote :
Revision history for this message
impert (cwallace-free) wrote :

26/10/2007 Tried again with update-manager. Same same. There is no problem with the net connection as I was able to download the binary gibberish in the bz2 files. Log files attached.
(Why does it go looking for Feisty bits when I want Gutsy? Mystery)

Revision history for this message
impert (cwallace-free) wrote :
Revision history for this message
impert (cwallace-free) wrote :
Revision history for this message
chovy (spam-chovy) wrote :

had same problem on kubuntu-64

Revision history for this message
impert (cwallace-free) wrote :

Still the same.

Revision history for this message
impert (cwallace-free) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.

Changed in update-manager:
status: New → Incomplete
Revision history for this message
impert (cwallace-free) wrote :

> We were wondering is this still an issue for you?

Not for me, (see my post above), but perhaps still for others.

Revision history for this message
Gareth Fitzworthington (mapping-gp-deactivatedaccount) wrote :

We are closing this bug report (no affirmative responses to questioning regarding present status of issue). Please reopen it if you think this issue requires on-going attention, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

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.

Other bug subscribers

Remote bug watches

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