On 28/10/2013 8:36 PM, Anders Ingemann wrote: > On 28 October 2013 12:51, Charles Plessy <[email protected] > <mailto:[email protected]>> wrote: > > Le Sun, Oct 27, 2013 at 03:22:55PM +0100, Anders Ingemann a écrit : > > > > Your script uses > > > MIRROR=http://cloudfront.debian.net > > I thought cloudfront was added to the http redirector > (http.debian.net <http://http.debian.net>, > > meaning you can use that URL instead)? Or am I wrong? > > Hi Anders and everybody, > > I have the impression that the http redirector does not > send to cloudfront... > > admin@ip-172-31-31-51:~$ GET -e http://http.debian.net/demo/debian/ > <chomp> > > James, any idea when this will work?
It seems the http.debian.net script sometimes marks cloudfront as not being in sync, and I've not been able to track down why this is. It has only been put in service via http.debian.net in a number of places - not universally - again, I've not had time to dissect logs. In my direct usage of cloudfront.debian.net in apt/sources.list across many hosts in many Regions (and on-premise at home), I've not had any issues with its consistency, but the http.debian.net script seems to reject this randomly. We went through a period earlier this year of reducing the cache timeout for certain objects (files under /debian/dists and /debian/trace) down to the values I spoke of at DebConf - 10 seconds or 5 seconds, and still the http.debian.net script seems to think they are out of sync. I've got a copy of the http.debian.net script (https://github.com/rgeissert/http-redirector/) but I am not sure how to configure it to be my own test for cloudfront. There's more hacking to do in here. I have wondered if using http://ftp.debian.org/ is the correct upstream to use for this distribution, of or there is a better recommendation as the upstream mirror - suggestions welcome? James -- /Mobile:/ +61 422 166 708, /Email:/ james_AT_rcpt.to
