GnuPG package repository (stable releases) for Debian 13 »Trixie«

This repository provides the recent stable release of GnuPG and its dependencies.

This software was built and packaged by the GnuPG project. We provide packages of our software through our package repositories.

These packages are intended for users who want (or need) to use the latest upstream versions of our projects. This includes stable releases as well as beta versions for testing, depending on the repository you pick. We keep these packages as close to the upstream releases as possible. This means that in addition to bleeding edge versions, these packages also do not contain patches that would make the software behave differently from what we intended.

Therefore, you will get all new features and the default behavior of GnuPG. Some distributions only provide patched packages that are missing some new features or behave rather differently compared to our original upstream releases.

Should you run into technical issues or bugs related to our packages, please do not hesitate to contact us. A good place to look for help is our forum or the GnuPG users mailing list.

You may also want to read the information on how to file bug reports. Please do not use the bug tracker of your distribution for issues with packages that you installed from our repositories, but get in touch with us.

For more information on the packages in this repository, please visit https://www.gnupg.org.

First install our signing key (32097B719B3745D6E61DDA1B85C45AE3E1A2B355). You can do so by using an installed version of gpg directly:

sudo gpg \
  --no-default-keyring \
  --keyring /usr/share/keyrings/gnupg-keyring.gpg \
  --fetch-keys https://repos.gnupg.org/deb/gnupg/trixie/gnupg-signing-key.gpg

Note: On distributions that have replaced gpgv with sqv for the signature verification process in apt, this may result in an error during apt update later, because sqv doesn’t support the keybox format. In these cases or if you prefer it, you can also use wget, curl, or similar tools (see blow). Alternatively, you can also make apt use gpgv again for signature verification, either by calling apt update -o APT::Key::gpgvcommand="/usr/bin/gpgv" instead of apt update, or permanently by adding a file like /etc/apt/apt.conf.d/90gpgv containing the line APT::Key::gpgvcommand "/usr/bin/gpgv";.

# if you prefer wget:
wget -O- https://repos.gnupg.org/deb/gnupg/trixie/gnupg-signing-key.gpg | \
  sudo gpg --dearmor --yes --output /usr/share/keyrings/gnupg-keyring.gpg

# if you prefer curl:
curl https://repos.gnupg.org/deb/gnupg/trixie/gnupg-signing-key.gpg | \
  sudo gpg --dearmor --yes --output /usr/share/keyrings/gnupg-keyring.gpg

After fetching the key make sure it is readable:

sudo chmod a+r /usr/share/keyrings/gnupg-keyring.gpg

Then add the repository to your package management:

echo "Types: deb deb-src
URIs: https://repos.gnupg.org/deb/gnupg/trixie/
Suites: trixie
Components: main
Signed-By: /usr/share/keyrings/gnupg-keyring.gpg" | \
  sudo tee /etc/apt/sources.list.d/gnupg.sources

Now you should be able to install/upgrade our packages:

sudo apt update
sudo apt upgrade
sudo apt install gnupg2

During the configuring stage, our packages should stop running services like gpg-agent anddirmngr to avoid incompatibility issues. New instances will be started automatically by GnuPG the first time they are needed.

In case you need gpg-agent running (e.g., to establish a SSH connection), you can restart it manually:

gpgconf --launch gpg-agent