Quoting Paul Gevers (2024-01-05 20:15:22) > Thanks for reaching out. Thank Helmut for poking me in #debian-apt :) > For britney2, the Sources stanza would also be needed; then we could use this > to generate britney2 testcases. I created 10 of those yesterday by hand [1]. > > The simplest for of tests is a tree with > var/data/unstable/Sources > # i386 is the default archive of the testsuite, which can be overruled > # if that makes sense > var/data/unstable/Packages_i386 > var/data/testing/Sources (may be empty) > var/data/testing/Packages_i386 > expected > > expected is in Heidi format (if I understand correctly) of what britney2 > will allow to be in testing after the run, it will only migrate packages > that are installable. > > Would it make sense to you to generate a branch in that archive with a bunch > of tests that you know the answer too? I think it's a bit more complicated than that. Currently, the tool creates 8624 package relationships. If I remember correctly, britney is unable to analyze cross-architecture relationships? In that case that number goes down to 2352. One could reduce that number even further and only check those cases where apt, dpkg and dose3 agree on a solution but that would then rather be a documentation of the status quo than a list of the intended ground truth. Maybe it would make sense to analyze the archive and only add those cases that currently exist as real package relationships? What the tool never received since its inception was somebody to look over these cases and write down what the ground-truth actually is supposed to look like. For the britney tests you likely want some kind of ground-truth and I fear that tool can give you the status quo but not necessarily the truth as intended by the spec. If that is fine for you, do you still want to add thousands of test-cases? Or do you want to hand-pick them? Thanks! cheers, josch
Attachment:
signature.asc
Description: signature