libglib-perl (3:1.329.3-3) [PTS] [DDPO]

NEW: VCS has unreleased changes: 3:1.329.3-4 > 3:1.329.3-3

Git: https://salsa.debian.org/perl-team/modules/packages/libglib-perl.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: master
Path: debian/changelog
Repo size: 901120
Browser: https://salsa.debian.org/perl-team/modules/packages/libglib-perl
Last scan: 2025-10-09 03:02:07+00
Next scan: 2025-10-15 16:20:00+00

Debian changelog in Git:

libglib-perl (3:1.329.3-4) UNRELEASED; urgency=medium

  * Don't embed date in generated manpages

 -- intrigeri <intrigeri@debian.org>  Thu, 17 Jul 2025 12:35:10 +0000

This branch is 2 commits ahead of tag debian/3%1.329.3-3

Git log:

commit 34207dada641382f4f9aec85932dcacf66d5f0fa
Author: intrigeri <intrigeri@riseup.net>
Date:   Thu Jul 17 12:28:34 2025 +0000

    Update debian/changelog.
    
    Gbp-Dch: Ignore

commit 822d32c474a48ea3faf42e2e651b16edde8dc7e6
Author: intrigeri <intrigeri@riseup.net>
Date:   Thu Jul 17 12:26:02 2025 +0000

    Don't embed date in generated manpages
    
    These dates trigger "Multi-Arch: same" file conflicts when binNMUs
    are scheduled on different dates on multiple architectures.
    
    Another option, in theory, is to request another set of binNMUs to get things
    back in line whenever the problem arises. In the case at hand, nobody did that
    since the problem started 9 months ago, hence this attempt to make the problem
    go away once and for all.
    
    For more context, see #1104854.