Bug 2126698

Summary: [Package Request]Please add mupdf to EPEL
Product: [Fedora] Fedora Reporter: galoyad325
Component: mupdfAssignee: Michael J Gruber <mjg>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: lizhenbo, mjg
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: mupdf-1.21.1-3.el9.next mupdf-1.21.1-5.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-01 03:12:51 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: 2121499    
Bug Blocks:    

Description galoyad325 2022-09-14 09:41:19 UTC
Please branch and build mupdf in EPEL 9. This means the mupdf-gl viewer as well as mupdf-tools.

Comment 1 Michael J Gruber 2022-09-14 13:51:49 UTC
We need the dependencies in RHEL/CRB/EPEL first. jbig2dec-devel is on its way already. I have to check the others. Until then there is always:

https://copr.fedorainfracloud.org/coprs/mjg/mupdf-zathura-EPEL/

Everything in there are direct rebuilds of current Fedora rawhide packages.

Note that mupdf might not be a good match for a slow moving distro like *EL. We will either have to bend the guidelines or not care too much about bugs since upstream does not work with release-hotfix branches, and backporting amounts to quite some work. In that sense, every mupdf release is a bugfix release (as well).

Comment 2 Michael J Gruber 2022-09-14 15:22:41 UTC
So, I think everything else will be in place eventually.

Note that jbig2dec-devel will be provided by RedHat (specifically in CRB). It just missed the cut for RHEL 9.1 (which I expect in October), so it will make it into CRB for RHEL 9.2 only (May 2023). Unless I misunderstand the various connections (which is quite probable), this means that jbig2dec-devel should arrive in CentOS stream after the release of RHEL 9.1, and I should be able to build mupdf in EPEL-9-next then, and in EPEL-9 after the release of RHEL 9.2.

Somewhat disappointing to wait for that long for a missing devel subpackage to an existing library subpackage, but that's how it is. At least we're moving!

Comment 3 Ben Cotton 2023-02-07 15:10:27 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 38 development cycle.
Changing version to 38.

Comment 4 Fedora Update System 2023-02-20 16:58:20 UTC
FEDORA-EPEL-NEXT-2023-f35e71ff55 has been submitted as an update to Fedora EPEL 9 Next. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2023-f35e71ff55

Comment 5 Fedora Update System 2023-02-21 02:29:29 UTC
FEDORA-EPEL-NEXT-2023-f35e71ff55 has been pushed to the Fedora EPEL 9 Next testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-NEXT-2023-f35e71ff55

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2023-03-01 03:12:51 UTC
FEDORA-EPEL-NEXT-2023-f35e71ff55 has been pushed to the Fedora EPEL 9 Next stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2023-05-10 12:12:06 UTC
FEDORA-EPEL-2023-a59bb927bc has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-a59bb927bc

Comment 8 Fedora Update System 2023-05-11 02:17:45 UTC
FEDORA-EPEL-2023-a59bb927bc has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-a59bb927bc

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2023-05-19 00:44:34 UTC
FEDORA-EPEL-2023-a59bb927bc has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.