Bug#1031377: UDD/lintian: Needs to run lintian on all binaries generated from same source
(Adding lintian-maint@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 running lintian after a build checks all binary
> packages and the source at the same time. I think UDD should do that.
That's not very convenient because UDD/lintian runs lintian for each
architecture, and lintian's output does not include the architecture for
binary packages, so I just get something like:
C: libbsd0: control-tarball-compression-format xz
C: libbsd0: control-tarball-compression-format xz
C: libbsd0: control-tarball-compression-format xz
C: libbsd0: control-tarball-compression-format xz
C: libbsd0: control-tarball-compression-format xz
C: libbsd0: control-tarball-compression-format xz
C: libbsd0: control-tarball-compression-format xz
C: libbsd0: control-tarball-compression-format xz
C: libbsd0: control-tarball-compression-format xz
with no way of linking emmitted tags to a specific architecture...
What I could do is:
for each arch in the packages's architectures (except all)
run lintian on source + architecture packages + architecture 'all' packages
... but that would result in a much longer runtime...
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?
The best way out is probably to have lintian optionally suffix packages
names with architecture, and then do a single lintian run with all
binaries for all architectures...
Lucas
Reply to: