package libapt-inst1.4 0.8.16~exp12ubuntu10.2 [modified: usr/share/locale/ar/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/ast/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/bg/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/bs/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/ca/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/cs/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/cy/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/da/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/de/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/dz/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/el/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/es/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/eu/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/fi/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/fr/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/gl/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/hu/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/it/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/ja/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/km/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/ko/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/ku/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/lt/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/mr/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/nb/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/ne/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/nl/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/nn/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/pl/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/pt/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/pt_BR/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/ro/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/ru/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/sk/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/sl/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/sv/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/th/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/tl/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/uk/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/vi/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/zh_CN/LC_MESSAGES/libapt-inst1.4.mo usr/share/locale/zh_TW/LC_MESSAGES/libapt-inst1.4.mo] failed to install/upgrade: './usr/share/locale/pt_BR/LC_MESSAGES/libapt-inst1.4.mo' is different from the same file on the system
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I was trying to recover my apt-install system by following the instructions on this website:
http://
The update process was broken due to another bug I have already reported on this site (at least 6 other people affected - sorry I can't find it now, I don't have the url to hand). The original problem seemed to come from an internal error generated by apt-get trying to update itself during a routine upgrade. I do not have all the error message to hand, but this one was on the end of one of the traces:
E: Internal Error, No file name for libapt-pkg4.12
The original problem appeared to be due to a mis-match between 32-bit and 64-bit versions of the library.
Now I am really screwed, and IDK how to recover normal update/upgrade operations.
ProblemType: Package
DistroRelease: Ubuntu 12.04
ProcVersionSign
Uname: Linux 3.2.0-31-generic x86_64
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu13
AptOrdering:
libapt-inst1.4: Install
libapt-pkg4.12: Install
libapt-inst1.4: Configure
libapt-pkg4.12: Configure
libapt-inst1.4: Configure
Architecture: amd64
Date: Fri Sep 28 09:53:47 2012
DpkgTerminalLog:
Preparing to replace libapt-inst1.4 0.8.16~
Unpacking replacement libapt-inst1.4 ...
dpkg: error processing /var/cache/
'./usr/
DuplicateSignature:
Unpacking replacement libapt-inst1.4 ...
dpkg: error processing /var/cache/
'./usr/
ErrorMessage: './usr/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Found the original bug: /bugs.launchpad .net/ubuntu/ +source/ apt/+bug/ 1039685
https:/
This bug may be a duplicate, but it is possible that it is a secondary issue arising from the first one.