Source: node-chalk
Version: 5.6.2+dfsg-4
Severity: minor
User: [email protected]
Usertags: debaudit

Hi,

While working on https://debaudit.debian.net/, I ran into an issue with
node-chalk/5.6.2+dfsg-4, 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/021f4d2a1d65e8cd255a8e7da89d876e421c03789f2056a97f6c38659398d3a7

The version in forky (5.6.0-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/4dad9d32bf52537a4b60b5b5bbd420539718c55688f4b38e74a32602bf172c1a

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

Reply via email to