tieto team mailing list archive

[Bolesław Tokarski <731879@xxxxxxxxxxxxxxxxxx>]

I am using lucid at the moment, libpam-ldap version 184-8.2ubuntu1.
Anyway, if you look at maverick and natty you will see that the package
is the exact same version, with the same dependencies.

** Changed in: libpam-ldap (Ubuntu)
       Status: Incomplete => New

-- 
You received this bug notification because you are a member of Tieto,
which is a direct subscriber.
https://bugs.launchpad.net/bugs/731879

Title:
  libpam-ldap depends on ldap-auth-client

Status in “libpam-ldap” package in Ubuntu:
  New

Bug description:
  Binary package hint: libpam-ldap

  Installation of libpam-ldap adds loads of trash to the system.

  Dependency on ldap-auth-config pulls also ldap-auth-client. As I can
  see ldap-auth-config is used for configuration of PAM in some old-way
  (it overwrites /etc/pam.d/common-*) and not actually using the libpam-
  runtime's pam-auth-update to manage pam.d files.

  Meanwhile libpam-ldap also depends on libpam-runtime! So in one
  package we depend on the old and the new config way, while in fact the
  postinstall script uses the new one and the user would have to run the
  old one manually. Why do this at all? And why "depend" on ldap-auth-
  client. Perhaps if somebody was interested in this, it could be
  "Suggested"?