Hi, thanks for the swift reply! On Mon, 7 Mar 2016 21:53:04 +0100 Jakub Wilk <jwilk@debian.org> wrote: > Hi Thomas! > > * Thomas Friedrichsmeier <thomas.friedrichsmeier@ruhr-uni-bochum.de>, > 2016-03-07, 21:07: [...] > >I would expect the following three override variants to all do the > >trick, but only variant 3 overrides, successfully: > > > >1) > >rkward source: source-is-missing *.js > >2) > >rkward source: source-is-missing rkward/plugins/*.js > >3) > >rkward source: source-is-missing rkward/plugins/* > > > >Variant 2 used to work with some earlier version of lintian, current > >around December 2015. I never used Variant 1 except for testing. > > The tag info doesn't end with ".js", but with "line length is $X > characters (>$Y)"; so it's not surprising that the first two variants > don't work. I see. (But I had been interpreting the "line length" part as an additional comment, not actually part of the description.) Obviously, I was plain wrong, then, technically. But two more remarks: > That said, I don't think this "line length ..." part is helpful to > users, so I'd be in favor of removing it. Yes, and no. It did get me off-track (and probably it's the reason why Variant 2 used to work, one day), but it clearly does help understand _why_ lintian believes the source is missing. Suggest adding something similar to the extended description, then (if feasible). Also, same problem for source-contains-prebuilt-javascript-object . Niels Thykier wrote: > An alternative override that should work: > > source-is-missing *.js line length is * characters (>256) Lintian user's manual might point out the fact that more than one wildcard can be used. Or perhaps I simply got derailed by the archeological tid-bit "The first wildcard support appeared in Lintian 2.0.0, which only allowed the wildcards in the very beginning or end. Version 2.5.0~rc4 extended this to allow wildcards any where in the additional info." Regards Thomas
Attachment:
pgpEU17bNQH13.pgp
Description: OpenPGP digital signature