Bug 2177873 - Please provide perl-Net-Amazon-S3 for EPEL9
Summary: Please provide perl-Net-Amazon-S3 for EPEL9
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-Net-Amazon-S3
Version: epel9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Pisar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 2178059 2178060 2178061 2178063 2178064 2178067 2187283
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-13 18:18 UTC by Jaroslav Pulchart
Modified: 2023-04-27 02:35 UTC (History)
6 users (show)

Fixed In Version: perl-Net-Amazon-S3-0.991-4.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-04-27 02:35:02 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Pulchart 2023-03-13 18:18:31 UTC
Description of problem:
perl-Net-Amazon-S3 package is missing for CentOS Stream 9

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

How reproducible:
try to install perl-Net-Amazon-S3

Steps to Reproduce:
1. dnf install perl-Net-Amazon-S3

Actual results:
package is not found

Expected results:
package is installed with all deps.

Additional info:
n/a

Comment 2 Fedora Update System 2023-04-18 11:07:33 UTC
FEDORA-EPEL-2023-dfaf3ea28f has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-dfaf3ea28f

Comment 3 Fedora Update System 2023-04-19 03:00:50 UTC
FEDORA-EPEL-2023-dfaf3ea28f 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-dfaf3ea28f

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

Comment 4 Fedora Update System 2023-04-27 02:35:02 UTC
FEDORA-EPEL-2023-dfaf3ea28f 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.