The reason pointed in bug 1990572 for avoiding the MIR still apply: - pcs Depends on ruby-json, but also on ruby - ruby-defaults is 3.3 on devel - libruby3.3 Provides ruby-json (just like 3.1 and 3.2 really)
I would say the sensible decision here is to patch pcs, removing ruby-json from the Depends section. This is only risky if libruby stops providing ruby-json in the future for some reason. I'd say it's more benefit than risk, because: - I am not sure if Ruby would stop providing JSON for any reason, but does not seem likely tbh. - Patching pcs should be fine as it already has some small delta. I'm curious on why component-mismatches ignored this Provides. Does it perform this kind of dependency resolving at all? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178274 Title: [MIR] ruby-json To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcs/+bug/1178274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
