[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: cargo-auditable and Debian



On 24/08/25 15:50, kpcyrd wrote:
On 8/23/25 4:39 PM, NoisyCoil wrote:
As for complementing dh-cargo-built-using, this seems a nice added touch which we maybe don't exactly need (again, we already track metadata in a more efficient way for the purposes of Debian -- just run `apt info` on any rust package, installed or not), but which I would fully support if the ecosystem converges towards using cargo- auditable.

I'm not sure the `apt info` approach scales. I'm currently faced with this problem:

E: rebuilderd: field-too-long Static-Built-Using (5126 chars > 5000)
E: Lintian run failed (policy violation)

Not sure what to do now.

cheers,
kpcyrd

As far as I know, this is already fixed in lintian [1]. But even if it wasn't, what do you mean by "it doesn't scale"? Btw, that's a non-release-critical error, it can be both overridden [2] or ignored [3], and the field will still show up in `apt info`.


[1] https://salsa.debian.org/lintian/lintian/-/commit/f8d3f94da69d810336e0ee81c1ca0b6f38c38d33

[2] https://salsa.debian.org/rust-team/debcargo-conf/-/blob/5a113d100a07fbe2b8793f191054abc2470b9cf4/src/broot/debian/broot.lintian-overrides

[3] https://udd.debian.org/lintian-tag/field-too-long?affected=yes


Reply to: