Error when using sudo apt-get update on ubuntu 22.04

Asked by Siddhesh Kokate

output/error :
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 https://dl.yarnpkg.com/debian stable InRelease
Get:3 http://security.debian.org/debian-security jessie/updates InRelease [44.9 kB]
Hit:4 http://in.archive.ubuntu.com/ubuntu jammy InRelease
Ign:5 http://security.ubuntu.com/ubuntu security.ubuntu.com InRelease
Hit:6 http://in.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:7 http://security.ubuntu.com/ubuntu bionic-security InRelease
Hit:8 http://in.archive.ubuntu.com/ubuntu jammy-backports InRelease
Err:9 http://security.ubuntu.com/ubuntu security.ubuntu.com Release
  404 Not Found [IP: 2620:2d:4000:1::16 80]
Err:3 http://security.debian.org/debian-security jessie/updates InRelease
  The following signatures were invalid: EXPKEYSIG 9D6D8F6BC857C906 Debian Security Archive Automatic Signing Key (8/jessie) <email address hidden> The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AA8E81B4331F7F50
Reading package lists... Done
E: The repository 'http://security.ubuntu.com/ubuntu security.ubuntu.com 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.
W: https://dl.yarnpkg.com/debian/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
W: GPG error: http://security.debian.org/debian-security jessie/updates InRelease: The following signatures were invalid: EXPKEYSIG 9D6D8F6BC857C906 Debian Security Archive Automatic Signing Key (8/jessie) <email address hidden> The following signatures couldn't be verified because the public key is not available: NO_PUBKEY AA8E81B4331F7F50
E: The repository 'http://security.debian.org/debian-security jessie/updates InRelease' is not signed.
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.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Siddhesh Kokate
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Don't mix Debian sources with Ubuntu. They have different dependencies you'll end up with a big mess.

Who told you to add that repo..... and why?

Revision history for this message
Manfred Hampl (m-hampl) said :
#2

For diagnostic purposes please provide the output that you receive for the following commands:

uname -a
lsb_release -crid
find /etc/apt -name '*.list' -exec bash -c 'echo -e "\n$1\n"; cat -n "$1"' _ '{}' \;

Revision history for this message
Siddhesh Kokate (siddheshkokate) said :
#3

problem solved