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

Reply via email to