Skip to content

Conversation

michaelweghorn
Copy link

Use a file apt-repos.gpg inside of the /etc/apt/trusted.gpg.d
directory for the GPG keyring instead of the legacy
/etc/apt/trusted.gpg.

Related Debian NEWS entry:

apt (2.4.0) unstable; urgency=medium

GPG verification now first tries only the trusted.gpg.d keys, before
then falling back to the legacy trusted.gpg keyring and issuing a
warning to migrate keys if verification succeeded in the fallback.

-- Julian Andres Klode [email protected] Tue, 22 Feb 2022 20:01:00 +0100

In my case, on Debian testing with apt 2.4.1, no fallback was
automatically used and GPG verification just failed when
running make tests without this change in place.

Use a file `apt-repos.gpg` inside of the `/etc/apt/trusted.gpg.d`
directory for the GPG keyring instead of the legacy
`/etc/apt/trusted.gpg`.

Related Debian NEWS entry:

> apt (2.4.0) unstable; urgency=medium
>
>   GPG verification now first tries only the trusted.gpg.d keys, before
>   then falling back to the legacy trusted.gpg keyring and issuing a
>   warning to migrate keys if verification succeeded in the fallback.
>
>  -- Julian Andres Klode <[email protected]>  Tue, 22 Feb 2022 20:01:00 +0100

In my case, on Debian testing with apt 2.4.1, no fallback was
automatically used and GPG verification just failed when
running `make tests` without this change in place.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant