Bug#1007971: Key location is deprecated? Show me!
Control: tag -1 wontfix
On Sat, Mar 19, 2022 at 08:46:17PM +0100, Harald Dunkel wrote:
> Package: apt
> Version: 2.4.1
> Severity: wishlist
>
> apt update gives me several messages like
>
> W: http://example.com/debian/dists/unstable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
> W: https://download.something.com/linux/debian/dists/buster/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
> W: https://updates.ohnonotagain.org/desktop/apt/dists/xenial/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
>
> This could be much more helpful if it would actually show the key id
> it was looking for. *All* warnings and errors about some key id should
> show it.
I don't think this is going to happen. It adds additional work,
keyid is the wrong thing to show (fpr would be the right thing),
and you really should not have to bother with GPG keys at all,
just files.
I think we should also hide from error messages which keys are
missing.
Showing key ids of any form just leads to people Googling for
key ids and finding weird instructions on how to add them.
--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer i speak de, en
Reply to: