Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the
report. The bug has been fixed in newer releases of Ubuntu.
** Changed in: pam (Ubuntu Intrepid)
Status: Confirmed => Invalid
--
pam-auth-update fails to enable Default: yes profiles
https://bugs.launchpad.net/bugs/29
** Branch linked: lp:ubuntu/karmic/pam
--
pam-auth-update fails to enable Default: yes profiles
https://bugs.launchpad.net/bugs/294513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
Not sure why, but this bug didn't get closed even though the fix has
been uploaded. Changelog is:
pam (1.0.1-5ubuntu1) jaunty; urgency=low
* Merge from Debian unstable
* Remaining changes:
- debian/libpam-modules.postinst: Add PATH to /etc/environment if it's not
present there or i
** Changed in: pam (Ubuntu Intrepid)
Importance: Undecided => Medium
Status: New => Confirmed
--
pam-auth-update fails to enable Default: yes profiles
https://bugs.launchpad.net/bugs/294513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
It will definitely be fixed in jaunty; I'm not sure yet whether I'll
push this as a change for intrepid-updates, because while I'm sure that
it fixes a bug, I'm less confident that it won't reduce any other
regressions in the process. So I'm going to let it cook in jaunty for a
bit first to get it
Excellent, thanks. I don't know much about the Ubuntu release and
update process; does a fix like this eventually appear in the apt
repositories under intrepid-updates or otherwise become available to
intrepid machines, or will it only be fixed in jaunty?
I've never used bzr, but I checked out (n
Thanks for the patches, Greg. I've applied the first to the bzr tree,
and am having a look at the second one now.
Seeing that you're using git-formatted patches, I feel compelled to
mention that there's a bzr branch specifically for the pam-auth-update
work, available at bzr.debian.org/bzr/pkg-pa
As a separate issue that hasn't bitten me but that I saw while editing
the code, if some profiles were previously selected but all of them have
now disappeared then we should presumably enter the same "use all the
defaults" fallback that we do if no profiles were selected. The present
version does
** Attachment added: "treat absent /var/lib/pam/seen as empty"
http://launchpadlibrarian.net/19413934/0001-handle-no-var-lib-pam-seen-like-empty.patch
--
pam-auth-update fails to enable Default: yes profiles
https://bugs.launchpad.net/bugs/294513
You received this bug notification because yo
