Bug 2122247 - Upgrade perl-Exporter-Tiny to 1.004000
Summary: Upgrade perl-Exporter-Tiny to 1.004000
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Exporter-Tiny
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL: https://metacpan.org/release/Exporter...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-29 15:21 UTC by Jitka Plesnikova
Modified: 2022-09-12 17:42 UTC (History)
2 users (show)

Fixed In Version: perl-Exporter-Tiny-1.004000-1.fc37 perl-Exporter-Tiny-1.004000-1.fc38
Clone Of:
Environment:
Last Closed: 2022-09-12 17:42:45 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jitka Plesnikova 2022-08-29 15:21:10 UTC 
Latest Fedora delivers 1.002002 version. Upstream released 1.004000. When you have free time, please upgrade it.
Comment 1 Paul Howarth 2022-08-30 09:59:28 UTC 
f37: https://koji.fedoraproject.org/koji/taskinfo?taskID=91431330
f38: https://koji.fedoraproject.org/koji/taskinfo?taskID=91431041
Comment 2 Fedora Update System 2022-08-30 10:00:27 UTC 
FEDORA-2022-a0d6a604de has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a0d6a604de
Comment 3 Fedora Update System 2022-08-31 02:21:35 UTC 
FEDORA-2022-a0d6a604de has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-a0d6a604de`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a0d6a604de

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 4 Fedora Update System 2022-09-12 17:42:45 UTC 
FEDORA-2022-a0d6a604de has been pushed to the Fedora 37 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.