Bug 2223696

Summary: Please branch and build xarchiver in epel9
Product: [Fedora] Fedora Reporter: Dan Horák <dan>
Component: xarchiverAssignee: Dan Horák <dan>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: mikedep333, ndevos
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: xarchiver-0.5.4.21-1.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-28 02:01:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dan Horák 2023-07-18 14:20:44 UTC
Or add me as an admin to xarchiver and I will take care of that.

Reproducible: Always

Comment 1 Niels de Vos 2023-07-19 08:20:43 UTC
You are now an admin and can branch/build xarchiver for EPEL9.

Thanks for your assistance and contribution!

Comment 2 Fedora Update System 2023-07-19 09:01:06 UTC
FEDORA-EPEL-2023-ac33721b72 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-ac33721b72

Comment 3 Dan Horák 2023-07-19 09:58:07 UTC
(In reply to Niels de Vos from comment #1)
> You are now an admin and can branch/build xarchiver for EPEL9.
> 
> Thanks for your assistance and contribution!

thanks, Niels :-)

Comment 4 Fedora Update System 2023-07-20 05:36:16 UTC
FEDORA-EPEL-2023-ac33721b72 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-ac33721b72

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

Comment 5 Fedora Update System 2023-07-28 02:01:40 UTC
FEDORA-EPEL-2023-ac33721b72 has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.