On Wed, Jul 02, 2008 at 11:09:18AM +0300, Andrei Popescu <[EMAIL PROTECTED]> was heard to say: > Not really. See #201842 and #479620. Unfortunately Daniel Burrows still > didn't comment on them. Maybe he will show up here?
The main reason I haven't touched those bugs is that there are many more important things to work on. This behavior might be annoying when it hits you, but the files that are wiped out are all cache files that you can download from the network when your connection is re-established. A secondary reason is that I can't figure out what's going on, because whenever I try taking my network down and running an update, my package lists are still around afterwards. I've read over the code and it looks to me like it only deletes the old package lists when it successfully downloaded new ones. Until I get more of a clue to go on, this looks to me like a way to waste a great deal of time. I put the apt-get and aptitude code up side-by-side and I can only see one difference in the conditions they use to determine whether to clean the lists. I don't see why this would matter (surely pkgAcquire::Run returns Failure if files can't be downloaded?), but if there's anyone who *can* reproduce this on demand, it would be interesting to know if the attached patch helps. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
