Bug 1753714 - chance to maintain rubygem-ruby-shadow on EPEL
Summary: chance to maintain rubygem-ruby-shadow on EPEL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-ruby-shadow
Version: 32
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Terje Røsten
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-19 15:40 UTC by Breno
Modified: 2020-05-12 02:13 UTC (History)
1 user (show)

Fixed In Version: rubygem-ruby-shadow-2.5.0-12.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-12 02:13:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Breno 2019-09-19 15:40:23 UTC
Hi,

Right now rubygem-ruby-shadow is not maintained on EPEL.

This is specifically important now that ruby-shadow is obsoleted by rubygem-ruby-shadow.

Would you please mind maintaining rubygem-ruby-shadow on EPEL?

Thank you very much.

- Breno

Comment 1 Ben Cotton 2020-02-11 17:55:33 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 2 Fedora Update System 2020-05-04 08:25:52 UTC
FEDORA-EPEL-2020-219cf9061b has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-219cf9061b

Comment 3 Fedora Update System 2020-05-05 00:24:36 UTC
FEDORA-EPEL-2020-219cf9061b has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-219cf9061b

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

Comment 4 Fedora Update System 2020-05-12 02:13:53 UTC
FEDORA-EPEL-2020-219cf9061b has been pushed to the Fedora EPEL 8 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.