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:56:20 MEZ schrieb Lucas Nussbaum <[email protected]>: >Source: nobootloader >Version: 1.74 >Severity: minor >User: [email protected] >Usertags: debaudit > >Hi, > >While working on https://debaudit.debian.net/, I ran into an issue with >nobootloader/1.74, which is currently in unstable and trying to migrate to >forky. > >debaudit detects the following issue in unstable: >> 330 - failed to guess tag >Debaudit could not identify a Git tag in the repository specified by >Vcs-Git for this version. Maybe the tag was not pushed? > >You can find more details at: >https://debaudit.debian.net/git2dsc/result/9a4b7a8c8c08e6da56d7a470f687bbd8d7e432da8bb94044bd7c1e68c9edbcee > >The version in forky (1.73) 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/8b96d88ab3e8aa6769ffe7e4eb8e098dd62a0bdf452a606bb5ad612054197600 > >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
