On Fri, 08 Feb 2019 22:45:49 +0000, Richard Kettlewell wrote:

> Martin Gregorie  writes:
>> On Fri, 08 Feb 2019 20:52:56 +0000, Richard Kettlewell wrote:
>>> Martin Gregorie  writes:
>>>> This is the second time that I've wanted to run an upgrade on my RPi
>>>> at about this time, around 18:00-19:00 on Friday: the previous
>>>> failure was a week ago.
>>>>
>>>> Have any of you seen this previously?
>>>>
>>>> Attempts to retrieve .deb files only result in multiple failures (14)
>>>> of in 'apt-get upgrade' this time as it tried to fetch nine .deb
>>>> files.
>>>>
>>>> Each of these gets an HTTP 302 response (this is a redirect) and all
>>>> are associated with IP 93.93.128.193 port 80 which curl can't access
>>>
>>> How are you testing this and what is the error output?
>>
>> If you're running a bash script that starts with
>>
>>   apt-get update apt-get upgrade ...
>>
>> from the console, as I am, its in your face - a whole list of 'E:'
>> prefixed lines reporting problems and, because my script checks exit
>> codes after each apt-xxx command, I know its "apt-get upgrade" that's
>> failing.
>
> If you won’t quote the error output then understanding the problem is
> not going to be practical.
>
>> ... and I find that 93.93.128.193 belongs to mythic-beasts.com, not to
>> raspberrypi.org
>
> MB are RPi’s web hosts.
>
>> - and they tell me that 93.93.128.193 is an old reference that should
>> not be used.
>
> Who told you this and how?

A bloke at mystic. By email.


--
Martin    | martin at
Gregorie  | gregorie dot org

--- SoupGate-Win32 v1.05