Si ejecutando apt-get update, obtenemos el mensaje:
W: Fallo al obtener http://ftp.de.debian.org/debian/dists/jessie-updates/InRelease No se pudo encontrar la entrada esperada «main/binary-amd64/Packages» en el archivo «Release» (entrada incorrecta en «sources.list» o fichero mal formado)
E: No se han podido descargar algunos archivos de índice, se han omitido, o se han utilizado unos antiguos en su lugar.
W: Failed to fetch http://ftp.de.debian.org/debian/dists/jessie-updates/InRelease Unable to find expected entry ‘main/source/Sources’ in Release file (Wrong sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones used instead.
Simplemente deberemos de actualizar nuestra lista de repositorios y configurar los paquetes Debian desde archive.debian.org.
Para ello, hacer el siguiente cambio entro del fichero /etc/apt/sources.list :
Comentamos las líneas jessie-updates que tengamos:
# deb http://ftp.de.debian.org/debian/ jessie-updates main non-free contrib # deb-src http://ftp.de.debian.org/debian/ jessie-updates main non-free contrib
, y la configuramos en archive:
deb http://archive.debian.org/debian/ jessie contrib main non-free
Hecho esto, limpiamos la lista de paquetes descargados previamente y actualizamos de nuevo el repositorio:
apt-get clean apt-get update
El pasado mes de marzo de 2019 la gente de Debian movió los paquetes del repositorio jessie-updates a la rama archive.
Fuente: lists.debian.org
Muchas gracias amigo!
De repente un equipo me mando ese mensaje, y no supe de que era.. si no se le realizan cambios. Ahora, ya he podido hacer que se actualicen los paquetes. Gracias!
Ahora, tengo una duda y de antemano te agradecería mucho en lo que me pudiese ayudar. Tengo otro equipo, y al mandar apt update, me muestra el siguiente mensaje de error:
Get:1 http://security.debian.org/debian-security stretch/updates InRelease [93.6 kB]
Err:1 http://security.debian.org/debian-security stretch/updates InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9D6D8F6BC857C906
Ign:2 http://ftp.mx.debian.org/debian stretch InRelease
Hit:4 http://ftp.mx.debian.org/debian stretch Release
Get:3 http://ftp.mx.debian.org/debian stretch-updates InRelease [90.3 kB]
Err:3 http://ftp.mx.debian.org/debian stretch-updates InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7638D0442B90D010
Fetched 90.3 kB in 6s (13.9 kB/s)
Reading package lists… Done
Building dependency tree
Reading state information… Done
All packages are up to date.
W: http://security.debian.org/debian-security/dists/stretch/updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://security.debian.org/debian-security/dists/stretch/updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://security.debian.org/debian-security/dists/stretch/updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://security.debian.org/debian-security/dists/stretch/updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://security.debian.org/debian-security/dists/stretch/updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://security.debian.org/debian-security stretch/updates InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9D6D8F6BC857C906
W: http://ftp.mx.debian.org/debian/dists/stretch/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://ftp.mx.debian.org/debian/dists/stretch/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://ftp.mx.debian.org/debian/dists/stretch/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://ftp.mx.debian.org/debian/dists/stretch/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://ftp.mx.debian.org/debian/dists/stretch/Release.gpg: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://ftp.mx.debian.org/debian/dists/stretch-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://ftp.mx.debian.org/debian/dists/stretch-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://ftp.mx.debian.org/debian/dists/stretch-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://ftp.mx.debian.org/debian/dists/stretch-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: http://ftp.mx.debian.org/debian/dists/stretch-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg are ignored as the file is not readable by user ‘_apt’ executing apt-key.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ftp.mx.debian.org/debian stretch-updates InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7638D0442B90D010
W: Failed to fetch http://security.debian.org/debian-security/dists/stretch/updates/InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9D6D8F6BC857C906
W: Failed to fetch http://ftp.mx.debian.org/debian/dists/stretch-updates/InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 7638D0442B90D010
W: Some index files failed to download. They have been ignored, or old ones used instead.
Creo que ya me cargue el sistema (lo bueno que ya viene Debian 10) 😀
y bueno, te comento en un update me mando un error parecido al de tu post, y seguí varias tutos(hasta el de eliminar las llaves) y creo que eso fue por lo que termine jodiendo mas mi sistema (en cuanto a la actualización, porque lo demás funciona impecable) 🙁
Buenos días Óscar.
Intenta regenerar de nuevo los ficheros con las claves GPG de los paquetes.
Para ello:
1.- Mueve tus claves actuales a un directorio de backup:
>> mv /etc/apt/trusted.gpg.d/ /etc/apt/trusted.gpg.d-old/2.- Reinstala el paquete de firmas:
>> apt-get install --reinstall debian-archive-keyring3.- Borra caché de paquetes y actualiza de nuevo:
>> apt-get clean>> apt-get updateUn saludo!
Después de hacer todo lo indicado, sigue dando error GPG
Las firmas siguientes no se pudieron verificar porque su clave pública no está disponible: NO_PUBKEY 4B8EC3BAABDC4346
W: Error de GPG: http://archive.debian.org jessie Release: Las firmas siguientes no se pudieron verificar porque su clave pública no está disponible: NO_PUBKEY 8B48AD6246925553