PPA warning from Ubuntu 22.04

[spikefishjohn]

# apt update
Hit:1 http://us.archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu jammy-security InRelease
Hit:5 http://ppa.launchpad.net/gns3/ppa/ubuntu jammy InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: http://ppa.launchpad.net/gns3/ppa/ubuntu/dists/jammy/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
#

This is from man apt-key

DEPRECATION
       Except for using apt-key del in maintainer scripts, the use of apt-key is deprecated. This section shows how to replace existing use of apt-key.

       If your existing use of apt-key add looks like this:

       wget -qO- https://myrepo.example/myrepo.asc | sudo apt-key add -

       Then you can directly replace this with (though note the recommendation below):

       wget -qO- https://myrepo.example/myrepo.asc | sudo tee /etc/apt/trusted.gpg.d/myrepo.asc

       Make sure to use the "asc" extension for ASCII armored keys and the "gpg" extension for the binary OpenPGP format (also known as "GPG key public ring"). The binary OpenPGP format works for all apt versions, while the ASCII armored format works for apt
       version >= 1.4.

       Recommended: Instead of placing keys into the /etc/apt/trusted.gpg.d directory, you can place them anywhere on your filesystem by using the Signed-By option in your sources.list and pointing to the filename of the key. See sources.list(5) for details. Since
       APT 2.4, /etc/apt/keyrings is provided as the recommended location for keys not managed by packages. When using a deb822-style sources.list, and with apt version >= 2.4, the Signed-By option can also be used to include the full ASCII armored keyring
       directly in the sources.list without an additional file.

This is from man sources.list

       •   Signed-By (signed-by) is an option to require a repository to pass apt-secure(8) verification with a certain set of keys rather than all trusted keys apt has configured. It is specified as a list of absolute paths to keyring files (have to be accessible
           and readable for the _apt system user, so ensure everyone has read-permissions on the file) and fingerprints of keys to select from these keyrings. The recommended locations for keyrings are /usr/share/keyrings for keyrings managed by packages, and
           /etc/apt/keyrings for keyrings managed by the system operator. If no keyring files are specified the default is the trusted.gpg keyring and all keyrings in the trusted.gpg.d/ directory (see apt-key fingerprint). If no fingerprint is specified all keys
           in the keyrings are selected. A fingerprint will accept also all signatures by a subkey of this key, if this isn't desired an exclamation mark (!) can be appended to the fingerprint to disable this behaviour. The option defaults to the value of the
           option with the same name if set in the previously acquired Release file of this repository (only fingerprints can be specified there through). Otherwise all keys in the trusted keyrings are considered valid signers for this repository. The option may
           also be set directly to an embedded GPG public key block. Special care is needed to encode the empty line with leading spaces and ".":

               Types: deb
               URIs: https://deb.debian.org
               Suites: stable
               Components: main contrib non-free
               Signed-By:
                -----BEGIN PGP PUBLIC KEY BLOCK-----
                .
                mDMEYCQjIxYJKwYBBAHaRw8BAQdAD/P5Nvvnvk66SxBBHDbhRml9ORg1WV5CvzKY
                CuMfoIS0BmFiY2RlZoiQBBMWCgA4FiEErCIG1VhKWMWo2yfAREZd5NfO31cFAmAk
                IyMCGyMFCwkIBwMFFQoJCAsFFgIDAQACHgECF4AACgkQREZd5NfO31fbOwD6ArzS
                dM0Dkd5h2Ujy1b6KcAaVW9FOa5UNfJ9FFBtjLQEBAJ7UyWD3dZzhvlaAwunsk7DG
                3bHcln8DMpIJVXht78sL
                =IE0r
                -----END PGP PUBLIC KEY BLOCK-----

[eantowne]

How did you install the PPA? I have 22.04 running on both of my servers. GNS3 server was installed via sudo apt-add-repository ppa:gns3/ppa and am not receiving the apt-key warning.

