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:
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:
Since Debaudit is in heavy development, I am very interested in hearing if the
issue was misdetected somehow.

Thanks,

Lucas Nussbaum

Hi Lucas,

Lucas Nussbaum <lucas@debian.org> ezt írta (időpont: 2026. márc. 1., V, 22:03):

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

Hi Lucas,

Lucas Nussbaum <lucas@debian.org> ezt írta (időpont: 2026. márc. 1., V, 22:03):

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

Hi Bálint,

Don't change your workflow just yet.
This set of bugs was just an experiment, and your feedback is useful.
I'll think about it.

One problem is that I'd like report regressions only, so the status in
forky needs to be available (to compare with the new status in sid). But
if I wait for too long to give the maintainer time to tag after acceptance,
then the package might migrate and I will lose the status in testing. So
I probably need to work around this with a more complex logic.

Lucas