Bug 1749749

Summary: kramdown version 2.1.0 is available
Product: [Fedora] Fedora Reporter: Fabio Valentini <decathorpe>
Component: rubygem-kramdownAssignee: Mamoru TASAKA <mtasaka>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: ktdreyer, mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-kramdown-2.1.0-1.fc32 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-11 10:06:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1743745, 1749751, 1749755    

Description Fabio Valentini 2019-09-06 11:16:14 UTC
see summary.

Jekyll 4 requires version >= 2.1.0 of kramdown.

Comment 1 Fabio Valentini 2019-09-06 11:16:34 UTC
WIP Pull Request: https://src.fedoraproject.org/rpms/rubygem-kramdown/pull-request/2

Comment 2 Fabio Valentini 2019-09-06 11:18:17 UTC
It also requires rubygem-stringex for the test suite, for which there exists an open Review Request:
https://bugzilla.redhat.com/show_bug.cgi?id=1748929

Comment 3 Mamoru TASAKA 2019-09-11 10:06:53 UTC
For now, I just killed tests requiring stringex because review request for rubygem-stringex may take long time (because it is unclear which review request to be reviewed), and pushed kramdown 2.1.0 into F-32 (for now F-32 only).

Comment 4 Fabio Valentini 2019-09-11 12:10:17 UTC
Great, thanks!

Though I don't quite understand why my review request for stringex was closed in favor of one that had been stalled for four years ...

Comment 5 Mamoru TASAKA 2019-09-11 13:05:17 UTC
Well, actually it is difficult when dealing with preceeding long-open review request - the submitter _may_ be still waiting for review, so the rule is perhaps 

- firstly asking the first submitter if he/she is still waiting for review
- ask for 2 or 3 times repeatedly
- if the first submitter fails to response, then close the first review requst as NOTABUG or WONTFIX

... but well, this procedure usually takes a month