Hi Jonas, Thank you for your reply!
On 09/02/2025 21:56, Jonas Smedegaard wrote: > Quoting Matthieu Baerts (NGI0) (2025-02-09 19:57:37) >> From: Matthieu Baerts <matt...@kernel.org> >> >> Simply fix the remaining lintian warnings from: >> >> https://udd.debian.org/lintian/?packages=iwd > > I disagree with how lintian parses copyright files. > >> Files: >> - */configure >> + configure > > My intent is to match any file named "configure" at any depth - similar > to the example */Makefile.in at > https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/#files-field Should it not be "*configure" and "*Makefile.in" then? According to the same doc... > Only the wildcards * and ? apply; the former matches any number of > characters (including none), the latter a single character. Both > match slashes (/) and leading dots, unlike shell globs. The pattern > *.in therefore matches any file whose name ends in .in anywhere in > the source tree, not just at the top level. ... it is a bit confusing: when reading this, it sounds like "*/configure" means all the "configure" file from any subdirectories. It should then match "./configure", but maybe it doesn't work like that. >> Files: >> - */Makefile.in >> + Makefile.in > > This is *exactly* the same as the example in the official definition. Is it needed to add something to silent the lintian warnings, or should we just ignore them? > >> - */ylwrap > > This change I agree with - there is indeed no ylwrap file on source. > > I will treat the removal of that one like as solving this bug - because > the alternative of forking the bugreport, closing one part, and keeping > the other open with a wontfix tag feels like too much effort for no real > gain. But please do tell if you prefer my opposition to lintian parsing > be more visible, then I'll do the alternative approach. Fine by me! Note that I'm fine with only the modification you did. I only shared this patch because I saw the warnings. It is OK for me to ignore them. Cheers, Matt
