Source: gcc-arm-none-eabi Version: 15:15.2.rel1.1-3 Severity: minor User: [email protected] Usertags: debaudit
Hi, While working on https://debaudit.debian.net/, I ran into an issue with gcc-arm-none-eabi/15:15.2.rel1.1-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/3d7aa6b845efa04e99187b7037d4e9c9f791ad513ed52090ec6330d174eefbea The version in forky (15:14.2.rel1-1) tested fine, with the following diagnostic: > 900 - git-generated dsc identical to archive dsc You can find its result at: https://debaudit.debian.net/git2dsc/result/dbc85c50eec80e8761b89deff4d986ef49f6c987fdc3ebcb5f860fd4db610ad8 Since Debaudit is in heavy development, I am very interested in hearing if the issue was misdetected somehow. Thanks, Lucas Nussbaum
