Control: tags -1 moreinfo unreproducible Control: severity -1 normal Hi!
On Thu, 2015-03-26 at 21:32:41 +0100, Alberto Salvia Novella wrote: > Package: dpkg > Version: 1.17.13 > Severity: important > As reported in > <https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1407757>: Ah, one of those bug reports in the dpkg's Launchpad page that makes it look like a wasteland. :) > 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. I think this and the ton of duped bugs in Launchpad are just a symptom of a buggy frontend asking dpkg to install packages multiple times, which then dpkg complains about. > 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) 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. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
