Bug#917790: lintian: please split wrong-path-for-interpreter into wrong and broken

2018-12-30 Thread Chris Lamb
tags 917790 - moreinfo thanks Hi Ivo, > - interpreters that are not expected to work (I called these 'broken' in my > previous mail) > > Examples of these are > /usr/local/bin/perl > /bin/perl > /usr/bin/bash > - interpreters that work, but are in violation of policy (10.4) > > The most comm

Bug#917790: lintian: please split wrong-path-for-interpreter into wrong and broken

2018-12-30 Thread Ivo De Decker
Hi Chris, On Sun, Dec 30, 2018 at 02:52:46PM +, Chris Lamb wrote: > > Currently wrong-path-for-interpreter lists both paths that are wrong, but > > work > > (like '/usr/bin/env perl') and paths that are wrong, and don't work (like > > '/usr/bin/bash'). > > I'm afraid I can't quite 100% parse

Bug#917790: lintian: please split wrong-path-for-interpreter into wrong and broken

2018-12-30 Thread Chris Lamb
found 917790 2.5.118 tags 917790 + moreinfo thanks Hi, > Currently wrong-path-for-interpreter lists both paths that are wrong, but work > (like '/usr/bin/env perl') and paths that are wrong, and don't work (like > '/usr/bin/bash'). I'm afraid I can't quite 100% parse what you mean here; work/don

Bug#917790: lintian: please split wrong-path-for-interpreter into wrong and broken

2018-12-30 Thread Ivo De Decker
package: lintian Hi, Currently wrong-path-for-interpreter lists both paths that are wrong, but work (like '/usr/bin/env perl') and paths that are wrong, and don't work (like '/usr/bin/bash'). This last type is common for packages that are built in a merged usr environment, but these will not work