Poblem z kluczami w repozytoriach dodatkowych

[tomsdb]

0

Od początku instalacji Linuxmint 21 przy odświeżaniu repozytoriów pojawia się taki błąd.

Kod:

W: https://repo.skype.com/deb/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: http://ppa.launchpad.net/danielrichter2007/grub-customizer/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.
W: http://ppa.launchpad.net/kdenlive/kdenlive-stable/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.

W sumie wszystko działa, ale da się to jakoś naprawić? Lekko denerwujące jest.

[dedito]

1

Wszystko działa bo to w zasadzie tylko ostrzeżenie, o czym świadczy litera W na początku.
Komunikat wskazuje gdzie szukać dalszych informacji.

Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details

Tak więc

Kod:

$man apt key

i tam we wskazanej sekcji mamy:

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.

Możesz skorzystać z jednej z metod opisanych w https://askubuntu.com/questions/1398344/...ing-system

Takie najszybsze, aczkolwiek niezalecane "rozwiązanie", to:

Kod:

$cd /etc/apt
$sudo cp trusted.gpg trusted.gpg.d

Takie zalecane to wylistowanie kluczy:

Kod:

$sudo apt-key list

i potem przenosiny

Kod:

$sudo apt-key export id_klucza | sudo gpg --dearmour -o /etc/apt/trusted.gpg.d/nazwa.gpg

i na koniec usunięcie klucza ze starej lokalizacji

Kod:

$sudo apt-key del id_klucza

Przykład:

Example fix:

For this warning message with sudo apt update...

W: http://ppa.launchpad.net/team-xbmc/ppa/u.../InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

We look in sudo apt-key list and find this entry for xbmc...

pub  rsa1024 2009-01-20 [SC]
      1897 01DA 570C 56B9 488E  F60A 6D97 5C47 91E7 EE5E
uid          [ unknown] Launchpad PPA for XBMC for Linux

Then we convert this entry to a .gpg file, using the last 8 numeric characters from above...

sudo apt-key export 91E7EE5E | sudo gpg --dearmour -o /etc/apt/trusted.gpg.d/team-xbmc.gpg

Repeat the above commands for each warning message generated by sudo apt update.

[tomsdb]

0

Czyli jednak muszę podłubać w systemie. Dzięki za wyczerpującą odpowiedź. Zajmę się tym w wolnym czasie.

[dedito]

0

Nie musisz, ale jak Cię denerwuje ten komunikat no to musisz