| Summary: | stable x11-apps/xdm-1.1.4 still installs /etc/pam.d/xdm incuding pam_stack.so | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Carsten Lohrke (RETIRED) <carlo> |
| Component: | New packages | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | CC: | flameeyes, Werner.Peter |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Carsten Lohrke (RETIRED)
2007-10-25 12:48:43 UTC
Err no, it doesn't. It did, but it doesn't. The old xdm ebuilds used to install pam_stack.so-based pamd files, but now installs a proper pamd file. It depends on when you installed. I just reinstalled 1.1.4 before I filed the bug and synced the tree this morning... Hm - .../image/etc/pam.d/xdm gets written correctly, but apparently not merged, while Portage claims to do so. Weird. Same problem with dev-libs/cyrus-sasl. Anyone having an idea? Portage bug!? *** Bug 197026 has been marked as a duplicate of this bug. *** (In reply to comment #3) > Hm - .../image/etc/pam.d/xdm gets written correctly, but apparently not merged, > while Portage claims to do so. Weird. Same problem with dev-libs/cyrus-sasl. > Anyone having an idea? Portage bug!? Maybe if you could post some emerge output... |