Your message dated Sun, 1 Mar 2026 22:48:43 +0100
with message-id
<CAJxTCxwGqtNgdAagzKvQ1wJY4pX=exfz6UgN9=d1glotwam...@mail.gmail.com>
and subject line Re: [Pkg-javascript-devel] Bug#1129440: nodejs:
debaudit/git2dsc regression in 22.22.0+dfsg+~cs22.19.13-1: 310 - gbp.conf but
no corresponding commit
has caused the Debian Bug report #1129440,
regarding nodejs: debaudit/git2dsc regression in 22.22.0+dfsg+~cs22.19.13-1:
310 - gbp.conf but no corresponding commit
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1129440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1129440
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Le dim. 1 mars 2026 à 22:03, Lucas Nussbaum <[email protected]> a écrit :
> 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?
>
The tag was missing. Done and pushed.
--- End Message ---
--
Pkg-javascript-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
