As a workaround, a user hitting this issue can run:
sudo rm -f /usr/share/man/man8/pam_exec.8.gz
/usr/share/man/man8/pam_unix.8.gz && sudo apt-get -f install
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pam (Ubuntu Wily)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
I've fixed the issue in Precise using bug #1558597 to track it.
** Changed in: pam (Ubuntu Precise)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
According to bug #1558597, the precise version is still buggy.
** Changed in: pam (Ubuntu Precise)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
Confirmed; this seems to be a regression in multiarch compatibility
introduced by this latest security update. This needs to be addressed
by including the manpage in the cve diff, along with the changes to
modules/pam_unix/pam_unix.8.xml, so that the file is not regenerated
(differently) at build
This bug was fixed in the package pam - 1.1.8-3.1ubuntu3.2
---
pam (1.1.8-3.1ubuntu3.2) wily-security; urgency=medium
* SECURITY REGRESSION: multiarch update issue (LP: #1558114)
- debian/patches-applied/cve-2015-3238.patch: removed manpage changes
so they don't get
This bug was fixed in the package pam - 1.1.8-1ubuntu2.2
---
pam (1.1.8-1ubuntu2.2) trusty-security; urgency=medium
* SECURITY REGRESSION: multiarch update issue (LP: #1558114)
- debian/patches-applied/cve-2015-3238.patch: removed manpage changes
so they don't get
/usr/share/man/man8/pam_exec.8.gz is also affected.
** Also affects: pam (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: pam (Ubuntu Trusty)
Status: New => Triaged
** Changed in: pam (Ubuntu Wily)
Status: Confirmed => Triaged
** Changed in: pam (Ubuntu
** Also affects: pam (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: pam (Ubuntu Xenial)
Importance: Critical
Assignee: Marc Deslauriers (mdeslaur)
Status: Triaged
** Changed in: pam (Ubuntu Precise)
Status: New => Triaged
** Changed in: pam
This bug was fixed in the package pam - 1.1.3-7ubuntu2.2
---
pam (1.1.3-7ubuntu2.2) precise-security; urgency=medium
* SECURITY REGRESSION: multiarch update issue (LP: #1558114)
- debian/patches-applied/cve-2015-3238.patch: removed manpage changes
so they don't get
The following packages have unmet dependencies:
libpam-modules : Recommends: update-motd but it is not installed
Breaks: libpam-modules:i386 (!= 1.1.8-3.1ubuntu3.1) but
1.1.8-3.1ubuntu3 is installed
libpam-modules:i386 : PreDepends: libpam-modules-bin:i386 (= 1.1.8-3.1ubuntu3)
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1558114
Title:
package libpam-modules 1.1.8-3.1ubuntu3.1 failed to install/upgrade:
This bug was fixed in the package pam - 1.1.8-3.2ubuntu2
---
pam (1.1.8-3.2ubuntu2) xenial; urgency=medium
* debian/patches-applied/cve-2015-3238.patch: removed manpage changes
so they don't get regenerated during build and cause a multiarch
installation issue. (LP:
13 matches
Mail list logo
