On Sat 25 Sep 2021 03:32:13 PM EDT, Paul Gevers <elbrus@debian.org> wrote:
Hi Torrance, On 25-09-2021 04:56, Torrance, Douglas wrote:There's a problem though -- this macaulay2 autopkgtest regression is now preventing ntl from migrating to testing! [1] This seems like a chicken and egg situation -- we need it to migrate for the tests to pass, but we need the tests to pass for it to migrate...I must confess that transitions aren't perfectly handled by the migration software (britney) of the release team yet. britney tries to figure which packages should come from unstable and adds them as pinned packages, but hasn't any special notion of transitions.Is there a good solution for this?Not yet.One very hacky idea would be to upload a new macaulay2 package with a very basic autopkgtest that's guaranteed to pass for the time being until everything migrates. Is there a better solution?Yes: * macaulay2 could (temporarily) add *versioned* test dependencies on libsingular4m1 and libflint-2.8.0 (then autopkgtest will do the right thing). * macaulay2 could add *versioned* dependencies on libsingular4m1 and libflint-2.8.0 * I could manually trigger the test with the combination. Let's pick the last option for now and see if it works.
That worked! The autopkgtests were all successful, and ntl has migrated to testing [1] (along with the flint and factory binNMU's). I'll go ahead and close this bug. Thanks for all of your help! Doug [1] https://tracker.debian.org/news/1261285/ntl-1151-1-migrated-to-testing/
Attachment:
signature.asc
Description: PGP signature