Hi, I'm the same person that reported this bug. I never had your last answer, sorry. I don't remember using this email address. It's not valid.
I fixed the problem at some point, but I don't remember how, probably with some SQL voodoo. One thing I'm sure : I had neither touched the database nor done "upstream migration" before apt upgrade that caused this. I only found I had reported this bug because I was looking for the reason of a similar upgrade failure, with a diferent column, resetpass_token this time. This bug is definitely unreproducible now, but I'll open a new one for resetpass_token. BTW, is the database upgrade fragile ? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
