This explanation is great, combined with bug 2095497 (as it has a
different root of dependencies) it explains the current mismatches that
are based on the same source we had.
Here is my short version of Renans good description from my session with him:
- Move from default Gems to bundled Gems, this removal comes from upstream but
also by Debian if they decide to apply it to the rest (those targetted). All
those got converted to proper gems and a preference using the deb-package
instead.
- This allows to have newer/older version of gems than what is in the
interpreter.
- There are more, but they have no dependency to be in main (yet) - the same
would apply to those.
- Most of those existed as individual debs before, but they are still based on
the same codebase.
- It is the new preference to use the debs (bundled) over the default gems
which now makes them pop up.
Due to all of this we are promoting the very same source in a more maintainable
fashion.
This does therefore not need re-review, it is in mismatches - setting the state
accordingly.
** Changed in: ruby3.3 (Ubuntu)
Status: New => Invalid
** Changed in: ruby-test-unit (Ubuntu)
Status: New => In Progress
** Changed in: ruby-power-assert (Ubuntu)
Status: New => In Progress
** Changed in: ruby-minitest (Ubuntu)
Status: New => In Progress
** Changed in: ruby-did-you-mean (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1556608
Title:
[MIR] ruby3.3 dependencies
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-did-you-mean/+bug/1556608/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
