Source: rails Version: 2:7.2.3+dfsg-3 Severity: minor User: [email protected] Usertags: debaudit
Hi, While working on https://debaudit.debian.net/, I ran into an issue with rails/2:7.2.3+dfsg-3, 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/99027090911777a79c1e9ee9ca0e1e9805a42057df861680cebd99a651d4e8cd The version in forky (2:7.2.2.2+dfsg-2) 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/29ead8bba637a07f227445946096f1d03d6e79a409b2e62ab17c10fdd73f2dfe Since Debaudit is in heavy development, I am very interested in hearing if the issue was misdetected somehow. Thanks, Lucas Nussbaum
