ruby-defaults stuck on 1:3.0~exp1

[Gunnar Hjalmarsson]

marisa 0.2.6-12 has been autosynced from unstable. It build-depends on ruby >= 1:3.1~ in order to help ruby-defaults migrate on the Debian side, but since ruby-defaults is still 1:3.0~exp1 in Ubuntu, marisa now fails to build here.

Has ruby-defaults not been autosynced from unstable for a reason, or is there a need to take some action?

[Lucas Kanashiro (lucaskanashiro)]

Hi Gunnar,

ruby-defaults is intended to not be synced, this will trigger the ruby3.1 transition and we planned to start that in January:

https://discourse.ubuntu.com/t/lunar-lobster-release-schedule/27284

I've been working on the transition in the Debian side and hopefully it will be done until there, which will make our life easier to finish the transition in Ubuntu.

When the time comes we will be syncing ruby-defaults.

[Gunnar Hjalmarsson (gunnarhj)]

Thanks for the clarification. There is no urgency with marisa, and I suppose we can drop the version specific build-dep on ruby as soon as the ruby3.1 transition has completed in Debian.

[Lucas Kanashiro (lucaskanashiro)]

Yes, once it is done ruby3.1 will be the default.