Comment 16 for bug 14929

This is definitely a 2.1->2.2 upgrade issue. I'm going to tag it for 5.10,
since I assume we'll sync 2.2 packages sometime before then, and watch to
see how it's resolved in Debian, perhaps helping with some simple slapcat
output mungers to fix easily-solved issues (like the root uid one), rather
than just rely entirely on a README file.

Also, dropping severity to normal, as it will at least be an issue with a
documented workaround by the time we get to caring about it.