tags 519713 +pending thanks Actually, it does not only happen for the users, but also for groups etc. ;-) This is due to the corresponding postgres sequences/serial datatypes not being updated after prepopulating the DB. The next version will have the fix.
Why this doesn't trigger any key violations in the DB at runtime, I do not know. I guess it actually does but there must be something inside serendipity that handles this exception silently. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
