Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2215030

Summary: Request to add rubygem-asciidoctor into CRB
Product: Red Hat Enterprise Linux 9 Reporter: Marián Konček <mkoncek>
Component: rubygem-asciidoctorAssignee: ruby maint <ruby-maint>
Status: CLOSED WONTFIX QA Contact: RHEL CS Apps Subsystem QE <rhel-cs-apps-subsystem-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, dhodovsk, jskarvad, jwboyer
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-24 13:02:42 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:

Description Marián Konček 2023-06-14 14:11:04 UTC
Description of problem:
rubygem-asciidoctor is a vital package to build documentation. I would like to have it in the CRB repository at least in c9s. We use it to test documentation generation in our CI. I know it is present in the buildroot but I want to to be easily installable in the centos:stream9 container.

See for example: https://github.com/fedora-java/jurand/blob/67fb975a85cce7aa209c0490dfff1418d5db82c1/.github/workflows/ci.yaml#L26
which requires modifying the configs.

Comment 1 Vít Ondruch 2023-06-15 08:25:45 UTC
I don't object this proposal in general. Nevertheless:

1) we should make sure the RHEL package version is aligned with Fedora. Specifically, the RHEL package makes sure the test suite is enabled:

https://gitlab.com/redhat/centos-stream/rpms/rubygem-asciidoctor/-/commit/d02280e27c7fa37a92c4b3b501246ce2a7895510

where the similar change was not accepted into Fedora yet:

https://src.fedoraproject.org/rpms/rubygem-asciidoctor/pull-request/6

and that in turn would mean troubles for RHEL10.

2) rubygem-asciidoctor is available in EPEL. We would need to drop the package from there. And I think the whole idea was to have the Asciidoctor available, but not block community from innovating by (possibly) keeping the Asciidoctor without updates.

Comment 2 Jaroslav Škarvada 2023-07-11 10:21:43 UTC
+1

Comment 3 Jaroslav Škarvada 2023-07-11 10:22:56 UTC
Or build root would be also OK for us.

Comment 4 Jaroslav Škarvada 2023-07-11 10:30:23 UTC
(In reply to Jaroslav Škarvada from comment #3)
> Or build root would be also OK for us.

Yep, it seems it's already in the RHEL-9 buildroot, so we (TuneD maintainers) are happy :)

Comment 5 Marián Konček 2023-07-24 13:02:42 UTC
I think the package being present in EPEL / buildroot is acceptable.