On Wed, 2012-01-18 at 13:42 +0000, Adam D. Barratt wrote: > If the two further changes included in the debdiff from > <[email protected]> are resovled in unstable (if > appropriate) then I'd be happy to look at including those in a stable > update. I have to admit that, like Julien, I would prefer an update > that only includes the changes relevant to the bug fixes; I appreciate > this means a little more maintenance burden when you're dealing with a > native package.
To be clear, there are three changes up for consideration:
(1) is #645599 which is essentially:
http://arthurdejong.org/viewvc/nss-pam-ldapd/nss-pam-ldapd-0.7/debian/libnss-ldapd.config?r1=1209&r2=1555
(2) is a problem with not-initialised variables which is:
http://arthurdejong.org/viewvc/nss-pam-ldapd/nss-pam-ldapd-0.7/nslcd/nslcd.c?r1=1209&r2=1559
(3) is a typo in error handling code:
http://arthurdejong.org/viewvc/nss-pam-ldapd/nss-pam-ldapd-0.7/nslcd/myldap.c?r1=1469&r2=1561
All three fixes were also made in 0.8.5 that are in both unstable and
testing (though the fix for (1) in 0.8.5 was a little more intrusive:
http://arthurdejong.org/viewvc/nss-pam-ldapd/nss-pam-ldapd/debian/libnss-ldapd.config?r1=1543&r2=1597
I also have a few more fixes that I would also like to fix in a 0.7
version. One of which is the range checking stuff in my second mail to
the bug report and a few more that are contributed by Jakub Hrozek of
Redhat (those patches are used at Redhat). Some of these changes are
more intrusive. Not all of these are in a released 0.8 version yet.
Which of the above fixes are OK for a stable update?
This leaves the question of what version number to use. I could upload a
0.7.16 which would also include updates to the version number in the
code and manual pages (like in the previous debdiffs) or a
0.7.15+squeeze1 version (which would only also change debian/changelog).
Thanks for considering and thanks for reviewing this stuff,
--
-- arthur - [email protected] - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
