Bug#1053812: Pretty sure #1053812 is fixed in 4.2

[Russ Allbery]

Jonathan Kamens  writes:

> So, Russ sent me his apt-listchanges database and I took a lot at it and
> it was very messed up.

> There was a bug in 4.1 which was uncovered and fixed a couple of days ago
> as a result of Alexandre Detiste's push to add typing hints to the
> program. This bug would have caused the type of corruption that I saw in
> Russ's database, so I'm pretty sure it will go away in 4.2.

I installed 4.2 locally and then did an apt upgrade and everything worked
correctly, so I am also hopeful.  4.2 is on its way to experimental now.

-- 
Russ Allbery (r...@debian.org)  

Bug#1053812: Pretty sure #1053812 is fixed in 4.2

[Jonathan Kamens]

So, Russ sent me his apt-listchanges database and I took a lot at it and 
it was very messed up.


There was a bug in 4.1 which was uncovered and fixed a couple of days 
ago as a result of Alexandre Detiste's push to add typing hints to the 
program. This bug would have caused the type of corruption that I saw in 
Russ's database, so I'm pretty sure it will go away in 4.2.


In addition, the structure of the database has been revamped in 4.2 so 
when upgrading to 4.1 to 4.2 the program is going to throw away the old 
database and start from scratch, which will clear out the corruption.


In addition, to facilitate debugging issues like this in the future, 
I've added new state snapshotting functionality to the program which 
will only be deployed in experimental releases. Here's 
 
the commit if you're curious. Here's 
 
the changelog showing everything significant that will be in 4.2.


  jik