Your message dated Fri, 27 Mar 2015 19:52:55 +0100
with message-id <[email protected]>
and subject line Re: Bug#781278: multi-arch packages cannot be installed due to
dpkg wrongly detecting them as already installed
has caused the Debian Bug report #781278,
regarding multi-arch packages cannot be installed due to dpkg wrongly detecting
them as already installed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
781278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781278
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.17.13
Severity: important
As reported in
<https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1407757>:
HOW TO REPRODUCE:
- Install an affected package.
EXPECTED BEHAVIOUR:
- The package to be installed.
REAL BEHAVIOUR:
- The package cannot be installed due to dpkg wrongly detecting them as
already installed.
ProblemType: Package
DistroRelease: Ubuntu 14.04
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
AptdaemonVersion: 1.1.1-1ubuntu5.1
Architecture: amd64
CrashReports:
640:0:0:1458151:2015-01-05 12:18:11.086621522 -0600:2015-01-05
12:18:12.086621522 -0600:/var/crash/libnss3:amd64.0.crash
600:0:0:217380:2015-01-05 12:17:09.359944581 -0600:2015-01-05
12:17:10.359944581 -0600:/var/crash/libpam-systemd:amd64.0.crash
644:0:0:0:2015-01-05 12:18:13.122599379 -0600:2015-01-05
12:18:13.122599379 -0600:/var/crash/libnss3:amd64.0.upload
600:0:0:217372:2015-01-05 12:17:10.375944347 -0600:2015-01-05
12:17:10.363944604 -0600:/var/crash/libnss3-nssdb.0.crash
Date: Mon Jan 5 12:17:10 2015
DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.9:package
libpam-systemd:amd64 is already installed and configured
ErrorMessage: package libpam-systemd:amd64 is already installed and
configured
InstallationDate: Installed on 2015-01-04 (1 days ago)
InstallationMedia: Mythbuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
SourcePackage: dpkg
Title: package libpam-systemd:amd64 204-5ubuntu20.9 failed to
install/upgrade: package libpam-systemd:amd64 is already installed and
configured
UpgradeStatus: No upgrade log present (probably fresh install)
smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
--- Begin Message ---
On Fri, 2015-03-27 at 18:57:18 +0100, Alberto Salvia Novella wrote:
> Guillem Jover:
> >I'm assuming that the package is actually properly configured on the
> >system, and the problem comes from whatever frontend is being used in
> >Ubuntu.
> >
> >Doing a «dpkg -l libpam-systemd:amd64» should confirm my suspicion.
>
> This is what happens when running that command.
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name Version Architecture Description
> +++-====================-==============-============-=======================================
> ii libpam-systemd:amd64 208-8ubuntu8.2 amd64 system and service
> manager - PAM module
> What does it tell you?
Assuming that this was run on the same system that got the reported
error, it means that the packages is fully installed and configured,
and that dpkg was right. The problem is that whatever is performing
the upgrade/installation is incorrectly telling dpkg to --configure
a packages that is already configured.
That could be unattended-upgrades (?) or libapt or something else I
don't know what's going on in Ubuntu regarding upgrades.
In any case closing with this mail and you should probably reassign
all those tons of dupes in the dpkg Launchpad to somewhere else, as
they are quite misleading and personally I stopped taking a peek at
it as it's now pretty much unusable.
Thanks,
Guillem
--- End Message ---
