Bug 2245509 - Please upgrade perl-GDGraph to >= 1.56
Summary: Please upgrade perl-GDGraph to >= 1.56
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-GDGraph
Version: 38
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-10-22 09:41 UTC by Ralf Corsepius
Modified: 2023-10-31 01:16 UTC (History)
3 users (show)

Fixed In Version: perl-GDGraph-1.56-1.fc37
Clone Of:
Environment:
Last Closed: 2023-10-31 01:16:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ralf Corsepius 2023-10-22 09:41:51 UTC
Upstream rt has released rt-5.0.5, which among other issues fix 2 yet undisclosed CVEs (cf. https://docs.bestpractical.com/release-notes/rt/5.0.5)

Due to this, I intend to upgrade rt on all released Fedoras, ASAP. 

Unfortunately, a prerequistite of rt-5.0.5 is perl-GDGraph >= 1.56, ie. all released Fedoras but f37 provide a suffiently recent perl-GDGraph.

Please upgrade perl-GDGraph for fc37 to >= 1.56.

Comment 1 Fedora Update System 2023-10-22 14:18:48 UTC
FEDORA-2023-f36f77c110 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f36f77c110

Comment 2 Fedora Update System 2023-10-23 02:36:31 UTC
FEDORA-2023-f36f77c110 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-2023-f36f77c110`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f36f77c110

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

Comment 3 Fedora Update System 2023-10-31 01:16:43 UTC
FEDORA-2023-f36f77c110 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.