I had another case of this same problem on Squeeze upgrade. It was
quite confusing to me, as I am not experienced with LDAP and only had it
installed for another application. I changed the root DN after the
initial install, because the other application required it. I had no
idea that this would put my database in a conflicting state.
It would be really nice to help the user with this issue. I agree with
the suggestions from Dmitri. But even simpler than that, you could
point to some troubleshooting documentation when the reload fails, with
clear instructions on how to resolve the problem:
Open up the .ldif backup in a text editor. Modify the DN of the
first two entries to match the current rootdn.
Or maybe just delete these first two entries? I'm not sure what they're
for.
Andrew
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
