Hi there,
Is there any reason to include HTCondor (development) version in EPEL 7 ? 1) RPM is broken (kind of, lacks of condor-externals (if memory serves well) so update fails on a system where condor (using official repo) is already installed). 2) Two repos already exist for stable and devel versions, supporting el5, 6, 7, made by HTCondor people themselves: http://research.cs.wisc.edu/htcondor/yum/
Thanks,
Hi,
On Fri, 2015-08-07 at 09:07 +0200, Laurent Wandrebeck wrote:
Hi there,
Is there any reason to include HTCondor (development) version in EPEL 7 ?
The problem is there exists other SW depending on condor (particulary condor-classads library), which needs to go to EPEL 7.
The packaging is taken from Fedora branches.
- RPM is broken (kind of, lacks of condor-externals (if memory serves
well) so update fails on a system where condor (using official repo) is already installed).
But the condor-externals bundles external dependencies (!). Some of them are already in EPEL.
- Two repos already exist for stable and devel versions, supporting
el5, 6, 7, made by HTCondor people themselves: http://research.cs.wisc.edu/htcondor/yum/
I can imagine to add dummy condor-externals package, if it will help. To make it more compatible using provids/obsoletes would be problematic I guess: both repositories have increasing versions. HTCondor repositories may need to use priorities.
The best way would be to package condor directly in EPEL by HTCondor.
Cheers, Frantisek
epel-devel@lists.fedoraproject.org