On Mon, Mar 16, 2026, at 8:06 PM, Lucas Nussbaum wrote:
> On 16/03/26 at 19:37 +0100, Fabian Grünbichler wrote:
>> On Mon, Mar 16, 2026, at 8:01 AM, Lucas Nussbaum wrote:
>> > On 16/03/26 at 00:23 +0100, kpcyrd wrote:
>> >> > 330 - failed to guess tag
>> >> 
>> >> It seems it's searching for a git tag in
>> >> https://salsa.debian.org/rust-team/debcargo-conf.git, but this repo only
>> >> contains configuration for the debian-rust tooling.
>> >> 
>> >> https://debaudit.debian.net/git2dsc/result/4317d143808217889eeb13c6c0fa5ea0d6c97aab09bb9f308facc028639b27c8
>> >
>> > The Rust team uses Vcs-Git with sub-dirs. In the above case:
>> > Vcs-Git: https://salsa.debian.org/rust-team/debcargo-conf.git 
>> > [src/ratatui-widgets]
>> > debaudit correctly handles this, see for example
>> >
>> > However the team does not tag releases, so there's no way for debaudit
>> > to reliably find the relevant commit.
>> >
>> > A related case is the Haskell team, that also uses a single repository
>> > with subdirs, but tags releases, so debaudit works:
>> > https://debaudit.debian.net/git2dsc/result/455e8bec15cacd42f5f3e6a66a9c9e98d61f40c7bfd925cb7f2369adc75f3e3c
>> 
>> AFAIR, the haskell team also keeps the full source package in git. we don't,
>> we only track the input for debcargo (including overridden and additional
>> contents of the debian/ dir, if needed). we've discussed a few times whether 
>> it
>> would make sense to keep the full thing in git, also for easier diffing - but
>> it would require extra handling of generated vs. overridden parts, so we 
>> don't
>> for now.
>> 
>> unless/until we do, the only way this would work is if git2dsc would call our
>> ./repackage.sh script with the crate name, which in turn calls debcargo to
>> create an unpacked source package. AFAICT, just adding tags on our end would
>> not be enough.
>
> Oh, I did not know the details about debcargo. It goes much further than
> what I imagined. Very nice.
>
> If the Rust team added tags, I would be happy to extend git2dsc with the above
> workflow (as an additional conditional step before building the source
> package).

I'll take this to the team then, and contact you if/when we implement this. Note
that running debcargo entails talking to crates.io and thus requires network
access.

Fabian

Reply via email to