Bug 2393065 - Please build vokoscreenNG for EPEL 10 and 10.1
Summary: Please build vokoscreenNG for EPEL 10 and 10.1
Keywords:
Status: NEW
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: vokoscreenNG
Version: epel10
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Artem
QA Contact:
URL:
Whiteboard:
Depends On: 2393066 2393748
Blocks: EPEL10Tracker
TreeView+ depends on / blocked
 
Reported: 2025-09-04 07:48 UTC by Robert Scheck
Modified: 2025-09-07 20:21 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Robert Scheck 2025-09-04 07:48:53 UTC
Please branch and build vokoscreenNG in EPEL 10.

Happy to support this as needed (like for EPEL 9 already).

Comment 1 Robert Scheck 2025-09-07 20:21:15 UTC
Artem, @epel-packagers-sig, which you added on my request in bug #2144669, doesn't exist anymore, see https://pagure.io/epel/issue/345 for details.

Could you add me either directly to the package or alternatively branch and build epel10 (leading to .el10_2.(arch).rpm targetting RHEL 10.2) *and* epel10.1 (leading to .el10_1.(arch).rpm targetting RHEL 10.1), please? In any case, please remove @epel-packagers-sig. I am happy to help with EPEL branches (or to care about them, if you aren't interested), if you have some pointer how to handle it with packit correctly.

As of writing, gstreamer1-plugin-gif is missing. The other dependencies are currently satisfied using buildroot overrides in epel10 and epel10.1 until the packages are the stable repository. Please note that for RHEL 10.0 too many dependencies are missing, but RHEL 10.1 should be released either at the end of October or beginning of November, thus not that far away.

By the way, is there any specific reason that e.g. vokoscreenNG-4.6.0 isn't being built anymore for EPEL 9? https://src.fedoraproject.org/rpms/vokoscreenNG/blob/rawhide/f/.packit.yaml mentions EPEL 9. And a manual rebuild worked for me...or did I overlook something?


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