Bug 2307411

Summary: [RFE:EPEL9] EPEL9 branch of pam_script
Product: [Fedora] Fedora EPEL Reporter: Pat Riehecky <riehecky>
Component: pam_scriptAssignee: JT <jtfas90>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel9CC: jtfas90
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pam_script-1.1.9-19.el9 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-11-13 01:55:15 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 Pat Riehecky 2024-08-22 19:45:08 UTC
Description of problem:

Can pam_script be branched for EPEL9

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Fedora Admin user for bugzilla script actions 2025-10-03 14:12:35 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 2 Fedora Update System 2025-11-04 04:13:34 UTC
FEDORA-EPEL-2025-eae4bc643b (pam_script-1.1.9-19.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-eae4bc643b

Comment 3 Fedora Update System 2025-11-05 04:21:36 UTC
FEDORA-EPEL-2025-eae4bc643b 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-eae4bc643b

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

Comment 4 Fedora Update System 2025-11-13 01:55:15 UTC
FEDORA-EPEL-2025-eae4bc643b (pam_script-1.1.9-19.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.