package libpam-modules 1.1.1-4ubuntu2.3 failed to install/upgrade: ErrorMessage: il pacchetto libpam-modules è già installato e configurato
Bug #803079 reported by
Matteo Piacentini
This bug report is a duplicate of:
Bug #541595: [Master] package failed to install/upgrade: package is already installed and configured.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
I don't know what else to say
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: libpam-modules 1.1.1-4ubuntu2.3
ProcVersionSign
Uname: Linux 2.6.35-30-generic i686
Architecture: i386
Date: Tue Jun 28 14:46:46 2011
ErrorMessage: ErrorMessage: il pacchetto libpam-modules è già installato e configurato
InstallationMedia: Mythbuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: pam
Title: package libpam-modules 1.1.1-4ubuntu2.3 failed to install/upgrade: ErrorMessage: il pacchetto libpam-modules è già installato e configurato
UpgradeStatus: Upgraded to natty on 2011-06-28 (0 days ago)
tags: | added: dist-upgrade |
To post a comment you must log in.
The error in the log file is:
Preparativi per sostituire libpam-modules v.1.1.1-4ubuntu2.3 (utilizzando .../libpam- modules_ 1.1.2-2ubuntu8. 3_i386. deb)... apt/archives/ libpam- modules_ 1.1.2-2ubuntu8. 3_i386. deb (--unpack): apt/archives/ libpam- modules_ 1.1.2-2ubuntu8. 3_i386. deb
dpkg: errore nell'elaborare /var/cache/
il sottoprocesso nuovo script pre-installation ha restituito lo stato di errore 1
Segnalazione apport non scritta poiché è stato raggiunto il valore massimo di MaxReports
Si sono verificati degli errori nell'elaborazione:
/var/cache/
dpkg: errore nell'elaborare libpam-modules (--configure):
il pacchetto libpam-modules è già installato e configurato
When the preinst fails as part of the upgrade, my understanding is that there's no reason to run --configure again on the package because it will not have been deconfigured yet. Reassigning this bug to update-manager, to avoid calling dpkg --configure and triggering this error.
(I don't think there's any bug here in libpam-modules itself. The preinst script itself is quite short, and should only have failed due to an issue with the availability of debconf, or with someone manually killing the debconf frontend.)