tieto team mailing list archive

[Bolesław Tokarski <731879@xxxxxxxxxxxxxxxxxx>]

Hello,

I have just verified that the libpam-ldap version in Precise
(184-8.5ubuntu2) has the same issue.

I have a custom package that configures ldap (actually it configures much more than that) and I tried to add:
Provides: ldap-auth-config
to it, but because libpam-ldap Depends: ldap-auth-config (>= 0.5.2) - it ignores virtual packages, and pulls ldap-auth-config which in turn pulls ldap-auth-client.

If you do not want to just remove the dependency, perhaps you could add
depend on a virtual package name by default and I could use that one
instead?

I just verified against Debian testing (Wheezy) and their libpam-ldap
184-8.5 does not have this dependency at all. Why is it in Ubuntu?

Best regards,
Boleslaw Tokarski

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

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

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

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"?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpam-ldap/+bug/731879/+subscriptions