Bug 2313915 - zathura-plugins-all: fails to install from epel9
Summary: zathura-plugins-all: fails to install from epel9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: zathura
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Alain V.
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-21 03:27 UTC by Carl George 🎩
Modified: 2025-03-01 02:01 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-03-01 02:01:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Carl George 🎩 2024-09-21 03:27:37 UTC
Description of problem:
zathura-plugins-all from epel9 has an unresolved dependency, causing it to be uninstallable.


Version-Release number of selected component (if applicable):
zathura-plugins-all-0.4.9-1.el9


How reproducible:
always


Steps to Reproduce:
1. dnf install zathura-plugins-all


Actual results:
Error: 
 Problem: conflicting requests
  - nothing provides zathura-ps needed by zathura-plugins-all-0.4.9-1.el9.x86_64 from epel


Expected results:
successful installation

Comment 1 Ankur Sinha (FranciscoD) 2025-02-12 12:33:33 UTC
Looks like zathura-ps has not been branched/built/provided in el9:

https://src.fedoraproject.org/rpms/zathura-ps

Alain, are you looking after the el branches for zathura*? If so, could you please branch for el9 and push a build? (I don't have access to el systems so I don't usually maintain packages for them).

(The alternative is to remove zathura-ps from the plugins-all package)

Comment 2 Alain V. 2025-02-12 14:25:33 UTC
I don't have an EPEL system for testing, but I can maintain those branches as well. I think you too, Ankur (as you are the main admin ?)

zathura-ps has an EPEL9 branch. But it does not build:
The problem is dependency : zathura-ps BR libspectre which is not in EPEL9.

Should I
1. request an EPEL9 branch of libspectre
2. remove zathura-ps from plugin-all, only for EPEL9

I think I'll go 1. first and see how long will it take to progress.
Let me know your thoughts.

Comment 3 Michael J Gruber 2025-02-12 15:28:28 UTC
While this bug is on EPEL 9, it's a good opportunity to think about EPEL 10 and - potentially - requesting EPEL 10 branches along with the EPEL 9 branches while we're at it. Note that there's no automatism EPEL n -> EPEL n+1 like we have with rawhide+branching.

Comment 4 Alain V. 2025-02-13 10:07:25 UTC
libspectre depends on ghostscript which is not on EPEL9/10 !!!
But ghostscript is on ELN. Why not considering ELN directly ?

To summarize, I doubt we will have libspectre for EPEL9 + 10

Also I can mention you are not forced to install zathura-plugins-all, but you can install individual available plugins.
So, if there is a way to conditionally requires zathura-ps, such as 

if zathura-ps exists then Requires: zathura-ps

this could solve the problem...
Thoughts ?

Comment 5 Alain V. 2025-02-13 10:27:22 UTC
Recommends ?
Suggests ?   iso Requires

Comment 6 Michael J Gruber 2025-02-13 13:09:20 UTC
ghostscript is not in EPEL9/10 because it is in RHEL. We can print in RHEL, obviously ;-)

Also - RHEL9:
libspectre.x86_64                 0.2.9-6.el9   @AppStream
libspectre-devel.x86_64         0.2.9-6.el9 codeready-builder-for-rhel-9-x86_64-rpms

CentOS Stream 10:
libspectre.x86_64                            0.2.12-8.el10                      appstream
libspectre-devel.x86_64                      0.2.12-8.el10                      crb  

It is trivial to exclude zathura-ps from zathura-plugins-all on EPEL-9 - since you don't apply release updates there you can just drop it from the spec on that branch.

zathura-ps builds as is on EPEL 9 (from the F37/F36 version):
https://koji.fedoraproject.org/koji/taskinfo?taskID=129201665

The question is more what you as the maintainer prefer.

Comment 7 Alain V. 2025-02-14 15:41:13 UTC
Congrats Michael
You have walked half the way : the build seems successful !
The branch exists (EPEL9). So why not pushing a build, officially ?

Ankur already mentioned he would prefer not to maintain non-Fedora packages (that is my understanding).
Neither I have an EPEL system.

So I could try to officially push a build, blindly, or you do ? (do you have a mean to test the result ?)
Your call...

Regards.
Alain

Comment 8 Michael J Gruber 2025-02-14 18:24:09 UTC
Personally, I don't mind either way. I just wanted to clarify what's possible, and resolving this bug would be nice. I don't use *EL myself but have VMs with RHEL9, COS9, Alma9, Rocky9.

Alain, since you're the zathura main admin and you've built other zathura plugins for EPEL 9 I don't want to push or build something without asking you which solution you prefer. I'd be happy to implement it then.

Comment 9 Michael J Gruber 2025-02-20 21:34:15 UTC
I have tested a scratch build of zathura-ps in RHEL9+EPEL, works fine. So I'm pushing this to the EPEL9 branch since this way it does not affect the main package nor other branches, and it solves this bug in the most functional way.

Comment 10 Fedora Update System 2025-02-20 21:46:13 UTC
FEDORA-EPEL-2025-20afb4794c (zathura-ps-0.2.7-2.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-20afb4794c

Comment 11 Fedora Update System 2025-02-21 03:29:08 UTC
FEDORA-EPEL-2025-20afb4794c 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-2025-20afb4794c

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

Comment 12 Fedora Update System 2025-03-01 02:01:49 UTC
FEDORA-EPEL-2025-20afb4794c (zathura-ps-0.2.7-2.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.