[Bug 790538] Re: pam update causes cron to stop working with "Module is unknown" error

[Vijay Krishna Ramesh]

Colin, that seems like a horrible solution - you now have everybody's
apt claiming they need to get a package that 404s, causing apt-get
upgrade to fail.  I understand a buggy package was released, but once
that has been done, you can't just remove the package itself (while
leaving reference to it as "here's the latest version of libpam")...

if a fixed version isn't quickly on the way, if nothing else you should
release 1.1.1-2ubuntu2 as 1.1.1-2ubuntu5.3 or whatever, so that people
who have already installed 1.1.1-2ubuntu5.2 can upgrade to a working
version, and people with 1.1.1-2ubuntu2 aren't prompted to install
1.1.1-2ubuntu5.2 that doesn't exist...

i'll add the caveat that i'm not intimately familiar with the release
process for ubuntu, but it seems that once a release is publicly
accessible, you can't just rollback - you have to move forward to keep
in line with every possible "path" (in this case, people who already
installed the buggy 1.1.1-2ubuntu5.2 and people with 1.1.1-2ubuntu2 who
are now being prompted to upgrade to 1.1.1-2ubuntu5.2).

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/790538

Title:
  pam update causes cron to stop working with "Module is unknown" error

Status in “pam” package in Ubuntu:
  Confirmed

Bug description:
  Upgrading libpam-modules from 1.1.1-4ubuntu1 to 1.1.1-4ubuntu2.2, cron stopped working, just gives a log message "Module is unknown". This happened during unattended-upgrades this night, so there might be a lot of people who didn't realize that yet.
  Downgrading to 1.1.1-4ubuntu1 fixes this.
  Ubuntu 10.10 amd64, almost vanilla, fresh, minimum install + java (ppa) + postgresql9 (ppa).