Bug 1140255 - RFE - Please build parallel for EPEL7
Summary: RFE - Please build parallel for EPEL7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: parallel
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1327342 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-10 15:13 UTC by James Hogarth
Modified: 2023-09-14 02:47 UTC (History)
8 users (show)

Fixed In Version: parallel-20160222-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1017232
Environment:
Last Closed: 2016-10-05 22:19:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description James Hogarth 2014-09-10 15:13:55 UTC
Could you please build the parallel destined for F21 in EPEL7

Comment 1 James Hogarth 2014-09-10 15:19:49 UTC
FYI the srpm from:
http://koji.fedoraproject.org/koji/buildinfo?buildID=521902


builds cleanly with this added to %files with an epel7 mock:
%doc %{_docdir}/%{name}

Comment 2 Golo Fuchert 2014-09-10 15:36:27 UTC
It seems that the moreutils package is now devided in a core package and a moreutils-parallel subpackage in EPEL, too. This was a prerequisite for including (Gnu) parallel in the repository, since it conflicts with the moreutils version of parallel. This is (or rather was) also the reason why there is no official branch for parallel in EPEL.
I would be fine with packaging parallel for EPEL as well, but I don't know the procedure how to get an EPEL branch retroactively. I will look into that, or do you happen to know this by chance?

Comment 3 Martin Gieseking 2014-09-10 15:59:09 UTC
(In reply to Golo Fuchert from comment #2)
> I would be fine with packaging parallel for EPEL as well, but I don't know
> the procedure how to get an EPEL branch retroactively. I will look into
> that, or do you happen to know this by chance?

It's easy to add additional branches to existing packages: Just place a package change request to the initial review ticket of the corresponding packages. Here you can find more detailed information about the topic:
http://fedoraproject.org/wiki/Package_SCM_admin_requests#Package_Change_Requests_for_existing_packages

Comment 4 James Hogarth 2015-03-18 10:23:44 UTC
Hi Golo,

Are you going to be able to do this?

If you are strapped for time I'd be happy to be sponsored as a co-maintainer to help out...

Comment 5 James Hogarth 2015-06-29 08:35:03 UTC
Hi Golo,

I'm now a Fedora packager so no longer need sponsorship.

If you are strapped for time for this I'm happy to act as co-maintainer and help out.

Regards,

James

Comment 6 markusN 2015-10-08 08:26:44 UTC
FYI, I compiled it for EPEL7 with a small SPEC file tweak for the docs.

https://copr.fedoraproject.org/coprs/neteler/parallel/

Comment 7 Fedora End Of Life 2015-11-04 10:16:33 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Fedora End Of Life 2015-12-02 03:47:01 UTC
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 9 Fedora Update System 2016-05-18 20:19:58 UTC
parallel-20160222-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-1995e7096b

Comment 10 Fedora Update System 2016-05-21 06:22:32 UTC
parallel-20160222-1.el7 has been pushed to the Fedora EPEL 7 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-2016-1995e7096b

Comment 11 James Hogarth 2016-06-15 20:44:35 UTC
*** Bug 1327342 has been marked as a duplicate of this bug. ***

Comment 12 James Hogarth 2016-09-21 09:25:27 UTC
This has been in EPEL7-testing for a long time now, are you able to push it to stable?

Comment 13 James Hogarth 2016-10-05 08:34:41 UTC
Since this has positive karma and has been in testing for a significant period of time I'm using PP credentials to push it to stable.

Comment 14 Fedora Update System 2016-10-05 22:19:30 UTC
parallel-20160222-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.

Comment 15 Red Hat Bugzilla 2023-09-14 02:47:19 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.