Bug#876508: apt-secure: apt-secure doesn't know how to handle armored keyfiles
Control: forcemerge 876508 -1
On Wed, 04 Oct 2017 21:54:16 +0000 kwadronaut - debian
<kwadronaut-debian@riseup.net> wrote:
> Package: apt
> Version: 1.4.7
> Severity: normal
>
> Dear Maintainer,
>
> when adding an old-style armored key, apt fails to use this. If you dump
> such a keyfile inside etc/apt/trusted.gpg.d/ (or
> /usr/share/keyrings/name.gpg, with accompanying sources file) apt-update
> will choke because it thinks the public key isn't available.
You can still use it if you name it name.asc
The problem is that apt does not report when a keyring file cannot be
used and why.
I've merged this bug report with the previous one (#876508).
Saludos
Reply to: