Quoting http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596935
As of backupninja 0.9.10, the LDAP handler is not shipped anymore.
** Bug watch added: Debian Bug tracker #596935
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596935
--
You received this bug notification because you are a
Backup Ninja doesn't ship that particular backend any more (see comment
#4).
** Changed in: backupninja (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/289957
This issue is tracked at https://labs.riseup.net/code/issues/2767
** Changed in: backupninja (Ubuntu)
Importance: Undecided = Low
** Changed in: backupninja (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
From reading the source, I found a workaround that permits taking
backups without changing the source code:
The LDAP configuration file should read as:
databases = cn=config dc=example,dc=com
binddn = cn=admin,cn=config
passwordfile = /etc/ldapscripts/ldapscripts.passwd
ldaphost =
Hacked backend for handling cn=config backends. I have not tested it
with any other setups than Ubuntus recommended setup (i.e. different
database types, different names for the cn=config tree, ...)
Should either go in the source at lp:backupninja/handlers/ldapconf.in or
on a running system at
