| 2009-02-12 23:34:34 |
Brian Murray |
bug |
|
|
added bug |
| 2009-02-22 14:35:11 |
Dave Gilbert |
update-manager: status |
New |
Confirmed |
|
| 2009-02-22 14:35:11 |
Dave Gilbert |
update-manager: statusexplanation |
|
The fact there are so many reports of corrupt archives makes me think this request is sensible; I'm guessing most of them are bad hardware?
|
|
| 2010-08-05 22:25:39 |
Jean-Baptiste Lallement |
description |
Binary package hint: update-manager
In the event that update-manager runs into a corrupted package like so:
dpkg: error processing /var/cache/apt/archives/xulrunner-1.9_1.9.0.5+nobinonly-0ubuntu0.8.10.1_i386.deb (--unpack):
corrupted filesystem tarfile - corrupted package archive
or possibly
dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error processing /var/cache/apt/archives/linux-image-2.6.27-7-generic_2.6.27-7.16_amd64.deb (--unpack):
subprocess dpkg-deb --fsys-tarfile returned error exit status 2
I think it would be a better idea if update-manager were to delete the deb from the cache and try downloading it again. |
Binary package hint: update-manager
In the event that update-manager runs into a corrupted package like so:
dpkg: error processing /var/cache/apt/archives/xulrunner-1.9_1.9.0.5+nobinonly-0ubuntu0.8.10.1_i386.deb (--unpack):
corrupted filesystem tarfile - corrupted package archive
or possibly
dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error processing /var/cache/apt/archives/linux-image-2.6.27-7-generic_2.6.27-7.16_amd64.deb (--unpack):
subprocess dpkg-deb --fsys-tarfile returned error exit status 2
I think it would be a better idea if update-manager were to delete the deb from the cache and try downloading it again.
== workaround ==
Please execute the following commands, as it will clear your package cache, in a terminal ( Applications -> Accessories -> Terminal ) :
sudo apt-get clean
sudo apt-get update
Then try performing the update again. This will likely resolve your issue. |
|
| 2010-08-05 22:25:54 |
Jean-Baptiste Lallement |
summary |
update-manager should deal with corrupted debs better |
[MASTER] update-manager should deal with corrupted debs better |
|
| 2010-08-05 22:26:44 |
Jean-Baptiste Lallement |
description |
Binary package hint: update-manager
In the event that update-manager runs into a corrupted package like so:
dpkg: error processing /var/cache/apt/archives/xulrunner-1.9_1.9.0.5+nobinonly-0ubuntu0.8.10.1_i386.deb (--unpack):
corrupted filesystem tarfile - corrupted package archive
or possibly
dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error processing /var/cache/apt/archives/linux-image-2.6.27-7-generic_2.6.27-7.16_amd64.deb (--unpack):
subprocess dpkg-deb --fsys-tarfile returned error exit status 2
I think it would be a better idea if update-manager were to delete the deb from the cache and try downloading it again.
== workaround ==
Please execute the following commands, as it will clear your package cache, in a terminal ( Applications -> Accessories -> Terminal ) :
sudo apt-get clean
sudo apt-get update
Then try performing the update again. This will likely resolve your issue. |
Binary package hint: update-manager
In the event that update-manager runs into a corrupted package like so:
dpkg: error processing /var/cache/apt/archives/xulrunner-1.9_1.9.0.5+nobinonly-0ubuntu0.8.10.1_i386.deb (--unpack):
corrupted filesystem tarfile - corrupted package archive
or possibly
dpkg-deb: subprocess paste killed by signal (Broken pipe)
dpkg: error processing /var/cache/apt/archives/linux-image-2.6.27-7-generic_2.6.27-7.16_amd64.deb (--unpack):
subprocess dpkg-deb --fsys-tarfile returned error exit status 2
or
dpkg-deb: `/var/cache/apt/archives/libswscale0_4%3a0.5+svn20090706-2ubuntu2_i386.deb' is not a debian format archive
I think it would be a better idea if update-manager were to delete the deb from the cache and try downloading it again.
== workaround ==
Please execute the following commands, as it will clear your package cache, in a terminal ( Applications -> Accessories -> Terminal ) :
sudo apt-get clean
sudo apt-get update
Then try performing the update again. This will likely resolve your issue.
|
|
| 2010-08-06 13:17:24 |
Jean-Baptiste Lallement |
bug task added |
|
apt (Ubuntu) |
|
| 2010-08-23 01:08:21 |
Micah Gersten |
bug |
|
|
added subscriber Micah Gersten |
| 2010-09-12 06:15:17 |
Micah Gersten |
update-manager (Ubuntu): importance |
Undecided |
Medium |
|
| 2010-09-12 06:15:17 |
Micah Gersten |
update-manager (Ubuntu): status |
Confirmed |
Triaged |
|
| 2011-08-18 15:31:11 |
Launchpad Janitor |
apt (Ubuntu): status |
New |
Confirmed |
|
| 2011-08-18 15:31:26 |
Christopher Forster |
bug |
|
|
added subscriber Christopher Forster |
| 2020-07-16 16:53:56 |
Kai Kasurinen |
bug |
|
|
added subscriber Kai Kasurinen |
