Same situation here as Tony's (Debian + Ubuntu), using path_map. My solution was to run two separate instances of apt-cacher, but having one handle both would be preferable.
> Now I can change the code a bit to not remove the parent directories > when storing the files. However the next problem are people that > already have a working cache - the stored files would need to be moved > to the "correct" locations but this is a bit complicated without > knowing their origin. Is it necessary to move the existing package files? Could not apt-cacher check for e.g. packages/debian_pool_main_f_foo_foo_1.1-1_i386.deb first, and packages/foo_1.1-1_i386.deb second? Keep up the expirations on the "path-less" package files, and this could allow for a painless migration of users' repositories to the new convention, over time. --Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
