Is buffindexed overview corruption problem fixed in -STABLE?

[Katsuhiro Kondou]

In article <Pine.BSF.4.21.0011071735570.64985-100000 at vax.chrillesen.dk>,
	Anonymous Coward <anonymous at Drunken.Newsbastards.org> wrote;

} In other words, with buffindexed, the order of overview entries
} is unimportant (since the dropped overview! data will usually
} result in out-of-order entries), while there is no duplicate
} detection/elimination.

Duplicate detection/elimination is done when retrieving.  This
means running expireover after additional overchan cleans them.

} If I have incorrect/corrupted overview data, the only way to fix
} it with buffindexed would be to wipe out the existing overview
} and while *not* running innd, use makehistory -O ...

If you don't care total article number in result of GROUP until
next expireover, you can do it.
-- 
Katsuhiro Kondou