Feature #26334
closedUpdate Redmine gems to latest stable versions
0%
Description
Some of the gems required by Redmine are ancient. For example, these are the highest versions available given the gem matching pattern versus the latest version of the package available:
- request_store 1.0.5 (1.3.2);
- roadie-rails 1.1.1 (1.2.1);
- nokogiri 1.7.2 (1.8.0);
- i18n 0.7.0 (0.8.4);
- ffi 1.9.14 (1.9.18);
- net-ldap 0.12.1 (0.16.0);
- ruby-openid 2.3.0 (2.7.0);
- pg 0.18.4 (0.21.0);
- tiny_tds 1.0.5 (1.3.0);
- rdoc 4.3.0 (5.1.0);
- simplecov 0.9.2 (0.14.1);
- test_after_commit 0.4.2 (1.1.0);
- selenium-webdriver 2.53.4 (3.4.3);
Updating these would make Redmine easier to maintain in various package systems. As it stands, we'd have to package these old versions of gems just to have Redmine in the package system. That's not ideal, as it requires double the maintenance for those gems, tracking security vulnerabilities in old versions too, etc.
Updated by Go MAEDA over 7 years ago
- Related to Feature #25538: Drop support for Ruby 2.2.1 and ealier, 2.2.2+ is now required added
Updated by Toshi MARUYAMA over 7 years ago
- Related to deleted (Feature #25538: Drop support for Ruby 2.2.1 and ealier, 2.2.2+ is now required)
Updated by Toshi MARUYAMA over 7 years ago
- Status changed from New to Closed
Reasons of pinning gem version are compatibility for old Ruby and breaking tests.
source:trunk/test
Please create new issue for each gems if you have solution to fix their brokenness.
Updated by Future Link Corporation pkgsrc team over 7 years ago
What is the point of ensuring compatibility with any Ruby version before 2.3? Upstream isn't supporting those versions any more. It's just more work for you guys plus marries this software to museum copies of Ruby packages.
Updated by Toshi MARUYAMA over 7 years ago
Future Link Corporation pkgsrc team wrote:
What is the point of ensuring compatibility with any Ruby version before 2.3?
See #25538.