Bug#913099: lintian: autopkgtests fail on !(amd64)

2018-11-08 Thread Chris Lamb
tags 913099 + pending
thanks

Merged https://salsa.debian.org/lintian/lintian/merge_requests/71
into Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/4326d7d416d482bbda7ae550097b2e2ac297d416

  debian/changelog  | 2 ++
  t/tests/binaries-missing-lfs/debian/debian/compat | 1 +
  t/tests/binaries-missing-lfs/desc | 4 +++-
  t/tests/binaries-missing-lfs/tags | 1 +
  t/tests/shared-libs-non-pic-i386/debian/debian/compat | 1 +
  t/tests/shared-libs-non-pic-i386/desc | 4 +++-
  t/tests/shared-libs-non-pic-i386/tags | 1 +
  7 files changed, 12 insertions(+), 2 deletions(-)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-



Bug#913099: lintian: autopkgtests fail on !(amd64)

2018-11-07 Thread Adam Conrad
I looked into the failure mentioned in this bug (as well as two other
failures on !amd64), and committed the following patch in Ubuntu, which
solves all outstanding issues and gets autopkgtests passing on all six
of our architectures again:

http://launchpadlibrarian.net/396411616/lintian_2.5.111ubuntu1_2.5.111ubuntu2.diff.gz

The changelog explains which upstream commits regressed these three
tests, and the fixes should be fairly obvious using those commits as
references.

I will note that this doesn't fix files-multiarch-foreign-files to work
on other arches, it just restricts it to amd64, but that's the state it
was in before debian bug #886163 was regressed.  I suspect it would be
more "correct" to figure out why that test doesn't pass on other arches
as it might mean the check also doesn't work on other arches, but for
now, it seemed that reverting to the pre-regression behaviour was the
path of least resistance.

... Adam