OK. It's unreproducible, so even if it gets fixed, it's unlikely
we'll know for sure. It might even be a file system failure, and not
aptitude's fault at all.
But perhaps the bug has left clues in the failing system. Are there any
files I should submit, investigate, or preserve in case they might yield
a clue? Or should I just wipe the freshly installed system and try
again?
I did try an update ('u' in the interactive aptitude) to see if it made
a difference. It didn't.
Should I try replacing pkgstates by pkgstates.old?
Is there some way I could examine the pkgstates and pkgstates.old for
clues? They look like binary gibberish. Is this perhaps a file-system
screwup? When I use file on it, it reports
/freshetch/var/lib/aptitude/pkgstates: data
but on my other Debian boxes (both sarge and etch) it reports
/var/lib/aptitude/pkgstates: ASCII text
The failing system is the only one where I've used jfs.
-- hendrik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
