Bug#1031377: UDD/lintian: Needs to run lintian on all binaries generated from same source

2023-09-27 Thread Paul Wise
On Thu, 16 Feb 2023 15:05:24 +0100 Lucas Nussbaum wrote: > What could work is: > run lintian on source > for each arch in the packages's architectures (except all) > run lintian on architecture packages + architecture 'all' packages > > But would that solve all issues? I discovered

Bug#1031377: UDD/lintian: Needs to run lintian on all binaries generated from same source

2023-02-16 Thread Lucas Nussbaum
(Adding lintian-ma...@debian.org to Cc for input) On 16/02/23 at 11:18 +0800, Paul Wise wrote: > On Thu, 2023-02-16 at 01:17 +0100, Guillem Jover wrote: > > > it would need to get the list of binary packages for a source and > > lint all of them with the same lintian call. > > The usual way of

Bug#1031377: UDD/lintian: Needs to run lintian on all binaries generated from same source

2023-02-15 Thread Paul Wise
On Thu, 2023-02-16 at 01:17 +0100, Guillem Jover wrote: > it would need to get the list of binary packages for a source and > lint all of them with the same lintian call. The usual way of running lintian after a build checks all binary packages and the source at the same time. I think UDD should

Bug#1031377: UDD/lintian: Needs to run lintian on all binaries generated from same source

2023-02-15 Thread Guillem Jover
Package: qa.debian.org Severity: normal User: qa.debian@packages.debian.org Usertags: udd Hi! There are some lintian tags (I know at least of lacks-unversioned-link-to-shared-library), which require multiple packages to be linted together for them to be emitted. In this case libfooN and