On Tue, Nov 22, 2022 at 11:00:57PM +0100, Sebastian Ramacher wrote: > On 2022-11-22 21:53:31 +0100, Paul Gevers wrote: > > Hi Lucas, > > > > On 22-11-2022 17:03, Lucas Kanashiro wrote: > > > After discussing with Antonio, since our deadline to finish the > > > transition is approaching, we decided to already enable ruby3.1 as the > > > default and remove ruby3.0 in a single step. > > > > I may be remembering wrong (it's a bit late), but isn't the change of the > > default a forward rebuild, while removal is a backward rebuild (I mean in > > the dependency tree)? If that's true, I think doing it in two steps is > > easier to manage, as packages can then migrate on their own and don't need a > > lock step migration. > > That's correct. I'd prefer to handle this with two trackers. Fair enough. I will update ruby-defaults accordingly. Is it OK for us to start the transition in unstable?
Attachment:
signature.asc
Description: PGP signature