Comment 8 for bug 225485

I have to say that I am happy it works for me now and have not looked into it any further. I will admit that I found the description of how things were supposed to work and be set up so difficult to understand that I gave up almost instantly and just tried whether using the latest debian version recompiled for hardy would fix it. That was the case.

My understanding is now that apt-cacher-ng looks at the sources.list file for the computer where it runs and extracts some information there to put in backends_* While I don't completely understand why that is necessary, I wonder if this will work as expected in a LAN environment where apt-cacher-ng serves a number of machines with possibly different distros and mirrors (all deb-based, of course).

The mirror I use is ubuntu.intergenia.de.

Again, this seems to be fixed for both Brian and me with the post-hardy version, so everything is cool with me, at least.