Bug#447646: apt-cacher: upstream server caught mid-sync causes indefinite false hits and constant client MD5Sum mismatch errors

2007-10-29 Thread Mark Hindley
The more I think about this issue, the more I think this is a problem with your mirror. - A mirror should sync in an atomic way so that it can never ship a partial file as being complete. - If you are dealing with a broken mirror you can force a refresh using by specifying Acquire::http::

Bug#447646: apt-cacher: upstream server caught mid-sync causes indefinite false hits and constant client MD5Sum mismatch errors

2007-10-22 Thread Mark Hindley
severity 447646 important thanks Since there is a workaround using the No-Cache option, I propose to downgrade this to important Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#447646: apt-cacher: upstream server caught mid-sync causes indefinite false hits and constant client MD5Sum mismatch errors

2007-10-22 Thread Mark Hindley
Thanks for this. Could you give me a bit more info: Are you using checksumming? Can you send the debug output of one of the 'stuck' retrievals On Mon, Oct 22, 2007 at 01:03:49PM -0700, Tony Godshall wrote: > When upstream server is caught mid-sync and apt-cacher downloads only > a partial file,

Bug#447646: apt-cacher: upstream server caught mid-sync causes indefinite false hits and constant client MD5Sum mismatch errors

2007-10-22 Thread Tony Godshall
Package: apt-cacher Version: 1.5.5 Severity: grave Justification: renders package unusable When upstream server is caught mid-sync and apt-cacher downloads only a partial file, apt-get on client identifies it as a MD5Sum mismatch error. Without apt-cacher, this is easily handled- one simply runs