Bug 1917554 - Upgrade perl-POE-Component-Client-Ping to 1.176
Summary: Upgrade perl-POE-Component-Client-Ping to 1.176
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-POE-Component-Client-Ping
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: marianne@tuxette.fr
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-18 17:53 UTC by Jitka Plesnikova
Modified: 2021-02-10 01:18 UTC (History)
2 users (show)

Fixed In Version: perl-POE-Component-Client-Ping-1.176-1.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-10 01:18:53 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jitka Plesnikova 2021-01-18 17:53:51 UTC 
Latest Fedora delivers 1.175 version. Upstream released 1.176. When you have free time, please upgrade it.
Comment 1 Fedora Update System 2021-02-01 13:55:02 UTC 
FEDORA-2021-eacfa94d3e has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-eacfa94d3e
Comment 2 Fedora Update System 2021-02-02 02:19:25 UTC 
FEDORA-2021-eacfa94d3e has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-eacfa94d3e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-eacfa94d3e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Ben Cotton 2021-02-09 15:41:33 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.
Comment 4 Fedora Update System 2021-02-10 01:18:53 UTC 
FEDORA-2021-eacfa94d3e has been pushed to the Fedora 33 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.