Your message dated Sat, 07 Mar 2026 13:31:59 +0000
with message-id <[email protected]>
and subject line fixed
has caused the Debian Bug report #1129494,
regarding seergdb: debaudit/git2dsc regression in 2.6+git20251009+ds-2: 330 -
failed to guess tag
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.)
--
1129494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1129494
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: seergdb
Version: 2.6+git20251009+ds-2
Severity: minor
User: [email protected]
Usertags: debaudit
Hi,
While working on https://debaudit.debian.net/, I ran into an issue with
seergdb/2.6+git20251009+ds-2, which is currently in unstable and trying to
migrate to
forky.
debaudit detects the following issue in unstable:
> 330 - failed to guess tag
Debaudit could not identify a Git tag in the repository specified by
Vcs-Git for this version. Maybe the tag was not pushed?
You can find more details at:
https://debaudit.debian.net/git2dsc/result/d3e27e34e013c9546b1e6fcb89c2b8aae185c67582c5a27d84cf29ac170e74b3
The version in forky (2.6+git20251009+ds-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/dda73aeabff94893a56310717afee42ad1a5f29c32414fb9e41a4de6cffbbb21
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 ---
fixed
--- End Message ---
