On Wed, Mar 26, 2008 at 08:19:04PM +0100, Raúl Sánchez Siles wrote: > Well, you're right, the thing is how this situation arises. TBH I don't > really know how to get into this, I've tried several things, truncating a > file that I know that aptitude will download to 0 bytes and also to stop it > in the middle of a download and then truncating the result e.g. to half its > downloaded size. apt-cache understood the situation and marked the file as > corrupted before starting over to download the file.
To be honest, that sounds perfectly correct behaviour. > Maybe there's some issue > on the apt-cache integrity DB if such a thing exists. Yes is does. Are you using checksumming (checksum=1 in config file)? I am still trying to get a handle on what you problem is. Has this situation arisen for you? Exactly what happened? Is it reproducible? If it is, enabling debugging info (debug=1 in the config file) will put lots of useful info into /var/log/apt-cacher/error.log. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
