Bug 1164564 - Please add EPEL7 branch
Summary: Please add EPEL7 branch
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: josm
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cédric OLIVIER
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1193626 1193630
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-16 14:24 UTC by Matěj Cepl
Modified: 2018-04-11 19:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-09 21:12:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Matěj Cepl 2014-11-16 14:24:56 UTC 
What could I add? Perhaps, just that I am willing to co-maintain the branch.
Comment 1 Matěj Cepl 2014-11-17 22:48:54 UTC 
All required packages are built in http://copr.fedoraproject.org/coprs/mcepl/josm-epel7/
Comment 2 Cédric OLIVIER 2014-11-19 18:26:06 UTC 
I would be happy to co-maintain epel branch with you.

Could you give me your FAS, if you agree to co-maintain josm in epel branch ?
Comment 3 Matěj Cepl 2014-11-19 20:01:40 UTC 
(In reply to Matěj Cepl from comment #0)
> What could I add? Perhaps, just that I am willing to co-maintain the branch.

I am a boring guy, just my Red Hat login: mcepl.
Comment 4 Cédric OLIVIER 2014-11-20 18:18:22 UTC 
epel 7 branch request done for :

josm
svgsalamander
signpost-core

do you prefer that I request for epel7 for metadata-extractor2 and xmpcore and perhaps libappstream-glib or do you want to do it yourself.
Comment 5 Matěj Cepl 2014-11-24 23:59:08 UTC 
I would rather do a minimum ... I really don't know much about packaging Java packages.
Comment 6 Jaroslav Reznik 2015-03-03 17:05:32 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Note You need to log in before you can comment on or make changes to this bug.