I've installed the patch; the one update I've done since has been fine. I'll have to use it for awhile to see how it works.
I notice 1.5.5 has this changelog entry: * Respect no-cache directives in request and pass through to upstream. Does the patch do anything different? I'm not http expert. I also noticed that my cache was almost empty a few days ago, even though I had migrated my whole apt cache over when I first installed it. That difficulty might be related to this problem: if debs that aren't in the Releases files are deleted, and the releases file is old, then stuff will get zapped. But there was almost nothing in apt-cacher's cache, so maybe something else was going on. Also, it seems really odd that Releases and Releases.gpg, with the same time stamp on the server, would be treated differently by any intermediate caching software. That, plus the reported lack of such software in the pipeline, makes me wonder if something else is going on. Maybe the Debian archive update changes the two files at much different times, and I just happen to be hitting the servers routinely while an update is in progress? But that doesn't explain why I see the problem with apt-cacher but not (much) with apt. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
