"Le fichier de version n'est pas encore valide" et d'autres erreurs lors de l'exécution d'apt-get update
J'utilise Ubuntu 18.04 sur un Lenovo Legion Y520 (16 Go de RAM, processeur i7-7700HQ de 7e génération). Lorsque j'exécute la commande apt-get update, le message suivant s'affiche:
$ Sudo apt-get update
Hit:2 http://us.archive.ubuntu.com/ubuntu bionic InRelease
Ign:3 http://download.opensuse.org/repositories/home:/strycore/xUbuntu_18.04 ./ InRelease
Hit:4 http://ppa.launchpad.net/arx/release/ubuntu bionic InRelease
Get:1 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB]
Hit:6 http://download.opensuse.org/repositories/home:/strycore/xUbuntu_18.04 ./ Release
Hit:8 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease
Get:5 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease [83.2 kB]
Ign:10 http://ppa.launchpad.net/gregory-hainaut/pcsx2.official.ppa/ubuntu bionic InRelease
Ign:11 http://ppa.launchpad.net/jd-team/jdownloader/ubuntu bionic InRelease
Get:7 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Hit:12 http://ppa.launchpad.net/libretro/stable/ubuntu bionic InRelease
Ign:13 http://ppa.launchpad.net/micove/console/ubuntu bionic InRelease
Hit:14 http://ppa.launchpad.net/minetestdevs/stable/ubuntu bionic InRelease
Hit:15 http://ppa.launchpad.net/nilarimogard/webupd8/ubuntu bionic InRelease
Ign:16 http://ppa.launchpad.net/noobslab/apps/ubuntu bionic InRelease
Hit:18 http://ppa.launchpad.net/persepolis/ppa/ubuntu bionic InRelease
Hit:19 http://ppa.launchpad.net/webupd8team/Java/ubuntu bionic InRelease
Err:20 http://ppa.launchpad.net/gregory-hainaut/pcsx2.official.ppa/ubuntu bionic Release
404 Not Found [IP: 91.189.95.83 80]
Err:21 http://ppa.launchpad.net/jd-team/jdownloader/ubuntu bionic Release
404 Not Found [IP: 91.189.95.83 80]
Err:22 http://ppa.launchpad.net/micove/console/ubuntu bionic Release
404 Not Found [IP: 91.189.95.83 80]
Err:23 http://ppa.launchpad.net/noobslab/apps/ubuntu bionic Release
404 Not Found [IP: 91.189.95.83 80]
Get:17 http://ppa.launchpad.net/pcsx2-team/pcsx2-daily/ubuntu bionic InRelease [15.9 kB]
Reading package lists... Done
E: Release file for http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease is not valid yet (invalid for another 2h 38min 48s). Updates for this repository will not be applied.
E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease is not valid yet (invalid for another 2h 38min 53s). Updates for this repository will not be applied.
E: Release file for http://us.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease is not valid yet (invalid for another 2h 39min 9s). Updates for this repository will not be applied.
E: The repository 'http://ppa.launchpad.net/gregory-hainaut/pcsx2.official.ppa/ubuntu bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/jd-team/jdownloader/ubuntu bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/micove/console/ubuntu bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/noobslab/apps/ubuntu bionic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Release file for http://ppa.launchpad.net/pcsx2-team/pcsx2-daily/ubuntu/dists/bionic/InRelease is not valid yet (invalid for another 3h 41min 24s). Updates for this repository will not be applied.
Le problème est que, chaque fois que j'essaie d'ajouter un référentiel récemment, j'obtiens la même erreur: le fichier de publication n'est pas valide et la mise à jour à partir d'un tel référentiel ne peut pas être effectuée de manière sécurisée. Au début, je pensais que le référentiel/programme est obsolète, mais même des programmes populaires comme Retroarch me donnent la même erreur. J'ai essayé au moins 5 différents, tous les mêmes.
Voici mon sources.list:
# deb cdrom:[Ubuntu 18.04 LTS _Bionic Beaver_ - Release AMD64 (20180426)]/ bionic main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://us.archive.ubuntu.com/ubuntu/ bionic main restricted
# deb-src http://us.archive.ubuntu.com/ubuntu/ bionic main restricted
## Major bug fix updates produced after the final release of the
## distribution.
deb http://us.archive.ubuntu.com/ubuntu/ bionic-updates main restricted
# deb-src http://us.archive.ubuntu.com/ubuntu/ bionic-updates main restricted
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ bionic universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ bionic universe
deb http://us.archive.ubuntu.com/ubuntu/ bionic-updates universe
# deb-src http://us.archive.ubuntu.com/ubuntu/ bionic-updates universe
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://us.archive.ubuntu.com/ubuntu/ bionic multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://us.archive.ubuntu.com/ubuntu/ bionic-updates multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ bionic-updates multiverse
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://us.archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
# deb-src http://us.archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse
## Uncomment the following two lines to add software from Canonical's
##'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
#deb http://archive.canonical.com/ubuntu bionic partner
#deb-src http://archive.canonical.com/ubuntu bionic partner
deb http://security.ubuntu.com/ubuntu bionic-security main restricted
# deb-src http://security.ubuntu.com/ubuntu bionic-security main restricted
deb http://security.ubuntu.com/ubuntu bionic-security universe
# deb-src http://security.ubuntu.com/ubuntu bionic-security universe
deb http://security.ubuntu.com/ubuntu bionic-security multiverse
# deb-src http://security.ubuntu.com/ubuntu bionic-security multiverse
Je cherchais une solution depuis une semaine et je n’en ai trouvé aucune. S'il vous plaît faites votre réponse autant "noob-friendly" que possible, je suis encore en train d'apprendre.
Merci beaucoup!
J'ai ouvert le premier que j'ai vu ( http://ppa.launchpad.net/gregory-hainaut/pcsx2.official.ppa/ubuntu/dists/ ) en regardant quelles versions sont prises en charge; et bionic (18.04) n’est pas là (c’est-à-dire qu’il n’est pas supporté).
Votre solution consiste à la commenter ou à la supprimer (voir Comment puis-je corriger une erreur 404 lors de l’utilisation d’un PPA ou de la mise à jour de mes listes de paquets? pour plus d’informations [fournie par karel]), puis en trouver une autre 'réparer' pour quelque raison que ce soit que vous l'avez ajouté.
Utiliser cette source avec votre version n’est pas très convivial, cela risque de poser des problèmes, il est donc plus facile de trouver un remplaçant.
FYI: Le lien que j'ai fourni était issu de votre sortie. Je viens de naviguer dans le dossier dists/où chaque version supportée est visible (par nom, 18.04 est bionique, 16.04 est xenial ( xenial est présent, 16.04 est supporté ) etc.).