[Summary]
MIR team NACK - at least until it is clear why we need this dependency.
Required TODOs:
- Please explain why a package defined as "source-level compatibility
library between ruby2.7 and ruby3 ... On ruby3, it does nothing."
is needed to promote a package in a ruby3 environment (lunar)?
I've ran `dpkg --remove --force-depends ruby-ruby2-keywords` and it seemed
to work fine still in a ruby = ruby3 environment.
I think this might be an artifact of past transitions or over-compatibility
and we could get rid of it.
You are more of a ruby expert, could you give it a closer look please?
Just like with ruby-backports I'm stopping the evaluation here, happy to
re-start it once a case has been made why we really would need it.
Review for Package: ruby-ruby2-keywords
[Summary]
MIR team NACK - at least until it is clear why we need this dependency.
Required TODOs: keywords` and it seemed
- Please explain why a package defined as "source-level compatibility
library between ruby2.7 and ruby3 ... On ruby3, it does nothing."
is needed to promote a package in a ruby3 environment (lunar)?
I've ran `dpkg --remove --force-depends ruby-ruby2-
to work fine still in a ruby = ruby3 environment.
I think this might be an artifact of past transitions or over-compatibility
and we could get rid of it.
You are more of a ruby expert, could you give it a closer look please?
Just like with ruby-backports I'm stopping the evaluation here, happy to
re-start it once a case has been made why we really would need it.