Control: close -1 In the past, I pushed my tag the next day after uploading, when I got the mail, that the package was accepted in unstable. Because of this new service, I have to adjust my workflow apparently.
Am 2. März 2026 07:55:56 MEZ schrieb Lucas Nussbaum <[email protected]>: >Source: netcfg >Version: 1.202 >Severity: minor >User: [email protected] >Usertags: debaudit > >Hi, > >While working on https://debaudit.debian.net/, I ran into an issue with >netcfg/1.202, 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/6117a9a9d5023ae9f5d17eec4b8a2d567f4034decebae17dafef955fc06b6b40 > >The version in forky (1.201) 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/f4b729a5b1adfcde740900e4136d22a6c4c4877682965aa77ff2e92b2f95e66b > >Since Debaudit is in heavy development, I am very interested in hearing if the >issue was misdetected somehow. > >Thanks, > >Lucas Nussbaum > -- Sent from /e/ OS on Fairphone3
