Hi,

packages Build-Depending on rustc should most likely emit
Built-Using and Static-Built-Using fields into at least one binary
package.

If these fields are absent or are missing the "rustc" source package,
it would be great if lintian could flag this as an error.

For clarification, both Built-Using and Static-Built-Using should
have the "rustc" source package listed.

Best,
Chris

have s-b-u field.

In case of golang, this is triggered only for arch:any packages - most
of the library packages are arch:all for go.

However, in case of rust, even the -dev packages are arch:any -- is that intended?
(example: librust-rebuilderd-dev, librust-ingredients-dev)

In case of rust-auth-git2, one of the lib packages has s-b-u while the other one
does not. What is the basis of deciding that?

You also say "or are missing rustc source package". I think "Static-Built-Using: ${cargo:Static-Built-Using}"
would auto-populate it, right? In that case isn't checking for the same enough?

Best,
Nilesh