The users who are still running hardy are almost certainly going to
upgrade to the next LTS release, not to intrepid. The bug is only
present if you upgrade to intrepid.
--
Xscreensaver will not unlock during upgrade
https://bugs.launchpad.net/bugs/256238
You received this bug notification becau
I know I'm commenting on a closed bug here, but comment #2 worries me:
> I'm not sure that, this far into the intrepid support cycle, it's justified
> to make this intrusive of a
> change via SRU for a one-time upgrade bug that most users will have already
> dealt with.
Since 8.04 / Hardy is a
On Thu, Jan 8, 2009 at 2:05 PM, Steve Langasek
wrote:
> To be clear, this doesn't fix the issue when upgrading from hardy to
> intrepid, which is still affected; it only provides the infrastructure
> for handling this case in future upgrades.
Makes sense.
> I'm not sure that, this far into the i
To be clear, this doesn't fix the issue when upgrading from hardy to
intrepid, which is still affected; it only provides the infrastructure
for handling this case in future upgrades.
I'm not sure that, this far into the intrepid support cycle, it's
justified to make this intrusive of a change via
This bug is resolved in the latest Debian version of pam, 1.0.1-5, which
has been merged into jaunty as pam 1.0.1-5ubuntu1. Changelog:
pam (1.0.1-5) unstable; urgency=low
* Build-conflict with libxcrypt-dev, which otherwise pulls libxcrypt in as
a dependency of libpam-modules if it's instal
** Changed in: pam (Ubuntu)
Importance: Undecided => High
Status: New => Confirmed
--
Xscreensaver will not unlock during upgrade
https://bugs.launchpad.net/bugs/256238
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
