Source: node-babel7 Version: 7.20.15+ds1+~cs214.269.168-13 Severity: minor User: [email protected] Usertags: debaudit
Hi, While working on https://debaudit.debian.net/, I ran into an issue with node-babel7/7.20.15+ds1+~cs214.269.168-13, 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/e8bb3e516e7bef04607f9992a38883353ead265cc05127f3fa3082114f148386 The version in forky (7.20.15+ds1+~cs214.269.168-11) 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/e8d5d8bfcf1a5de5990a01946119b20c03c41560411204e5e751898069b8dc61 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
