Debian Package Tracker
Register | Log in
Subscribe

gnupg2

GNU privacy guard - a free PGP replacement (dummy transitional package)

Choose email to subscribe with

general
  • source: gnupg2 (main)
  • version: 2.4.8-5
  • maintainer: Debian GnuPG Maintainers (archive) (DMD)
  • uploaders: Eric Dorland [DMD] – Daniel Kahn Gillmor [DMD] – Andreas Metzler [DMD]
  • arch: all any
  • std-ver: 4.7.2
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 2.2.27-2+deb11u2
  • o-o-sec: 2.2.27-2+deb11u2
  • oldstable: 2.2.40-1.1+deb12u1
  • stable: 2.4.7-21
  • testing: 2.4.8-4
  • unstable: 2.4.8-5
versioned links
  • 2.2.27-2+deb11u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.2.40-1.1+deb12u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.4.7-21: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.4.8-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.4.8-5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • dirmngr (10 bugs: 0, 6, 4, 0)
  • gnupg (87 bugs: 0, 66, 21, 0)
  • gnupg-agent (42 bugs: 0, 34, 8, 0)
  • gnupg-l10n
  • gnupg-utils
  • gnupg2 (36 bugs: 0, 22, 14, 0)
  • gpg (20 bugs: 0, 15, 5, 0)
  • gpg-agent (15 bugs: 0, 11, 4, 0)
  • gpg-wks-client (1 bugs: 0, 1, 0, 0)
  • gpg-wks-server
  • gpgconf (1 bugs: 0, 1, 0, 0)
  • gpgsm (5 bugs: 0, 5, 0, 0)
  • gpgv (4 bugs: 0, 4, 0, 0)
  • gpgv-static
  • gpgv-udeb
  • gpgv-win32
  • scdaemon (11 bugs: 0, 9, 2, 0)
  • tpm2daemon
action needed
2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:
  • CVE-2025-68972: In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.
  • CVE-2025-68973: In GnuPG through 2.4.8, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
Created: 2025-12-28 Last update: 2025-12-30 04:31
1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:
  • CVE-2025-68972: In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.
Created: 2025-12-28 Last update: 2025-12-30 04:31
2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:
  • CVE-2025-68972: In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.
  • CVE-2025-68973: In GnuPG through 2.4.8, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
Created: 2025-12-28 Last update: 2025-12-30 04:31
3 security issues in bullseye high

There are 3 open security issues in bullseye.

2 important issues:
  • CVE-2025-68972: In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.
  • CVE-2025-68973: In GnuPG through 2.4.8, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
1 issue postponed or untriaged:
  • CVE-2025-30258: (postponed; to be fixed through a stable update) In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a valid backsig or that has incorrect usage flags, the user loses the ability to verify signatures made from certain other signing keys, aka a "verification DoS."
Created: 2025-12-28 Last update: 2025-12-30 04:31
3 security issues in bookworm high

There are 3 open security issues in bookworm.

2 important issues:
  • CVE-2025-68972: In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.
  • CVE-2025-68973: In GnuPG through 2.4.8, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
1 issue left for the package maintainer to handle:
  • CVE-2025-30258: (needs triaging) In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a valid backsig or that has incorrect usage flags, the user loses the ability to verify signatures made from certain other signing keys, aka a "verification DoS."

You can find information about how to handle this issue in the security team's documentation.

Created: 2025-03-20 Last update: 2025-12-30 04:31
2 new commits since last upload, is it time to release? normal
vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:
commit ea3bce9fef7e8eed88240b06ca360dc20d08a3f6
Author: Andreas Metzler <ametzler@bebt.de>
Date:   Tue Dec 30 07:22:20 2025 +0100

    Patch metadata: Add upstream bug references to gpg.fail patches
    
    Gbp-Dch: Ignore

commit 89ce641af32bee9fc81e93fffbf6d912769ffeb9
Author: Andreas Metzler <ametzler@bebt.de>
Date:   Tue Dec 30 06:49:48 2025 +0100

    gpg: Do not use a default when asking for another output filename.
    
    https://gpg.fail/filename #2
    Unfuzzed patch from GIT master
