package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz' as a fix for failed installation of irssi , which is different from other instances of package libperl5.22:i386
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
perl (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Installation that triggered problem was installation of irssi on HP Probook 450G1.
lsb_release -a
LSB Version: core-9.
Distributor ID: Ubuntu
Description: Ubuntu 16.10
Release: 16.10
Codename: yakkety
uname -a
Linux curiosity 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
apt-cache policy irssi
irssi:
Installed: 0.8.19-1ubuntu2
Candidate: 0.8.19-1ubuntu2
Version table:
*** 0.8.19-1ubuntu2 500
500 http://
100 /var/lib/
apt-cache policy
libperl5.22:
Installed: 5.22.2-3
Candidate: 5.22.2-3
Version table:
*** 5.22.2-3 500
500 http://
100 /var/lib/
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: libperl5.22 5.22.2-3
ProcVersionSign
Uname: Linux 4.8.0-34-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Tue Jan 24 16:29:34 2017
DuplicateSignature:
package:
Unpacking libperl5.22:i386 (5.22.2-3) ...
dpkg: error processing archive /tmp/apt-
trying to overwrite shared '/usr/share/
ErrorMessage: trying to overwrite shared '/usr/share/
InstallationDate: Installed on 2016-12-06 (49 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
RelatedPackageV
dpkg 1.18.10ubuntu1
apt 1.3.3
SourcePackage: perl
Title: package libperl5.22 5.22.2-3 failed to install/upgrade: trying to overwrite shared '/usr/share/
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
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 1574351, 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.