Hi, Thanks for reaching out.
On 05-01-2024 07:45, Johannes Schauer Marin Rodrigues wrote:
It would generate the following two stubs (shortened here for brevity): Package: pkga Version: 1 Architecture: amd64 Depends: pkgc:any Multi-Arch: no Package: pkgb Version: 1 Architecture: amd64 Provides: pkgc Multi-Arch: allowed
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 expectedexpected 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?
Paul[1] https://salsa.debian.org/debian/britney2-tests/-/commit/5ab98de685e15a654227e9b188a48e44857f9d11
OpenPGP_signature.asc
Description: OpenPGP digital signature