On Wed, 15 Jan 2020 18:23:20 +0100, Dominique Dumont wrote: > Looks I've managed to block the migration of some libconfig-model-perl packages > to testing.. > > Step 1. > > In libconfig-model-perl 2.138, I've (tried to) improve some warning messages. > These messages are tested in libconfig-model-tkui-perl. Which means that old > libconfig-model-itself-perl (in testing) fails with new libconfig-model-perl > 2.138 > > Step 2 > > So I've fixed these tests in libconfig-model-itself-perl 1.371, which build > depends on libconfig-model-perl 2.138 (because the warnings messages have > changed) > > Step 3 > > autopkgtest blocks migration of new libconfig-model-perl because the tests of > old libconfig-model-tkui-perl are broken with new libconfig-model-perl > > Step 4 > > migration of new libconfig-model-tkui-perl is blocked because its build > dependencies cannot migrate to testing. > > Note that libconfig-model-itself-perl is also blocked for the same reason. Hrm, interesting situation :) The "logical" solution would be that they migrate together but apparently britney+ci.d.n. don't consider this option. Which, if I'm not mistaken, might be a hint to a missing dependency or more probably a missing Breaks. Maybe adding a Breaks to libconfig-model-perl on libconfig-model-tkui-perl << 1.371 and libconfig-model-itself-perl << 2.019 would help? But before I dive too much into guesswork, let's add elbrus to the CC as the domain expert :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- NP: Joan Baez: Rivers
Attachment:
signature.asc
Description: Digital Signature