[DRE-maint] Proposal to update ruby-commonmarker from 0.23.10 to 2.6.3

Simon Quigley simon at tsimonq2.net
Mon Feb 23 23:06:08 GMT 2026


Hi all,

I cherry-picked two of those commits, but I can't seem to get any further. It involves removing the rb-allocator crate, after that it's a longer stacktrace I'd have to spend more time on.

My changes are pushed to debian/latest, feel free to fix further.

Thanks,
Simon

On February 23, 2026 4:16:46 PM CST, Manuel Guerra <ar.manuelguerra at gmail.com> wrote:
>Hi Simon,
>
>Please, do what you need :D
>
>I have no problem, do a merge if this is good for the package.
>
>Regards,
>
>El lun, 23 de feb. de 2026 18:14, Simon Quigley <simon at tsimonq2.net>
>escribió:
>
>> Hi Manuel,
>>
>> We can work together. :)
>>
>> Your change to use packaged dependencies looks like exactly what we need
>> to solve the CI failure. Would you like to merge that on to debian/latest,
>> or would you like me to proceed?
>>
>> Thanks for your work,
>> Simon
>>
>>
>> On February 23, 2026 4:07:13 PM CST, Manuel Guerra <
>> ar.manuelguerra at gmail.com> wrote:
>>
>>> If Simon proceeds with the package update, he can disregard my changes to
>>> the debian/upstream branch.
>>>
>>> Regards,
>>>
>>> El lun, 23 de feb. de 2026 17:54, Simon Quigley <simon at tsimonq2.net>
>>> escribió:
>>>
>>>> Hi Soren, all,
>>>>
>>>> This sounds good to me. I have 2.6.3 staged in Salsa, please let me know
>>>> if I should upload that or hold off for now.
>>>>
>>>> Thanks for looking into this! Let me know if I can help further.
>>>>
>>>> Thanks,
>>>> Simon Quigley
>>>> tsimonq2 at debian.org
>>>>
>>>>
>>>> On February 23, 2026 3:11:27 PM CST, Soren Stoutner <soren at debian.org>
>>>> wrote:
>>>>
>>>>> 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.
>>>>>
>>>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20260223/76ef4cea/attachment-0001.htm>


More information about the Pkg-ruby-extras-maintainers mailing list