Hi everyone,
I did encounter a strange behavior with my squid-deb-proxy server.
on the master Debian repository server I forced publish an already existing Debian package having the same version 0.1 (my bad, I won't do it again)
my squid-deb-proxy configuration looks like:
...
# refresh pattern for debs and udebs
refresh_pattern deb$ 129600 100% 129600
refresh_pattern udeb$ 129600 100% 129600
refresh_pattern tar.gz$ 129600 100% 129600
# always refresh Packages and Release files
refresh_pattern \/(Packages|Sources)(|\.bz2|\.gz|\.xz)$ 0 0% 0
refresh_pattern \/Release(|\.gpg)$ 0 0% 0
refresh_pattern \/InRelease$ 0 0% 0
...
as far as I understand, the Packages and Release files are always refreshed from the master repository server, but I quite do not understand the meaning of "129600 100% 129600" for Debian packages.
I interpret that the Debian packages stay in the cache and are not refreshed. So my package legacy-tools_0.1_all.deb and Release file got updated on the master repository and only the Release file got updated through the squid-deb-proxy but the old version mismatching the Release size of the package is still available in the cache.
does this make sense?
Best Regards
--
Eric
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
