Bug 1883473 - Please build ripmime for EPEL7
Summary: Please build ripmime for EPEL7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: ripmime
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Itamar Reis Peixoto
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-29 10:39 UTC by Xavier Bachelot
Modified: 2020-09-30 01:37 UTC (History)
1 user (show)

Fixed In Version: ripmime-1.4.0.10-7.el7 ripmime-1.4.0.10-7.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-30 00:33:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Xavier Bachelot 2020-09-29 10:39:28 UTC 
Could you please build ripmime for EPEL 7 and also EPEL 8 ?
Current specfile rebuilds properly against both of them.
Also, I've filed a PR with a couple cleanups for the specfile:
https://src.fedoraproject.org/rpms/ripmime/pull-request/1

Regards,
Xavier
Comment 1 Itamar Reis Peixoto 2020-09-29 13:20:23 UTC 
[itamar@localhost ripmime]$ fedpkg request-branch epel7 
https://pagure.io/releng/fedora-scm-requests/issue/29289

[itamar@localhost ripmime]$ fedpkg request-branch epel8
https://pagure.io/releng/fedora-scm-requests/issue/29290
https://pagure.io/releng/fedora-scm-requests/issue/29291
Comment 2 Fedora Update System 2020-09-29 13:36:48 UTC 
FEDORA-EPEL-2020-7f1b1d582a has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-7f1b1d582a
Comment 3 Fedora Update System 2020-09-30 00:33:28 UTC 
FEDORA-EPEL-2020-7f1b1d582a has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 4 Fedora Update System 2020-09-30 01:37:26 UTC 
FEDORA-EPEL-2020-125d6b8fbe 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.