On Wed, 2009 Aug 19 22:50+0100, Mark Hindley wrote: > > > > 5. If no, complain that the package can't be imported. > > > > Does this sound reasonable? #5 would be a new behavior for the > > import script, but these would be files that apt-cacher-cleanup.pl > > would blow away anyway. > > I think i would leave them to be cleaned normally
Even if the package files are current, they can't be imported properly if no index files are cached. So these could end up being summarily deleted, and if they were the only copy the user had... that would be a problem! > Have you tried running it with checksumming enabled? How is the > database coping? It works fine with one client downloading. Checksums are retrieved and compared successfully for the long-named package files. With two or more clients, however, I run into what appears to be an unrelated bug: a deadlock at line 49 in apt-cacher-lib-cs.pl. strace(1) shows a futex() call hanging, and the affected apt-cacher2 process only responds to SIGKILL. I can reproduce this with stock 1.6.8. Could you try this? I set up two Ubuntu machines (one 32-bit, one 64-bit) to download a large set of packages, already in the apt-cacher cache. Both download runs start out fine, but after ten or twenty or so packages, each one hangs at [Waiting for headers]. What's worse, if you kill and restart the client (apt- get), the download hangs straightaway---it's the server that's borked. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
