package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libperl5.26/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libperl5.26:i386
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
perl (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
O sistema de pacotes está quebrado. Verifique se você está utilizando repositórios de terceiros. Se estiver, desabilite-os, já que normalmente são fonte de problemas. Além disso, execute o seguinte comando em um Terminal: apt-get install -f
I have already tried apt-get install -f and apt --fix-broken install but they did not work.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libperl5.26 5.26.1-6ubuntu0.1
ProcVersionSign
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Wed Jun 13 14:53:15 2018
DpkgTerminalLog:
A preparar para desempacotar .../libperl5.
A descompactar libperl5.26:i386 (5.26.1-6ubuntu0.1) ...
[1mdpkg:[0m erro ao processar o arquivo /var/cache/
a tentar sobreescrever '/usr/share/
ErrorMessage: a tentar sobreescrever '/usr/share/
InstallationDate: Installed on 2018-04-30 (44 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageV
dpkg 1.19.0.5ubuntu2
apt 1.6.1
SourcePackage: perl
Title: package libperl5.26 5.26.1-6ubuntu0.1 failed to install/upgrade: a tentar sobreescrever '/usr/share/
UpgradeStatus: No upgrade log present (probably fresh install)
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.