Bug#801760: [checks/manpages] manpage-named-after-build-path won't trigger for packages built in sbuild

* Mattia Rizzolo , 2015-10-14, 17:28: I wonder if just using $file =~ m/_build_/ instaead of $file =~ m/_build_buildd/ is sane enough. There are legitimate manpages that have "_build_" in their name, for example: /usr/share/man/man1/slonik_build_env.1.gz (in

Bug#801760: [checks/manpages] manpage-named-after-build-path won't trigger for packages built in sbuild

Package: lintian Version: 2.5.38 This code was meant to catch bugs like #713883: if ($file =~ m/_build_buildd/ or $file =~ /_tmp_buildd/) { tag 'manpage-named-after-build-path', $file; } But sbuild builds stuff in /build/$PACKAGE-$RANDOMSTRING, so this regexp wouldn't

Bug#801760: [checks/manpages] manpage-named-after-build-path won't trigger for packages built in sbuild

On Wed, Oct 14, 2015 at 12:30:27PM +0200, Jakub Wilk wrote: > Package: lintian > Version: 2.5.38 > > This code was meant to catch bugs like #713883: > >if ($file =~ m/_build_buildd/ or $file =~ /_tmp_buildd/) { >tag 'manpage-named-after-build-path', $file; >} > > But