Public bug reported: ruby-rack version 3.1.12-1 has ruby-rackup in the Recommends section.
ruby-rackup was part of ruby-rack in the past, but in version 3.* it's a separate gem. The problem is that ruby-rack is in main, and ruby-rackup is not. Although we could theoretically MIR the package (as the code is as maintainable as it was when part of the rack package), but there is no reason to. That's because there is a soft-deprecation rule in the ruby-rackup repository upstream, which holds the context about the rack separation and instructs developers to not depend on ruby-rackup: https://github.com/rack/rackup?tab=readme-ov-file#soft-deprecation Also check in the same readme it's stated that ruby-rackup is not intended for production use, which makes it even less appealing to have as a package in main. The sensible solution to this component-mismatch would be changing the Recommends to a Suggests. ** Affects: ruby-rack (Ubuntu) Importance: Undecided Assignee: Renan Rodrigo (renanrodrigo) Status: In Progress ** Changed in: ruby-rack (Ubuntu) Assignee: (unassigned) => Renan Rodrigo (renanrodrigo) ** Changed in: ruby-rack (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/2115364 Title: ruby-rack should suggest ruby-rackup instead of recommend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby-rack/+bug/2115364/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
