Hoi,

About the second issue, the logs record the following:

Downloading package lists from http://ftp-master.debian.org/i18n/ ...
failed to wget http://ftp-master.debian.org/i18n/md5sum
  buster
failed to wget http://ftp-master.debian.org/i18n/buster
  sid
failed to wget http://ftp-master.debian.org/i18n/sid
  stretch
failed to wget http://ftp-master.debian.org/i18n/stretch
  timestamp
failed to wget http://ftp-master.debian.org/i18n/timestamp
  timestamp.gpg
failed to wget http://ftp-master.debian.org/i18n/timestamp.gpg
buster: FAILED open or read
sid: FAILED open or read
stretch: FAILED open or read
timestamp: FAILED open or read
timestamp.gpg: FAILED open or read

That's weird, those files exist. But then we get this:

ddtp@ddtp:~$ wget -O - http://ftp-master.debian.org/i18n/buster
--2018-05-17 19:16:11--  http://ftp-master.debian.org/i18n/buster
Resolving ftp-master.debian.org (ftp-master.debian.org)... 138.16.160.17
Connecting to ftp-master.debian.org
(ftp-master.debian.org)|138.16.160.17|:80...
connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://ftp-master.debian.org/i18n/buster [following]
--2018-05-17 19:16:11--  https://ftp-master.debian.org/i18n/buster
Connecting to ftp-master.debian.org
(ftp-master.debian.org)|138.16.160.17|:443...
connected.
ERROR: The certificate of `ftp-master.debian.org' is not trusted.

That's just plain weird.

At a guess, it looks like ftp-master.debian.org is signed by a CA that the
system doesn't recognise? Yet the file /etc/ssl/certs/DST_Root_CA_X3.pem is
present and appears to contain the correct certificate.

What am I missing?

Have a nice day,
Martijn


On 16 May 2018 at 00:54, Thomas Vincent <tho...@vinc-net.fr> wrote:

>
> > BTW we're still getting th emails "Lisa..." but I don't know why,
> > ddtp2.debian.net is up and working, at least from the translators PoV...
>
> The "Lisa" messages basically say that FTP masters fail to find new
> translations where they should normally be located. Last time we had a
> similar recurring issue (around november 2016), it was related to some
> incorrect rsync parameters. I just asked on #debian-ftp how we can
> identify the current problem and fix it.
>
>
-- 
Martijn van Oosterhout <klep...@gmail.com> http://svana.org/kleptog/
_______________________________________________
Debian-l10n-devel mailing list
Debian-l10n-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-l10n-devel

Reply via email to