Bug 1761855 - perl-GD-SecurityImage for EL8
Summary: perl-GD-SecurityImage for EL8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: perl-GD-SecurityImage
Version: epel8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Emmanuel Seyman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-15 13:21 UTC by Xavier Bachelot
Modified: 2019-11-05 04:41 UTC (History)
3 users (show)

Fixed In Version: perl-GD-SecurityImage-1.75-4.el8
Clone Of:
Environment:
Last Closed: 2019-11-05 04:41:23 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Xavier Bachelot 2019-10-15 13:21:18 UTC 
Hi,

Could you please build perl-GD-SecurityImage in EPEL 8 ?
It's in the dependency chain of a package I'd like to build for EPEL 8.

Regards,
Xavier
Comment 1 Xavier Bachelot 2019-10-15 20:51:57 UTC 
Missing BR: perl-GD is in epel-testing (perl-GD-2.71-1.el8).
Comment 2 Emmanuel Seyman 2019-10-16 18:27:15 UTC 
https://pagure.io/releng/fedora-scm-requests/issue/18408
https://pagure.io/releng/fedora-scm-requests/issue/18409
Comment 3 Fedora Update System 2019-10-20 07:16:42 UTC 
FEDORA-EPEL-2019-60610d4a5d has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-60610d4a5d
Comment 4 Fedora Update System 2019-10-21 00:50:34 UTC 
perl-GD-SecurityImage-1.75-4.el8 has been pushed to the Fedora EPEL 8 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-60610d4a5d
Comment 5 Fedora Update System 2019-11-05 04:41:23 UTC 
perl-GD-SecurityImage-1.75-4.el8 has been pushed to the Fedora EPEL 8 stable repository. If problems still persist, 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.