gnupg2 (2.4.3-2) [PTS] [DDPO]

OLD: VCS is behind the version in the archive: 2.2.40-1.1 < 2.4.3-2.

Git: https://salsa.debian.org/debian/gnupg2.git -b debian/main
JSON
Enter a full Vcs-* header, supported schemes are: Vcs-Bzr, Vcs-Cvs, Vcs-Darcs, Vcs-Git, Vcs-Hg, Vcs-Mtn, Vcs-Svn.
For Vcs-Git append -b branch to select the branch name; append [subdir] if the debian/ directory is not in the repository root.
The next upload will reset the information from the source package headers.
Branch: debian/unstable
Path: debian/changelog
Repo size: 429617152
Browser: https://salsa.debian.org/debian/gnupg2
Last scan: 2023-12-06 09:58:25+00
Next scan: 2023-12-11 19:10:00+00
Merge requests: 4

Debian changelog in Git:

gnupg2 (2.2.40-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * In migration CI test skip debian-archive-bookworm-stable.gpg (and
    aggregated keyring), gpg1 cannot read the ed25519 key. Closes: #1033155

 -- Andreas Metzler <ametzler@debian.org>  Sun, 26 Mar 2023 15:03:05 +0200

This branch is 1 commit ahead of tag debian/2.2.40-1.1

Git log:

commit d7adbe4da527be01f2abebc511008c9a0670219f
Author: Bastien Roucariès <rouca@debian.org>
Date:   Sat Aug 13 21:09:20 2022 +0000

    Re-apply merge request debian/gnupg2!8
    
    Improve systemd integration of gnupg by injecting environment variable
    at start/stop
    
    Previously we used to set SSH_AUTH_SOCK using systemd environment.
    
    The former approach has the following drawbacks:
    - the lifetime of SSH_AUTH_SOCK is not tied to the lifetime of the service
    - it is hard to know where variables are set
    - it is hard custumize the socket variable, for instance for running multiple ssh-agent or testing purpuse
    
    Moreover conceptually it is better to set the environment variable in the same file that run the
    service (or socket)