failure to remove/upgrade memtest86+
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| memtest86+ (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: memtest86+
Just finished a fresh install of Gutsy on to a FakeRaid array. Booted up and tried updating via update-manager and I get the following about memtest86+
(Reading database ... 106979 files and directories currently installed.)
Preparing to replace memtest86+ 1.70-2ubuntu1 (using .../memtest86+
Unpacking replacement memtest86+ ...
[: 25: ==: unexpected operator
exec: 25: -a: not found
dpkg: warning - old post-removal script returned error exit status 2
dpkg - trying script from the new package instead ...
[: 25: ==: unexpected operator
exec: 25: -a: not found
dpkg: error processing /var/cache/
subprocess new post-removal script returned error exit status 2
[: 25: ==: unexpected operator
exec: 25: -a: not found
dpkg: error while cleaning up:
subprocess post-removal script returned error exit status 2
Errors were encountered while processing:
/var/cache/
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
ProblemType: Package
Architecture: amd64
Date: Tue Aug 14 00:19:49 2007
Dependencies:
DistroRelease: Ubuntu 7.10
ErrorMessage: subprocess new post-removal script returned error exit status 2
NonfreeKernelMo
Package: memtest86+ 1.70-2ubuntu1
PackageArchitec
SourcePackage: memtest86+
Title: package memtest86+ 1.70-2ubuntu1 failed to install/upgrade: subprocess new post-removal script returned error exit status 2
Uname: Linux ma10quad 2.6.22-8-generic #1 SMP Thu Jul 12 16:09:47 GMT 2007 x86_64 GNU/Linux
| ma10 (ma10-wong) wrote | #1 |
| Reinhard Tartler (siretart) wrote | #2 |
| ma10 (ma10-wong) wrote | #3 |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 129614 , so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can add, or to see if there is a workaround for the bug. Feel free to continue to report any other bugs you may find.