Created: 2025-12-30 Last update: 2025-12-30 08:32
1 bug tagged help in the BTS normal
The BTS contains 1 bug tagged help, please consider helping the maintainer in dealing with it.
Created: 2019-03-21 Last update: 2025-12-30 08:30
5 bugs tagged patch in the BTS normal
The BTS contains patches fixing 5 bugs (6 if counting merged bugs), consider including or untagging them.
Created: 2025-01-06 Last update: 2025-12-30 08:30
lintian reports 3 warnings normal
Lintian reports 3 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2025-12-30 Last update: 2025-12-30 05:30
debian/patches: 43 patches to forward upstream low

Among the 49 debian patches available in version 2.4.8-5 of the package, we noticed the following issues:

  • 43 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.
Created: 2023-02-26 Last update: 2025-12-30 08:00
Standards version of the package is outdated. wishlist
The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.3 instead of 4.7.2).
Created: 2025-12-23 Last update: 2025-12-29 23:00
testing migrations
  • excuses:
    • Migration status for gnupg2 (2.4.8-4 to 2.4.8-5): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • ∙ ∙ Autopkgtest for apt/3.1.12: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for aptly/1.6.2-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for archlinux-keyring/0~20251116-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for ca-certificates-java/20240118: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for debsig-verify/0.33: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for debsigs/0.2.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for devscripts/2.25.30: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for dgit/13.20: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for di-netboot-assistant/0.79: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for diffoscope/309: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for distrobuilder/3.2-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for dput-ng/1.44: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for dulwich/0.24.10-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for extrepo/0.14: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for flatpak/1.16.2-1: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for freedombox/25.17.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for freeipa/4.12.4-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for git-annex/10.20251029-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for git-evtag/2022.1-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for git-revise/0.7.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for gnupg1/1.4.23-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for gnupg2/2.4.8-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for gpgme1.0/2.0.1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for jetring/0.32: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for keyring-pass/0.9.3-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for laniakea-spark/0.1.1-1: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for libgnupg-interface-perl/1.04-6: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for libmail-gnupg-perl/0.23-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for libpgp-sign-perl/1.04-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for lintian/2.127.0: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered (failure will be ignored), s390x: Pass
    • ∙ ∙ Autopkgtest for lxc/1:6.0.5-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for mandos/1.8.19-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for mkosi/26-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for mmdebstrap/1.5.7-3: amd64: Failed (not a regression) ♻ (reference ♻), arm64: Failed (not a regression) ♻ (reference ♻), i386: Failed (not a regression) ♻ (reference ♻), ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Failed (not a regression) ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for notmuch/0.39-1: amd64: Pass, arm64: Pass, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for octavia/17.0.0-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for openpgp-applet/1.1-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for ostree/2025.7-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for paperkey/1.6-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for patatt/0.6.3-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for pgpgpg/0.13-12: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for php-crypt-gpg/1.6.11-2: amd64: Pass, arm64: Regression ♻ (reference ♻), i386: Pass, ppc64el: Failed (not a regression) ♻ (reference ♻), riscv64: Test triggered, s390x: Regression ♻ (reference ♻)
    • ∙ ∙ Autopkgtest for pius/3.0.0-8: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for podman/5.7.0+ds2-3: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-apt/3.1.0: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-debian/1.0.1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python-gnupg/0.5.4-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for python3-lxc/1:5.0.0-2: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for reform-tools/1.82-3: amd64: No tests, superficial or marked flaky ♻ (reference ♻), arm64: Pass, i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for repo/2.58-4: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for rust-sequoia-git/0.4.0-5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for rust-sequoia-gpg-agent/0.6.2-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for rust-sequoia-wot/0.15.0-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for sbuild/0.91.5: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for sdkmanager/0.6.11-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for skopeo/1.21.0~pre1-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for snapd/2.71-3: amd64: Pass, arm64: No tests, superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or marked flaky ♻, riscv64: Test triggered, s390x: No tests, superficial or marked flaky ♻
    • ∙ ∙ Autopkgtest for systemd/259-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Autopkgtest for tomb/2.13+dfsg-1: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Test triggered, s390x: Pass
    • ∙ ∙ Lintian check waiting for test results on riscv64 - info
    • ∙ ∙ Too young, only 0 of 2 days old
    • Additional info (not blocking):
    • ∙ ∙ Updating gnupg2 will fix bugs in testing: #1124221
    • ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gnupg2.html
    • ∙ ∙ Reproducible on amd64 - info ♻
    • ∙ ∙ Waiting for reproducibility test results on arm64 - info ♻
    • Not considered
