debsig-verify (0.34) [PTS] [DDPO]

COMMITS: VCS has seen 1 commit since the 0.34 tag

Git: https://git.dpkg.org/git/dpkg/debsig-verify.git
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: main
Path: debian/changelog
Repo size: 3616768
Browser: https://git.dpkg.org/cgit/dpkg/debsig-verify.git
Last scan: 2026-05-12 16:24:04+00
Next scan: 2026-05-13 13:36:00+00

Debian changelog in Git:

debsig-verify (0.34) unstable; urgency=medium

  * Update for new libdpkg-dev >= 1.23.0 API changes. Closes: #1123841
  * Documentation:
    - doc: Update TODO.
  * Packaging:
    - Remove «Rules-Requires-Root: no», which is the current default.
    - Remove «Priority: optional», which is the current default.

 -- Guillem Jover <guillem@debian.org>  Mon, 22 Dec 2025 21:19:35 +0100

This branch is 1 commit ahead of tag 0.34

Git log:

commit 4eb7bd79db6a905ec44d6430f700608040cff3f7
Author: Guillem Jover <guillem@debian.org>
Date:   Fri May 8 05:39:36 2026 +0200

    build: Set TAR_OPTIONS to avoid leaking maintainer information on dist
    
    The default tar invocation by automake leaks the user and group IDs and
    names into the tarball. And while those are probably going to be easy to
    infer, it is unnecessary to expose them. With the automake switch from
    tar format v7 to ustar this is now worse as it used to only leak the
    IDs, not the names.
    
    We set and export TAR_OPTIONS with --owner=0 and --group=0 to neuter the
    information leak. Although ideally automake would set those by default.