Source: npm Version: 9.2.0~ds3-1 Severity: minor User: [email protected] Usertags: debaudit
Hi, While working on https://debaudit.debian.net/, I ran into an issue with npm/9.2.0~ds3-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/4ebc48718ef8bfa19449d49a29496b8314c63ffd0fd5fa22b656daff80faea98 The version in forky (9.2.0~ds2-2) 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/2180e7674b1f0601aa0eb8bcb970343ba79a1a834fe5e481b90503ec4285e8a0 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
