On Mon, Aug 17, 2009 at 01:13:46PM -0400, Daniel Richard G. wrote: > On Sun, 2009 Aug 16 21:01+0100, Mark Hindley wrote: > > > > Thanks for this. Interesting. When I originally went through sorting > > out the 2 server workaround for this, I considered (and rejected :)) > > this approach. > > > > The problem with it is that apt-cacher was designed to ignore the > > server path so that .debs from different servers were deemed > > identical. This is useful for people who use the path_map hopping to > > provide server redundancy. This approach will break that. > > How would the path be different between servers? We're talking > something like > > pool/main/z/zip/zip_2.32-1_amd64.deb > > which is reflected identically across all mirror servers. Sure, there's > the server hostname and path prefix (e.g. "/pub/mirrors/debian"), but > the path_map mechanism already abstracts all that away. > > Could you give an example of the breakage that is a concern?
I meant, if you weren't using the path_map at all. Currently, if one apt client requests ftp.uk.debian.org/debian/pool/main/z/zip/zip_2.32-1_amd64.deb and one ftp.us.debian.org/debian/pool/main/z/zip/zip_2.32-1_amd64.deb through the same apt-cacher instance, it will return the same /var/cache/apt-cacher/packages/zip_2.32-1_amd64.deb to both clients. If you add the host/path prefix to the cached file, this will no longer happen. I am not convinced this is a corner case. Note that path_map is not enabled by default. The reverse of this is also problematic: You have /var/cache/apt-cacher/packages/zip_2.32-1_amd64.deb. In your 2 stage process to smooth the transition with existing caches, do you serve that as a debian or ubuntu file, assuming it existed in both distros? Mark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