news
[rss feed]
  • [2025-12-29] Accepted gnupg2 2.4.8-5 (source) into unstable (Andreas Metzler)
  • [2025-10-26] gnupg2 2.4.8-4 MIGRATED to testing (Debian testing watch)
  • [2025-10-22] Accepted gnupg2 2.4.8-4 (source) into unstable (Daniel Kahn Gillmor) (signed by: dkg@debian.org)
  • [2025-08-29] gnupg2 2.4.8-3 MIGRATED to testing (Debian testing watch)
  • [2025-08-21] Accepted gnupg2 2.4.8-3 (source) into unstable (Andreas Metzler)
  • [2025-08-19] gnupg2 2.4.8-2 MIGRATED to testing (Debian testing watch)
  • [2025-08-11] Accepted gnupg2 2.4.8-2 (source) into unstable (Andreas Metzler)
  • [2025-06-29] Accepted gnupg2 2.4.8-1 (source) into experimental (Andreas Metzler)
  • [2025-06-21] Accepted gnupg2 2.2.40-1.1+deb12u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Andreas Metzler)
  • [2025-06-06] gnupg2 2.4.7-21 MIGRATED to testing (Debian testing watch)
  • [2025-06-01] Accepted gnupg2 2.4.7-21 (source) into unstable (Andreas Metzler)
  • [2025-06-01] gnupg2 2.4.7-19 MIGRATED to testing (Debian testing watch)
  • [2025-05-31] Accepted gnupg2 2.4.7-20 (source) into experimental (Andreas Metzler)
  • [2025-05-14] Accepted gnupg2 2.4.7-19 (source) into unstable (Andreas Metzler)
  • [2025-05-11] Accepted gnupg2 2.4.7-18 (source) into experimental (Andreas Metzler)
  • [2025-05-09] gnupg2 2.4.7-17 MIGRATED to testing (Debian testing watch)
  • [2025-04-28] Accepted gnupg2 2.4.7-17 (source) into unstable (Andreas Metzler)
  • [2025-04-26] Accepted gnupg2 2.4.7-16 (source) into unstable (Andreas Metzler)
  • [2025-04-26] gnupg2 2.4.7-15 MIGRATED to testing (Debian testing watch)
  • [2025-04-16] Accepted gnupg2 2.4.7-15 (source) into unstable (Daniel Kahn Gillmor) (signed by: dkg@debian.org)
  • [2025-04-12] Accepted gnupg2 2.4.7-14 (source) into unstable (Daniel Kahn Gillmor) (signed by: dkg@debian.org)
  • [2025-04-10] Accepted gnupg2 2.4.7-13 (source) into unstable (Daniel Kahn Gillmor) (signed by: dkg@debian.org)
  • [2025-04-08] Accepted gnupg2 2.4.7-12 (source) into experimental (Daniel Kahn Gillmor) (signed by: dkg@debian.org)
  • [2025-03-31] Accepted gnupg2 2.4.7-11 (source) into experimental (Andreas Metzler)
  • [2025-03-28] gnupg2 2.2.46-6 MIGRATED to testing (Debian testing watch)
  • [2025-03-22] Accepted gnupg2 2.2.46-6 (source) into unstable (Andreas Metzler)
  • [2025-03-20] gnupg2 2.2.46-5 MIGRATED to testing (Debian testing watch)
  • [2025-03-17] Accepted gnupg2 2.4.7-10 (source) into experimental (Andreas Metzler)
  • [2025-03-13] Accepted gnupg2 2.4.7-9 (source) into experimental (Daniel Kahn Gillmor) (signed by: dkg@debian.org)
  • [2025-03-13] Accepted gnupg2 2.2.46-5 (source) into unstable (Daniel Kahn Gillmor) (signed by: dkg@debian.org)
  • 1
  • 2
bugs [bug history graph]
  • all: 229 241
  • RC: 0
  • I&N: 173 182
  • M&W: 56 59
  • F&P: 0
  • patch: 5 6
  • help: 1
links
  • homepage
  • lintian (0, 3)
  • buildd: logs, reproducibility, cross
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • l10n (-, 67)
  • debian patches
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2.4.8-4ubuntu1
  • 70 bugs (1 patch)
  • patches for 2.4.8-4ubuntu1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing