In my use case, I need to override the pam config of another package.
It would be useful to instead of just saying "conflicts" saying
"replaces", and then not having it warn.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
On Mon, Mar 26, 2012 at 09:40:47PM -, Ray Link wrote:
> Then why does pam-auth-update deactivate only the lower priority module
> when a Conflict: is found?
Because in a corner case when using the noninteractive frontend,
deactivating both could mean there are no modules enabled, resulting in
Then why does pam-auth-update deactivate only the lower priority module
when a Conflict: is found?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965662
Title:
pam-auth-update conflict resolution sho
On Mon, Mar 26, 2012 at 08:59:44PM -, Jeffrey Hutzelman wrote:
> As documented, the resolution mechanism compares priorities on the
> affected modules to determine which one to use in case of a conflict.
> That's what guarantees the result is what you want, or at least what the
> package mainta
"need" is an awfully strong word.
As documented, the resolution mechanism compares priorities on the
affected modules to determine which one to use in case of a conflict.
That's what guarantees the result is what you want, or at least what the
package maintainers wanted the default behavior to be
This is entirely by design. The pop-up is informing the user that there
was a conflict and that *they need to review the list of selected
modules*, because there's nothing about the resolution mechanism that
guarantees the result is what you want.
The only reason the resolution mechanism exists a
