Simon and Manuel, I see that you have both been doing work on ruby-commonmarker. The current version in Debian is 0.23.10, which is a legacy branch. The current upstream version is 2.6.3 which involves a lot of breaking changes.
There are two packages in Debian that depend on ruby-commonmarker: redmine and ruby-jekyll-commonmark. The current version of redmine requires commonmarker ~> 2.3.0. https://salsa.debian.org/ruby-team/redmine/-/blob/debian/latest/Gemfile? ref_type=heads#L21 There does not appear to be significant differences between commonmarker 2.3.0 and 2.6.3, so I think we are probably safe to use the latest upstream. https://github.com/gjtorikian/commonmarker/releases Doing so will break ruby-jekyll-commonmark, which depends on commonmarker -> 0.23.4. https://github.com/jekyll/jekyll-commonmark/blob/master/jekyll-commonmark.gemspec#L19 There is an open upstream issue to support commonmarker 2.x, but so far there has been no response. https://github.com/jekyll/jekyll-commonmark/issues/61 ruby-jekyll-commonmark has low popcon installs. https://qa.debian.org/popcon.php?package=ruby-jekyll-commonmark I try to avoid doing updates that break software. However, in this case, I propose we update ruby-commonmarker to fix redmine and the three transitions it is blocking. I have included Daniel, the Uploader of ruby-jekyll-commonmark, to get his feedback. -- Soren Stoutner [email protected]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Pkg-ruby-extras-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
