Re: URGENT..! Very annoying when UPDATE = debian.map.fastlydns.net
On Thu 06 May 2021 at 08:43:22 (-0400), The Wanderer wrote:
> On 2021-05-06 at 08:40, Greg Wooledge wrote:
> > On Thu, May 06, 2021 at 08:33:47AM -0400, The Wanderer wrote:
> >> On 2021-05-06 at 08:28, Andrei POPESCU wrote:
> >> > > On Thu, May 06, 2021 at 07:00:02AM -0400, The Wanderer wrote:
> >> > > > ISTR that
> >> > > > this is the second complaint about this mirror not working correctly
> >> > > > we've seen in the past week or three; whether they are from different
> >> > > > people, or both from the same, I don't know.
Six days ago, and 11 timezones apart.
> >> > Maybe this helps (though it might be outdated):
> >> >
> >> > https://deb.debian.org
> >>
> >> That's the mirror auto-selector which the original complainant here was
> >> using, and which apparently chose debian.map.fastlydns.net as the mirror
> >> to be used, which led to the error which was the subject of the complaint.
> >>
> >> IOW, I think that site is part of the problem (in that it has a broken
> >> mirror listed), but I don't see how it could help. Is there a part of
> >> your suggestion I'm not understanding?
> >
> > I believe the suggestion was that you actually *go* to that web page
> > in your web browser and read what it says. It's fairly short.
>
> I did, and I didn't see how it was helpful, thus my question.
I went there too, once I realised that it was a reference to be
browsed, rather than something to do with one's sources.list.¹
> > To be fair, though, it'll basically reiterate advice that was
> > already given in this thread ("try a different mirror").
I thought the page rather full of gobbledegook, talking about SRV
records and CDN instances. As for trying a different mirror, the only
occurrence of "mirror" is "This service provides mirrors for the
following Debian archive repositories".
And the instance chosen, "cdn-fastly.deb.debian.org" is not actually
among these mysterious SRV records, "_http._tcp.deb.debian.org",
"prod.debian.map.fastly.net" and "dpvctowv9b08b.cloudfront.net" that
we're not even told how to obtain.
> Which might help in the immediate term, but doesn't get the actual
> problem fixed, that problem being either with the mirror or with the
> configuration of the redirector to include that mirror.
Yes, more useful might be a page something like one of these:
https://packages.debian.org/buster/amd64/base-files/download
that might get you back on your feet.
¹ Now after reading
https://lists.debian.org/debian-user/2021/05/msg00238.html
I'm not even sure about that. I was under the impression,
from this list, that https was best avoided in favour of http.
Cheers,
David.
Reply to: