Ubuntu
barry package

package libbarry0 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libbarry0/README', which is also in package linberry 1.0a3b

Bug #844679 reported by Jony on 2011-09-08

This bug report is a duplicate of: Bug #835658: package libbarry0 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libbarry0/README', which is also in package linberry 1.0a3b. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	barry (Ubuntu)	New	Undecided	Unassigned

Bug Description

I cannot install libbarry0.

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: libbarry0 (not installed)
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
Architecture: i386
Date: Thu Sep 8 16:41:38 2011
DpkgTerminalLog:
Unpacking libbarry0 (from .../libbarry0_0.15-1ubuntu3_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/libbarry0_0.15-1ubuntu3_i386.deb (--unpack):
trying to overwrite '/usr/share/doc/libbarry0/README', which is also in package linberry 1.0a3b
ErrorMessage: trying to overwrite '/usr/share/doc/libbarry0/README', which is also in package linberry 1.0a3b
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: barry
Title: package libbarry0 (not installed) failed to install/upgrade: trying to overwrite '/usr/share/doc/libbarry0/README', which is also in package linberry 1.0a3b
UpgradeStatus: Upgraded to natty on 2011-07-18 (51 days ago)

Tags:

Revision history for this message

Jony (mjonyh) wrote on 2011-09-08:

AptOrdering.txt Edit (229 bytes, text/plain; charset="utf-8")
Df.txt Edit (443 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (42.0 KiB, text/plain; charset="utf-8")

Revision history for this message

papukaija (papukaija) wrote on 2012-06-10:

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 835658, 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.