I've looked at this case together with Renan and it is quite an interesting one. The way dependencies and Ruby's management of internal function vs gems work.
Surely we'd want the new version, but we'd also not want to break an unknown amount of dependencies and this is what we might face. Here are the details ruby-json has had deprecated functions for a while. The new does not only move it out (past upgrade in version) of ruby, but also act on modernizing and dropping some deprecated things (newest version). Now comes the special twist, ruby internally still has some json stuff left. And if you do not have ruby-json it will use the code in ruby itself. But if you install the separate ruby-json it will use the new gem instead. This will not break autopkgtest or other things always nor be clear transition, as the old users might just depend on ruby and not yet on ruby-json. This is a tricky problem, it might even happen that it works in isolation - but then something else installs ruby-json and breaks you. This is very risky and not worth the last few days before Feature freeze to upset all and then barely fight an uphill fight towards releases. I'm thereby overruling our usual request for having the latest, please have - The current version in questing - Remove the version from proposed to avoid it migrates automatically by any chance - Get ruby-json updated in 26.04 and there take your time to get all the dependencies happy'ish With that, this request has all it needs - can be promoted and also acted on the removal for the time being. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2115398 Title: [MIR] ruby-json To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-json/+bug/2115398/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
