Hi Christoph,

On 26/05/26 11:59 pm, Christoph Biedl wrote:
> Source: lintian
> Version: 2.136.1
> Severity: normal
> X-Debbugs-Cc: [email protected]
> 
> file package maintainer here ...
> 
> Dear maintainer,
> 
> the next version 5.47 of the file package is currently in experimental,
> and as I've learned via the pseudo excuses¹, this introduces a regression
> in your (autopkg)test.
> 
> Root cause: Lintian expects a perticular output from file(1) in the
> cruft-wasm test that is no longer given.
> 
> -WebAssembly (wasm) binary module version 0x1 (MVP)
> +WebAssembly (wasm) binary version 0x1 (MVP module)
> 
> If my anaylsis is correct, lib/Lintian/Check/Files/SourceMissing.pm:66
> needs an according update. Please use the version of file in
> experimental to check.

I do not know much about wasm, but from lintian's point of view, both
MVP and components would be considered as generated source, right?

My reading online suggests that one would "generate" component and not
write it by hand.

> The following approach seems sensible to me: Prepare an updated lintian,
> with a versioned dependency on file/libmagic 1:5.47. Then  wait until I
> upload file to unstable, planned for next weekend, then upload the new
> lintian version. Let me know if you need more time or have other ideas
> about this.
This is likely not necessary.

lintian was taking the `\0asm` part from webassembly file output [1]. Which
changed from "WebAssembly (wasm) binary module" to "WebAssembly (wasm) binary"
here [2].

Fortunately, the former is a prefix string of the latter, so all flagged things
earlier should work as-is.

I've fixed this with new file here

https://salsa.debian.org/lintian/lintian/-/merge_requests/736

If you could take a look and give me a go ahead, that'd be great. I'll be happy
to make an upload this weekend, so things go smoothly for you when you upload
file, as lintian would have migrated to testing by then.

[1] https://github.com/file/file/blob/master/magic/Magdir/webassembly#L13
[2] https://github.com/file/file/commit/6b5e54014

Best,
Nilesh

Reply via email to