Source: libtoxcore Version: 0.2.22-1 Severity: minor User: [email protected] Usertags: debaudit
Hi, While working on https://debaudit.debian.net/, I ran into an issue with libtoxcore/0.2.22-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/3c6bf9fea48577c19dcb75740d10b0f178aff7813ce94b121ff2170bf2f41355 The version in forky (0.2.20-1) tested fine, with the following diagnostic: > 900 - git-generated dsc identical to archive dsc You can find its result at: https://debaudit.debian.net/git2dsc/result/6d5223922e3d2d561df3d7d1e04c932076e7ee7a24b5c71cabc4564cd8babe16 Since Debaudit is in heavy development, I am very interested in hearing if the issue was misdetected somehow. Thanks, Lucas Nussbaum
