update-manager fails on dist-upgrade 7.04 to 7.10
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| update-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: update-manager
running the update manager trying to update from 7.04 to 7.10 fails.
i'm using this on a macbook c2d with parallels.
log files look like this.
main.log:
2007-10-19 15:07:58,593 INFO release-upgrader version '0.81' started
2007-10-19 15:07:59,543 DEBUG lsb-release: 'feisty'
2007-10-19 15:07:59,547 DEBUG _pythonSymlinkCheck run
2007-10-19 15:08:00,606 DEBUG checkViewDepends()
2007-10-19 15:08:00,606 DEBUG getRequiredBack
2007-10-19 15:08:03,028 ERROR IOError in cache.update(): 'Failed to fetch http://
Failed to fetch http://
Failed to fetch cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Release i386 (20070415)
Failed to fetch cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Release i386 (20070415)
'. Retrying (currentRetry: 0)
2007-10-19 15:08:07,769 ERROR IOError in cache.update(): 'Failed to fetch http://
Failed to fetch http://
Failed to fetch http://
Failed to fetch cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Release i386 (20070415)
Failed to fetch cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Release i386 (20070415)
'. Retrying (currentRetry: 1)
2007-10-19 15:08:12,338 ERROR IOError in cache.update(): 'Failed to fetch http://
Failed to fetch http://
Failed to fetch cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Release i386 (20070415)
Failed to fetch cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Release i386 (20070415)
'. Retrying (currentRetry: 2)
2007-10-19 15:08:12,338 ERROR doUpdate() failed complettely
2007-10-19 15:08:14,608 DEBUG marking 'release-
2007-10-19 15:08:14,702 DEBUG marking 'release-
2007-10-19 15:08:15,153 DEBUG pre-requists item: '<pkgAcquire:
2007-10-19 15:08:15,155 ERROR pre-requists item 'http://
apt.log:
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
bzip2: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzip2: Inappropriate ioctl for device
Input file = (stdin), output file = (stdout)
It is possible that the compressed file(s) have become corrupted.
You can use the -tvv option to test integrity of such files.
You can use the `bzip2recover' program to attempt to recover
data from undamaged sections of corrupted files.
main_pre_req.log:
2007-10-19 14:44:05,750 INFO release-upgrader version '0.81' started
2007-10-19 14:44:06,313 DEBUG lsb-release: 'feisty'
2007-10-19 14:44:06,316 DEBUG _pythonSymlinkCheck run
2007-10-19 14:44:07,291 DEBUG checkViewDepends()
2007-10-19 14:44:07,294 DEBUG getRequiredBack
2007-10-19 14:44:35,551 ERROR IOError in cache.update(): 'Failed to fetch http://
Failed to fetch http://
Failed to fetch http://
'. Retrying (currentRetry: 0)
2007-10-19 14:44:44,023 ERROR IOError in cache.update(): 'Failed to fetch http://
Failed to fetch http://
Failed to fetch http://
'. Retrying (currentRetry: 1)
2007-10-19 14:44:48,875 ERROR IOError in cache.update(): 'Failed to fetch http://
Failed to fetch http://
'. Retrying (currentRetry: 2)
2007-10-19 14:44:48,875 ERROR doUpdate() failed complettely
2007-10-19 14:44:53,271 DEBUG marking 'release-
2007-10-19 14:44:53,336 DEBUG marking 'release-
2007-10-19 14:44:55,019 DEBUG pre-requists item: '<pkgAcquire:
2007-10-19 14:44:55,019 DEBUG pre-requists item: '<pkgAcquire:
2007-10-19 14:44:55,022 DEBUG extracting udeb '/tmp/tmppXv00o
2007-10-19 14:44:55,201 DEBUG extracting udeb '/tmp/tmppXv00o
| Oliver Wirjadi (wirjadi) wrote | #1 |
| Oliver Wirjadi (wirjadi) wrote | #2 |
| Brian Murray (brian-murray) wrote | #3 |
| Changed in update-manager: | |
| status: | New → Incomplete |
| Oliver Wirjadi (wirjadi) wrote | #4 |
| Brian Murray (brian-murray) wrote | #5 |
| Changed in update-manager: | |
| status: | Incomplete → Invalid |
I have encountered a (maybe) related problem while upgrading from 7.04 to 7.10, using update-manager: ERROR IOError in cache.update(). Shortly after starting the upgrade dialog, the contents of /etc/apt/
I am attaching the logs (main.log only bacause {apt,term}.log are empty) and the prerequisits. The first URL in prerequists is the one that's being changed. It had initially been set to http://