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.
Description of problem:
asciidoctor is used by a number of packages for building documentation (like man pages) in Fedora (a notable example being ntpsec). Please ship rubygem-asciidoctor in CRB so we can use it in EPEL.
(In reply to Vít Ondruch from comment #2)
> Hi Neal,
>
> Is there any reason to not have rubygem-asciidoctor in EPEL?
I guess not? It builds in my local EPEL-ish environment, would you be willing to add it to EPEL9 once it's available?
(In reply to Neal Gompa from comment #3)
> (In reply to Vít Ondruch from comment #2)
> > Hi Neal,
> >
> > Is there any reason to not have rubygem-asciidoctor in EPEL?
>
> I guess not? It builds in my local EPEL-ish environment, would you be
> willing to add it to EPEL9 once it's available?
I would leave it to community. I am not Fedora asciidoctor maintainer anyway.
(In reply to Vít Ondruch from comment #4)
> (In reply to Neal Gompa from comment #3)
> > (In reply to Vít Ondruch from comment #2)
> > > Hi Neal,
> > >
> > > Is there any reason to not have rubygem-asciidoctor in EPEL?
> >
> > I guess not? It builds in my local EPEL-ish environment, would you be
> > willing to add it to EPEL9 once it's available?
>
> I would leave it to community. I am not Fedora asciidoctor maintainer anyway.
Ah, it's maintained in Fedora by the upstream developer. I'll ask there, then.