Hi Felix, On 31/10/2019 18.54, Felix Lechner wrote: > Please have a look at coreutils >= 8.30:> It could also be related to > libberkeleydb-perl and libmldbm-perl, but
Thanks for the pointers, but it's none of these. So I've started bisecting between 2.29.0 and 2.30.0 ... In case you have some hints for "speeding up" bisecting lintian, you could add them to some readme. Right now I'm working in a minimal stretch+backports chroot with B-D installed, doing a (parallel) 'debian/rules binary' for each step, waiting for test failures. There is a dubious failure in stretch in 2.29.0 (and later "good" versions) (I verified that it does not happen in sid): ===( 336;658 1/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1 0/1 0... )===# Failed test 'Lintian passes for debconf-config-not-executable' # at /build/lintian-2.29.0/lib/Test/Lintian/Run.pm line 300. # Tags do not match # # --- debian/test-out/tags/checks/debian/debconf/debconf-config-not-executable/tags.specified.calibrated # +++ debian/test-out/tags/checks/debian/debconf/debconf-config-not-executable/tags.actual.parsed # -debconf-config-not-executable (binary): control-file-has-bad-permissions config 0644 != 0755 # # Looks like you failed 1 test of 1. debian/test-out/tags/checks/debian/debconf/debconf-config-not-executable/generic.t .................................... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests Bisecting ended with There are only 'skip'ped commits left to test. The first bad commit could be any of: 53002feb5b944681a17109b704fdcb10f1032c84 ba56dcca2932913945346ebf56e428801970e3e1 5b3f9904ee4f2aa128c65f7b407be14827f06c9c fb7c61656fd6a5ba5f4449a005a3d8884b4be886 713e9ac5e159d7011239e78a025747a80cdaf54b 8e4e87e93958ee75a707be0e97de3af6dcf8e859 a6d28ec18b0968728aab07490a04384ea78f0a25 We cannot bisect more! which is a bunch of commits doing a larger reorganization. Does the new Lintian::Processable::Pool have new insufficiently versioned external dependencies? Or does it require newer perl? Andreas
