Just a quick note to say that the LDB build failure isn't a regression
- whatever is going on here has always been going on, it just wasn't
tested before ldb 1.1.23.
The commit adding the tests is:
commit 0d36d6d84271f97df82a1f0c9c6c6412833575be
Author: Petr Viktorin <pvikt...@redhat.com>
Date: Fri Aug 21 10:22:22 2015 +0200
pyldb: Improve test coverage
Add tests for:
- ldb.Dn.{get,set}_{extended_,}component_{name,value}
- ldb.Dn.{get,set}_rdn_{name,value}
- ldb.Dn.get_casefold
- ldb.Dn.get_linearized
- ldb.Dn.canonical_str
Add negative test for Dn.__contains__
Add a helper function to register a dummy DN extension for testing.
Signed-off-by: Petr Viktorin <pvikt...@redhat.com>
Reviewed-by: Andrew Bartlett <abart...@samba.org>
Reviewed-by: Stefan Metzmacher <me...@samba.org>
That said, fixing this is going to require gdb on a s390. Is the
porterbox where that should be done?
https://db.debian.org/machines.cgi?host=zelenka
How do I get on such a machine?
Andrew Bartlett
