ldapscripts in hardy tries to read /etc/pam_ldap.conf

[Arnd]

Invoking one of the ldap scripts in hardy heron does not work:

/usr/bin/ldapaddusertogroup hannemann um-webadmin
egrep: /etc/pam_ldap.conf: No such file or directory
egrep: /etc/pam_ldap.conf: No such file or directory

This is probably because
libpam-ldap was changed to use /etc/ldap/ldap.conf as its config file.

Solution:
/usr/share/ldapscripts/runtime.debian
should be changed in a way to parse /etc/ldap/ldap.conf instead.

[Benjamin Drung (bdrung)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in ldapscripts.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

[KarlGoetz (kgoetz)]

I can confirm this bug under 8.04.1

[KarlGoetz (kgoetz)]

This debdiff should close the bug, but the 'only problem' is that its so trivial i expect it wont be accepted.

Still, we can hope.

[James Westby (james-w)]

Hi Karl,

If you would like to get this bug fixed for Hardy then you need
to follow

  https://wiki.ubuntu.com/StableReleaseUpdates

I would upload the fix to Intrepid, but Intrepid now has 1.8,
and I don't see how the patch would apply there, as that
file no longer exists, and there is no mention of pam_ldap
in the package. This may mean that the bug is fixed,
but I'm not sure how to verify.

I'm un-subscribing the sponsors, please re-subscribe when
there is something to sponsor. I will remain subscribed if
you have any questions.

Thanks,

James

[KarlGoetz (kgoetz)]

> If you would like to get this bug fixed for Hardy then you need
> to follow
>
> https://wiki.ubuntu.com/StableReleaseUpdates

Thanks, I'll look at it now.

>
> I would upload the fix to Intrepid, but Intrepid now has 1.8,
> and I don't see how the patch would apply there, as that
> file no longer exists, and there is no mention of pam_ldap
> in the package. This may mean that the bug is fixed,
> but I'm not sure how to verify.

I grabbed the intrepid source as well, and couldnt find anything to
patch, so I'm hoping its 'ok'.

>
> I'm un-subscribing the sponsors, please re-subscribe when
> there is something to sponsor. I will remain subscribed if
> you have any questions.

Cheers.

>
> Thanks,
>
> James

[KarlGoetz (kgoetz)]

James, what other information would be required from this?

* Seems to fit ok with "When" (safe patch+affects application)

* Procedure has a few more options
Procedure:
1. Fixed in current release

2.1. A statement explaining the impact of the bug on users and justification for backporting the fix to the stable release
* Parts of ldapscripts are unusable without it.
* Its not a backported patch - its new
* It doesn't affect other packages

2.2. An explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix.
* I'm not sure - its a new version, and the file(s) involved don't seem to exist any more.

2.3. A minimal patch applicable to the stable version of the package. If preparing a patch is likely to be time-consuming, it may be preferable to get a general approval from the SRU team first.
* I think its minimal. Is there a specific change it requires?

2.4. Detailed instructions how to reproduce the bug. These should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. Please mark this with a line "TEST CASE:".
* How detailed? Hopefully not a guide to installing the LDAP server as well...
* Have a working openldap server
* Have a working pam-ldap
* sudo apt-get install ldapscripts
* sudo ldapadduser user
Output is:
egrep: /etc/pam_ldap.conf: No such file or directory
egrep: /etc/pam_ldap.conf: No such file or directory

2.5. A discussion of the regression potential of the patch and how users could get inadvertently effected.
* Its currently unusable - I'm not sure how it can regress.

Steps 3/4/5: Not sure how i test/perform these.

[KarlGoetz (kgoetz)]

And i forgot to say - I've built it successfully (in case that's relevant)