I R A Darth Aggie wrote:
> On Mon, 25 Mar 2019 19:53:23 +0000,
> The Natural Philosopher , in
>  wrote:
>>  On 25/03/2019 19:26, I R A Darth Aggie wrote:
>>> Oh, and usually when you encounter a 404 error in debian-style
>>> repository, it is because your package list is out of sync with the
>>> remote provider. apt-get update should cure that issue.
>>
>>  Its is apt-get update that is throwing the errors
>
> I think your assessment that some sort of ISP caching is a good one,
> since apt-get update is simply asking for the Packages file from
>
> http://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/
>
> which we all know exists.
>
> The OP might want to try from the pi account
>
> wget \
> http://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages
>
> and see what happens, but I expect another 404. But, I just read that
> https is not cachable, so maybe
>
> wget \
>
https://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages
>
> might be just the trick to see if there is some caching going on.
I tried:
wget
\http://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages
and
wget
\https://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages
I hope the syntax is right

The result is this:
wget
\http://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages
converted
'http://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages'
(ANSI_X3.4-1968) ->
'http://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages'
(UTF-8)
--2017-06-24 01:48:41--
http://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages
Resolving archive.raspberrypi.org (archive.raspberrypi.org)...
93.93.128.230, 93.93.130.39, 93.93.135.188, ...
Connecting to archive.raspberrypi.org
(archive.raspberrypi.org)|93.93.128.230|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2017-06-24 01:48:41 ERROR 404: Not Found.

With https the result is this:
 wget
\https://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages
converted
'https://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages
'
(ANSI_X3.4-1968) ->
'https://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages
'
(UTF-8)
--2017-06-24 01:44:18--
https://archive.raspberrypi.org/debian/dists/jessie/main/binary-armhf/Packages
Resolving archive.raspberrypi.org (archive.raspberrypi.org)...
46.235.227.11, 93.93.128.230, 93.93.128.133, ...
Connecting to archive.raspberrypi.org
(archive.raspberrypi.org)|46.235.227.11|:443... connected.
ERROR: The certificate of 'archive.raspberrypi.org' is not trusted.
ERROR: The certificate of 'archive.raspberrypi.org' is not yet
activated.
The certificate has not yet been activated

What do you think about it ?

--
Roby

--- SoupGate-Win32 v1.05