Bug 2248689

Summary: Logcheck in EPEL9 not installable - missing lockfile-progs
Product: [Fedora] Fedora EPEL Reporter: Roy Bonser <rbonser>
Component: logcheckAssignee: Emmanuel Seyman <emmanuel>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: emmanuel, mrunge
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-21 02:52:29 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:

Description Roy Bonser 2023-11-08 11:55:53 UTC
Description of problem:
Logcheck was just added to EPEL9 but is missing an install dependency.

Version-Release number of selected component (if applicable):
logcheck-1.3.18-15.el9.noarch

How reproducible:
always

Steps to Reproduce:
1. dnf install logcheck

Actual results:
Error: 
 Problem: conflicting requests
  - nothing provides lockfile-progs needed by logcheck-1.3.18-15.el9.noarch

Expected results:
Software installed.

Additional info:

Comment 1 Fedora Update System 2023-11-12 08:31:37 UTC
FEDORA-EPEL-2023-8e3e036af7 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-8e3e036af7

Comment 2 Fedora Update System 2023-11-13 01:13:03 UTC
FEDORA-EPEL-2023-8e3e036af7 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-8e3e036af7

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

Comment 3 Fedora Update System 2023-11-21 02:52:29 UTC
FEDORA-EPEL-2023-8e3e036af7 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.