lancer apt-get update sur un hôte pointant sur mon miroir local renvoie les avertissements et erreurs suivants ...
W: The repository 'https://apt.devita.co/puppet xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://apt.devita.co/ubuntu xenial-backports Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://apt.devita.co/ubuntu xenial-security Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://apt.devita.co/ubuntu xenial-updates Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: The repository 'https://apt.devita.co/ubuntu xenial Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://apt.devita.co/puppet/dists/xenial/PC1/binary-AMD64/Packages
E: Failed to fetch https://apt.devita.co/ubuntu/dists/xenial-backports/main/binary-AMD64/Packages
E: Failed to fetch https://apt.devita.co/ubuntu/dists/xenial-security/main/binary-AMD64/Packages
E: Failed to fetch https://apt.devita.co/ubuntu/dists/xenial-updates/main/binary-AMD64/Packages
E: Failed to fetch https://apt.devita.co/ubuntu/dists/xenial/main/binary-AMD64/Packages
E: Some index files failed to download. They have been ignored, or old ones used instead.
vous pouvez voir des captures d'écran du dépôt local ici, et le dépôt est publiquement disponible temporairement pendant que je dépanne.
mon sources.list.d ressemble à ceci
# This file is managed by Puppet. DO NOT EDIT.
# puppetlabs-pc1
deb https://apt.devita.co/puppet xenial PC1 main
# This file is managed by Puppet. DO NOT EDIT.
# xenial-backports
deb https://apt.devita.co/ubuntu/ xenial-backports main restricted universe multiverse
# This file is managed by Puppet. DO NOT EDIT.
# xenial
deb https://apt.devita.co/ubuntu/ xenial main restricted universe multiverse
# This file is managed by Puppet. DO NOT EDIT.
# xenial-security
deb https://apt.devita.co/ubuntu/ xenial-security main restricted universe multiverse
# This file is managed by Puppet. DO NOT EDIT.
# xenial-updates
deb https://apt.devita.co/ubuntu/ xenial-updates main restricted universe multiverse
et le répertoire /var/www
est un lien symbolique vers les emplacements d’apt-mirror comme so
Nous en avons discuté le IRC dans #ubuntu-server
. Jusqu'à présent, il semble qu'une autorité de certification ajoutée à /etc/ssl/certs
ait cassé update-ca-certificates, donc /etc/ssl/certs/ca-certificates.crt
était cassé ou tout simplement vide, donc apt-transport-https
ne fonctionnait pas du tout.
Débogué avec: apt-get -o Debug::Acquire::https=1 update