From: Daniel Smolik <marvin@xxxxxxxxxx> Date: Fri, 26 May 2006 18:22:15 +0200 > I test it on my E250 with debian sid and 2.6.17-rc4. With 2.6.16.16 no > problem with status database. I switch to 2.6.17-rc4 install some > package and DB is corrupted. Reboot to 2.6.16.16 and all works. I > applied your patch and situation is the same as without patch still db > corruption. Thanks for testing. Can you double check to make absolutely sure you had my patch applied? You seem to have a really good reproducable test case for this, how do you do it? Perhaps we can somehow take the state of your package database, and what it tries to update it to, to make some self-contained reproducable test case. - To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
