Your message dated Sat, 14 Dec 2019 16:27:10 -0800 with message-id <cafhyt57ma_qwtm9a6ckxnfqzz9eonhhz4roagpwxijkhmx5...@mail.gmail.com> and subject line Issue seems resolved has caused the Debian Bug report #817068, regarding Wildcard in overrides no longer appears to work mid-string to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 817068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: lintian Version: 2.5.42 Trying to overrides some source-is-missing false-positives in package rkward, I note that wildcard matching no longer appears to work at start or mid of string. I'm trying to override source is missing for E: rkward source: source-is-missing rkward/plugins/plots/box_plot.js line length is 257 characters (>256) E: rkward source: source-is-missing rkward/plugins/analysis/power/Poweranalysis.js line length is 538 characters (>512) (Note: The heuristics underlying source-is-missing have seen a number of changes, apparently. Other versions have been flagging more .js files in rkward). 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. Regards ThomaspgpoMS03hSERW.pgp
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Hi Thomas, > I see. > > Obviously, I was plain wrong, then, technically. As far as I can tell, your issue was resolved. > That said, I don't think this "line length ..." part is helpful to > users, so I'd be in favor of removing it. I find that information helpful (but do not like the verbosity) because such tags often come together. The additional information helps tell them apart. I have not gotten to that part of Lintian, but it needs improvement. Please file another bug report if needed. > 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." Personally, I think that still refers to one wildcard, but we are working on the documentation. Merge requests are welcome. Closing this bug. Kind regards Felix Lechner
--- End Message ---