Your message dated Mon, 2 Mar 2026 21:51:15 +0100
with message-id
<CAK0Odpyznx+HthU1D-co_WZtrX7uHPs5yGhA2=brn7zwwtz...@mail.gmail.com>
and subject line Re: Bug#1129462: wireshark: debaudit/git2dsc regression in
4.6.4-1: 310 - gbp.conf but no corresponding commit
has caused the Debian Bug report #1129462,
regarding wireshark: debaudit/git2dsc regression in 4.6.4-1: 310 - gbp.conf but
no corresponding commit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1129462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1129462
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: wireshark
Version: 4.6.4-1
Severity: minor
User: [email protected]
Usertags: debaudit
Hi,
While working on https://debaudit.debian.net/, I ran into an issue with
wireshark/4.6.4-1, which is currently in unstable and trying to migrate to
forky.
debaudit detects the following issue in unstable:
> 310 - gbp.conf but no corresponding commit
Debaudit could not identify a Git tag in the repository specified by
Vcs-Git for this version. The package is maintained using
git-buildpackage (debian/gbp.conf is present) so the tag should follow
gbp's conventions. Maybe the tag was not pushed?
You can find more details at:
https://debaudit.debian.net/git2dsc/result/2ec7786643eb316d6d075adda98b7ee9918084e8ebf2941878073c71d4559c7a
The version in forky (4.6.3-1) tested fine, with the following diagnostic:
> 910 - git-generated dsc identical to archive dsc after normalization
You can find its result at:
https://debaudit.debian.net/git2dsc/result/a11716730143cfef902e765f5f2b7f279f6d5655a05c59ca2fb30bbfd9616868
Since Debaudit is in heavy development, I am very interested in hearing if the
issue was misdetected somehow.
Thanks,
Lucas Nussbaum
--- End Message ---
--- Begin Message ---
Control: fixed -1 4.6.4-1
Hi Lucas,
Lucas Nussbaum <[email protected]> ezt írta (időpont: 2026. márc. 1., V, 22:03):
>
> Source: wireshark
> Version: 4.6.4-1
> Severity: minor
> User: [email protected]
> Usertags: debaudit
>
> Hi,
>
> While working on https://debaudit.debian.net/, I ran into an issue with
> wireshark/4.6.4-1, which is currently in unstable and trying to migrate to
> forky.
>
> debaudit detects the following issue in unstable:
> > 310 - gbp.conf but no corresponding commit
> Debaudit could not identify a Git tag in the repository specified by
> Vcs-Git for this version. The package is maintained using
> git-buildpackage (debian/gbp.conf is present) so the tag should follow
> gbp's conventions. Maybe the tag was not pushed?
I tend to push the tag after I see the version being accepted, thus
adding some delay may help this workflow.
I'll probably switch to pushing the tag first.
Cheers,
Balint
> You can find more details at:
> https://debaudit.debian.net/git2dsc/result/2ec7786643eb316d6d075adda98b7ee9918084e8ebf2941878073c71d4559c7a
>
> The version in forky (4.6.3-1) tested fine, with the following diagnostic:
> > 910 - git-generated dsc identical to archive dsc after normalization
> You can find its result at:
> https://debaudit.debian.net/git2dsc/result/a11716730143cfef902e765f5f2b7f279f6d5655a05c59ca2fb30bbfd9616868
>
> Since Debaudit is in heavy development, I am very interested in hearing if the
> issue was misdetected somehow.
>
> Thanks,
>
> Lucas Nussbaum
--- End Message ---
