Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Scott Kitterman
On Sat, 28 Jul 2018 14:16:11 +0100 Chris Lamb wrote: > Hi Stuart, > > > In the upload of translate-toolkit 2.3.0-3, I ended up with the following: > > > > Depends: python3, python3-pkg-resources, python3-six, python3-translate, > > python3:any, python:any > > > > such that the package

Jenkins build is back to normal : lintian-tests_sid #3098

2018-07-28 Thread jenkins
See

G

2018-07-28 Thread William Wightman
Sent from my iPhone

Bug#904852: lintian: package-contains-documentation-outside-usr-share-doc far too overzealous

2018-07-28 Thread Chris Lamb
Hi Axel, > the phrase "Please move this files to /usr/share/doc/ or remove it." > sounds very final, but completely ignores that there are quite a lot of > files (often named README or so) documenting the purpose or contents of > the directory they're in. I agree. Bastian, you added this in

Bug#904852: lintian: package-contains-documentation-outside-usr-share-doc far too overzealous

2018-07-28 Thread Axel Beckert
Package: lintian Version: 2.5.94 Severity: normal Hi, the phrase "Please move this files to /usr/share/doc/ or remove it." sounds very final, but completely ignores that there are quite a lot of files (often named README or so) documenting the purpose or contents of the directory they're in.

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Stuart Prescott
On Saturday, 28 July 2018 15:58:55 AEST Chris Lamb wrote: > Hi Stuart, > > > > This won't trigger for packages unless they are called / > > > ^python([23]?)-/ however > > […] > > > Only module packages are called python{,3}-foo, while applications > > packages do not have the binary prefix > >

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Chris Lamb
Hi Stuart, > > This won't trigger for packages unless they are called / > > ^python([23]?)-/ however […] > Only module packages are called python{,3}-foo, while applications packages > do > not have the binary prefix Right, exactly; would your package have triggered this error *if* the

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Stuart Prescott
Hi Chris, > https://lintian.debian.org/tags/python-package-depends-on-package-from-othe > r-python-variant.html > > This won't trigger for packages unless they are called / > ^python([23]?)-/ however. Indeed, this seems to be required so we > "know" that a package is a "2" or a "3". > > Would

Build failed in Jenkins: lintian-tests_sid #3097

2018-07-28 Thread jenkins
See -- Started by GitLab push by Paul Wise [EnvInject] - Loading node environment variables. Building on master in workspace

Build failed in Jenkins: lintian-tests_sid #3096

2018-07-28 Thread jenkins
See -- Started by GitLab push by Paul Wise [EnvInject] - Loading node environment variables. Building on master in workspace

Build failed in Jenkins: lintian-tests_sid #3095

2018-07-28 Thread jenkins
See -- Started by GitLab push by Paul Wise [EnvInject] - Loading node environment variables. Building on master in workspace

Build failed in Jenkins: lintian-tests_sid #3093

2018-07-28 Thread jenkins
See -- Started by GitLab push by Paul Wise [EnvInject] - Loading node environment variables. Building on master in workspace

Build failed in Jenkins: lintian-tests_sid #3094

2018-07-28 Thread jenkins
See -- Started by GitLab push by Paul Wise [EnvInject] - Loading node environment variables. Building on master in workspace

Build failed in Jenkins: lintian-tests_sid #3092

2018-07-28 Thread jenkins
See -- Started by GitLab push by Paul Wise [EnvInject] - Loading node environment variables. Building on master in workspace

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Chris Lamb
Hi Stuart, > In the upload of translate-toolkit 2.3.0-3, I ended up with the following: > > Depends: python3, python3-pkg-resources, python3-six, python3-translate, > python3:any, python:any > > such that the package depended on both the Python 2 and Python 3 interpreters. Thinking about it,

Bug#904817: lintian: Warn that depending on both Python 2 and Python 3 interpreters is unusual, likely a mistake?

2018-07-28 Thread Stuart Prescott
Package: lintian Version: 2.5.94 Severity: wishlist Dear Maintainer, In the upload of translate-toolkit 2.3.0-3, I ended up with the following: Depends: python3, python3-pkg-resources, python3-six, python3-translate, python3:any, python:any such that the package depended on both the Python 2