Source: nodejs Version: 22.22.0+dfsg+~cs22.19.13-1 Severity: minor User: [email protected] Usertags: debaudit
Hi, While working on https://debaudit.debian.net/, I ran into an issue with nodejs/22.22.0+dfsg+~cs22.19.13-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/84d07bc06c11bbf8bb85bac47f7ed9be06920f93fcef2285647cc96c72801521 The version in forky (22.22.0+dfsg+~cs22.19.6-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/1e18ce9f2bf312544c27cf92e3b09199e574044534e63eea2da947a38d9738fd Since Debaudit is in heavy development, I am very interested in hearing if the issue was misdetected somehow. Thanks, Lucas Nussbaum -- Pkg-javascript-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
