Ubuntu
libanyevent-perl package

package libanyevent-perl (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man3/AnyEvent.3pm.gz', which is also in package anyevent-perl 0:1.02-0.2

Bug #519152 reported by Brian Murray on 2010-02-09

This bug report is a duplicate of: Bug #470560: package libanyevent-perl (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man3/AnyEvent.3pm.gz', which is also in package anyevent-perl 0:1.02-0.2. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	libanyevent-perl (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: libanyevent-perl

This happened during a dist-upgrade from Karmic to Lucid.

ProblemType: Package
Architecture: amd64
Date: Mon Feb 8 16:04:26 2010
DistroRelease: Ubuntu 10.04
ErrorMessage: trying to overwrite '/usr/share/man/man3/AnyEvent.3pm.gz', which is also in package anyevent-perl 0:1.02-0.2
NonfreeKernelModules: fglrx
Package: libanyevent-perl (not installed)
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
SourcePackage: libanyevent-perl
Title: package libanyevent-perl (not installed) failed to install/upgrade: trying to overwrite '/usr/share/man/man3/AnyEvent.3pm.gz', which is also in package anyevent-perl 0:1.02-0.2
Uname: Linux 2.6.32-12-generic x86_64

Tags:

Revision history for this message

Brian Murray (brian-murray) wrote on 2010-02-09:

AptOrdering.txt Edit (43.7 KiB, text/plain; charset="utf-8")
Df.txt Edit (738 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (185.0 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.gz Edit (71.6 KiB, application/x-gzip)

Revision history for this message

Ansgar Burchardt (aburch) wrote on 2010-02-09:

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