acroread install issue re man page?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
acroread (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: acroread
Possible dup of #359518
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following packages will be REMOVED:
acroread-
libmozjs0d{u} libxul-common{u} libxul0d{u}
The following packages will be upgraded:
acroread
1 packages upgraded, 0 newly installed, 6 to remove and 0 not upgraded.
Need to get 0B/63.4MB of archives. After unpacking 48.1MB will be used.
Do you want to continue? [Y/n/?] y
Writing extended state information... Done
Preconfiguring packages ...
(Reading database ... 163827 files and directories currently installed.)
Removing acroread-
(Reading database ... 163812 files and directories currently installed.)
Preparing to replace acroread 8.1.3-0medibunt
Unpacking replacement acroread ...
dpkg: error processing /var/cache/
trying to overwrite `/usr/share/
Processing triggers for man-db ...
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:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Purged old files performed fresh install --> success
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: trying to overwrite `/usr/share/
NonfreeKernelMo
Package: acroread 8.1.3-0medibunt
SourcePackage: acroread
Title: package acroread 8.1.3-0medibunt
Uname: Linux 2.6.27-11-generic i686
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 359518, 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 provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.