Hi Niko On 03-06-2020 18:55, Niko Tyni wrote: >> As recently announced [1], the Release Team now considers packages that >> are out-of-sync between testing and unstable for more than 60 days as >> having a Release Critical bug in testing. Your package >> src:libcatmandu-perl in unstable has been trying to migrate for 60 days >> [2]. Hence, I am filing this bug. > > So if I read this correctly, libcatmandu-perl cannot migrate because it > breaks the test suite of libcatmandu-sru-perl in testing. The version of > libcatmandu-sru-perl in unstable fixes this, but cannot migrate because > it has a versioned dependency on libcatmandu-perl that is only satisfied > in unstable.
Aha, that's unfortunate than. Normally this would mean that the test run of libcatmandu-sru-perl for itself already yielded a good result for libcatmandu-perl, but because the latter was updated, no such thing happened. In such a case, britney doesn't solve it by itself. > I believe the preferred way to get these to migrate together is to declare > that libcatmandu-perl Breaks the older libcatmandu-sru-perl versions. Or a reupload of libcatmandu-sru-perl would also solve it I believe. > Alternatively, just waiting it out will probably work too: once testing > removal happens, the newer packages can migrate on their own. This would be a bad solution as ... > However, > if the test suite breakage is not just a technicality, the missing > Breaks makes it possible for users to partially upgrade their systems > to a broken combination. This is the interesting question. Is there something broken in the combination that we're testing? If so, I would prefer the Breaks. > Paul, please correct me if I'm mistaken above :) If it's *only* the test that's broken, I can manually trigger the right test. Paul
signature.asc
Description: OpenPGP digital signature
