Mailing List ArchivesPublic Access |
![[Computer Systems Lab]](https://www-auth.cs.wisc.edu/pics/csl_logo.gif){kind=logo}
|
Mailing List ArchivesPublic Access |
|
|
Hi there, As Iâm no part of either EPEL or HTCondor teams, maybe you (both teams) should get in touch about what FrantiÅek (CCâed) replied to my email on EPEL ml so things get cleared ? I guess Iâm not the only admin to use both EPEL and HTCondor repo, and maybe thereâs a way to get things done more cleanly than using priorities ? Last point is, *if* HTCondor is to be delivered via EPEL, Iâm not that fond of using a devel version in prod. Anyway, itâs up to you, guys :) Keep up the good work ! -------- Message transfÃrà --------
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. > 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). But the condor-externals bundles external dependencies (!). Some of them are already in EPEL. > 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/ > 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 mailing list epel-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/epel-devel |