This is perhaps more of a "recommended best practice" request than a
transition request.

gromacs has an upcoming library transition, staged in experimental, and
its next upload to sid will close one RC bug [1].  However, its only
direct build-dependency in testing is votca-csg, which has a pending RM
request [2].  votca-csg *can* be binNMUed against gromacs 2022.1, but
that's not terribly useful when it's about to be replaced.

Additionally, gromacs upstream dropped support for 32-bit architectures
in the new release, so that will need an additional RM bug for old
binaries, not yet filed.

Should I proceed with an upload to sid when a slot is ready, or wait for
one or both of those removals to clear first?

Thanks.

Control: tags -1 confirmed

gromacs is not colliding with any other planned or ongoing transitions
and with votca-csg being removed, you can just go ahead with this one.
The removal of gromacs on the 32 bit architectures will be the blocker
for gromoacs' migration to testing -- without the removal, gromacs won't
be able to migrate.

So, I'd suggest to go ahead with the gromacs upload to unstable whenever
you're ready and to immediately file the RM bug for the 32 bit binaries.

The removal of votca-csg from testing can happen independently from
unstable. If by the time gromacs is ready to migrate to testing
votca-csg hasn't been removed from unstable, we can place a manual
removal hint to get it removed from testing.

Cheers

Migration complete, closing out the transition bug.