Eduard Bloch wrote: > Ehm. You won't find debrep there because this message is caused by an > internal job trying to find the original source URL of a certain index > (i.e. volatile) file in order to update it, and if everything else > fails, it attempts to interpret the cache directory itself as the remote > host.
So I always thought of apt-cacher-ng as a transparent cache. I always thought it would simply cache the deb files when they were requested. But the above and other behavior implies that it tries to update the cache from upstream sites more like a mirror. Updating the packages even if they are not requested by a proxy. Is that what it is doing? Just curious... > However, the version in Stable prefers the cache-repo-as-hostname method > before trying others, and there were some heuristics to guess whether > this makes more sense than the URL stored in the file's metadata (the > .head file in the same directory). This was changed in the last > Sid/Testing version(s) but IIRC that change is not in wheezy-backports > yet. > > So here is the plan: I suggest you wait a couple of days until I upload > a wheezy-backports version and then you try to reproduce it. I like the plan. I will be happy to try the wheezy-backports version when it is available. There is no rush. Thanks! Bob
signature.asc
Description: Digital signature
