Description of problem: Not packaged for epel8. Version-Release number of selected component (if applicable): Version 1.11.0-4.el7 is provided for epel7, but this is not provided for epel8. Please could this be packaged for epel8 as well?
Hi, we need makeself for VirtualBox build I'm happily can co-maintain this package , my fas user is: sergiomb Thank you.
Sorry I meant xalan-c-devel , but after all xalan-c is not needed anymore to build VirtualBox
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
Please note that since this bug was filed, I've released Xalan-C version 1.12 (https://github.com/apache/xalan-c/releases/tag/Xalan-C_1_12_0). This includes a new CMake build and should be easier to package than with the older build that wasn't using the autotools particularly effectively and was quite fragile and non-standard.
I am the new volunteer maintainer of this package in Fedora. I have packaged the new upstream release 1.12.0. Those interested may already inspect the new spec file in Pagure, and a Koji scratch build for Rawhide is available at https://koji.fedoraproject.org/koji/taskinfo?taskID=56532547. The new package will be built for Rawhide on 2020-12-08. Indeed, the new version is much easier to package! I appreciate it. It looks like it will be straightforward to backport this new package to EPEL8 with only trivial spec file changes, so expect this issue to be resolved in the next few weeks.
FEDORA-EPEL-2020-d875071170 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d875071170
FEDORA-EPEL-2020-d875071170 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-d875071170 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-d875071170 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.