ean@server1:~$ sudo apt update
[sudo] password for ean: 
Hit:1 https://download.docker.com/linux/ubuntu jammy InRelease
Hit:2 http://us.archive.ubuntu.com/ubuntu jammy InRelease                      
Get:3 http://us.archive.ubuntu.com/ubuntu jammy-updates InRelease [109 kB]     
Get:4 http://us.archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]  
Get:5 http://us.archive.ubuntu.com/ubuntu jammy-security InRelease [110 kB]    
Get:6 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [326 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu jammy-updates/main Translation-en [79.8 kB]
Get:8 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 c-n-f Metadata [5,720 B]
Get:9 http://us.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [211 kB]
Get:10 http://us.archive.ubuntu.com/ubuntu jammy-updates/restricted Translation-en [32.2 kB]
Get:11 http://us.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 c-n-f Metadata [536 B]
Get:12 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [134 kB]
Hit:13 https://ppa.launchpadcontent.net/gns3/ppa/ubuntu jammy InRelease
Get:14 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe Translation-en [47.3 kB]
Get:15 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f Metadata [2,736 B]
Get:16 http://us.archive.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [173 kB]
Get:17 http://us.archive.ubuntu.com/ubuntu jammy-security/restricted Translation-en [25.6 kB]
Get:18 http://us.archive.ubuntu.com/ubuntu jammy-security/restricted amd64 c-n-f Metadata [512 B]
Fetched 1,358 kB in 1s (2,106 kB/s)    
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
4 packages can be upgraded. Run 'apt list --upgradable' to see them

[spikefishjohn]

ooooh you know what, i'm controlling all aspects of my box with ansible now. The PPA was done through that so maybe its ansible's fault. I'll check that out and if its the PPA module in ansible messing things up i'll close this with how I corrected it.

[eantowne]

Normally I see that issue when the installation process is using apt-key to manually add the key, and manually adding the repo. I have never seen this pop up when using apt-add-repository.

[spikefishjohn]

Thanks for the hint, i'll check that out.

[spikefishjohn]

Per @eantowne this seems like its self induced and I haven't had a chance to look up what i'm doing wrong. I'll close this for now and re-open if needed later.

[marlon-figueroa]

Errors, throw message with not publish files apt-secure

[grossmj]

What error do you see? Can you provide more context/info?

Thanks.

[nonymous01]

j'ai un probleme avec mon ubuntu je n'arrive pas a fais la mise a jour j'ai des erreur 404

youssef@anonymous:~$ sudo apt update Atteint :1 https://dl.google.com/linux/chrome/deb stable InRelease
Ign :2 http://archive.ubuntu.com/ubuntu kinetic InRelease
Atteint :3 https://ppa.launchpadcontent.net/gns3/ppa/ubuntu kinetic InRelease
Atteint :4 http://packages.microsoft.com/repos/code stable InRelease
Ign :5 http://archive.ubuntu.com/ubuntu kinetic-updates InRelease
Ign :6 http://archive.ubuntu.com/ubuntu kinetic-backports InRelease
Atteint :7 https://packages.microsoft.com/ubuntu/22.10/prod kinetic InRelease
Ign :8 http://archive.ubuntu.com/ubuntu kinetic-security InRelease
Ign :9 https://ppa.launchpadcontent.net/nilarimogard/webupd8/ubuntu kinetic InRelease Err :10 http://archive.ubuntu.com/ubuntu kinetic Release
404 Not Found [IP : 91.189.91.82 80] Err :11 http://archive.ubuntu.com/ubuntu kinetic-updates Release 404 Not Found [IP : 91.189.91.82 80] Atteint :12 https://ppa.launchpadcontent.net/ubuntu-toolchain-r/test/ubuntu kinetic InRelease Err :13 http://archive.ubuntu.com/ubuntu kinetic-backports Release 404 Not Found [IP : 91.189.91.82 80] Err :14 http://archive.ubuntu.com/ubuntu kinetic-security Release
404 Not Found [IP : 91.189.91.82 80] Err :15 https://ppa.launchpadcontent.net/nilarimogard/webupd8/ubuntu kinetic Release 404 Not Found [IP : 185.125.190.52 443] Lecture des listes de paquets... Fait
E: Le dépôt http://archive.ubuntu.com/ubuntu kinetic Release ne contient plus de fichier Release.

[grossmj]

Kinetic was marked 'end of life' on July 20, 2023: https://wiki.ubuntu.com/Releases

We cannot release GNS3 for these 'deprecated' versions.

[nonymous01]

svp quelqu'un peut m'aider

[nonymous01]

voici la capture svp https://i.stack.imgur.com/kXLzx.png

[grossmj]

Tu dois mettre a jour ta version d'Ubuntu, Kinetic n'est plus supportee:

Pour mettre a jour : sudo do-release-upgrade

[nonymous01]

merci bien Monsieur grossmj