Comment 6 for bug 256091

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.