It looks like EPEL is now stable on RHEL6 but I do not see any 389ds packages in the epel or epel-testing repos. Any idea when that is happening? I'm setting up a new machine and wanted to start using RHEL6 if possible to take advantage of some of the new fun features of RHEL6.
Thanks for all your hard work, 389ds is great!
Sincerely,
Aaron Hagopian
On 01/26/2011 12:25 PM, Aaron Hagopian wrote:
It looks like EPEL is now stable on RHEL6 but I do not see any 389ds packages in the epel or epel-testing repos. Any idea when that is happening? I'm setting up a new machine and wanted to start using RHEL6 if possible to take advantage of some of the new fun features of RHEL6.
389-ds-base will be going into RHEL 6 at some point. We cannot put it in EPEL6 because it would conflict. We are interested in suggestions about how to provide binary packages on EL6.
Thanks for all your hard work, 389ds is great!
Sincerely,
Aaron Hagopian
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
Rich Megginson wrote:
389-ds-base will be going into RHEL 6 at some point. We cannot put it in EPEL6 because it would conflict. We are interested in suggestions about how to provide binary packages on EL6.
pardon my ignorance, but what would it clash with ?
Cheers Sean
On 01/27/2011 01:33 AM, Sean Murray wrote:
Rich Megginson wrote:
389-ds-base will be going into RHEL 6 at some point. We cannot put it in EPEL6 because it would conflict. We are interested in suggestions about how to provide binary packages on EL6.
pardon my ignorance, but what would it clash with ?
389-ds-base in RHEL6.
Cheers Sean
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
389-ds-base will be going into RHEL 6 at some point. We cannot put it in EPEL6 because it would conflict. We are interested in suggestions about how to provide binary packages on EL6.
pardon my ignorance, but what would it clash with ?
389-ds-base in RHEL6.
And I assume that's in the Directory Server channel because on my RHEL6 machine no 389-ds-base package exists and I do not have a subscription to Redhat Directory service. Again working on my assumption that means that RH directory service is using the same package name as 389ds which would create the conflict. So either 389-ds packages are renamed or cannot go in EPEL, now its making sense.
So is there some obstacle for the 389ds project to host its own yum repo?
On 01/27/2011 08:33 AM, Aaron Hagopian wrote:
389-ds-base will be going into RHEL 6 at some point. We cannot put it in EPEL6 because it would conflict. We are interested in suggestions about how to provide binary packages on EL6.pardon my ignorance, but what would it clash with ?389-ds-base in RHEL6.And I assume that's in the Directory Server channel because on my RHEL6 machine no 389-ds-base package exists and I do not have a subscription to Redhat Directory service. Again working on my assumption that means that RH directory service is using the same package name as 389ds which would create the conflict. So either 389-ds packages are renamed or cannot go in EPEL, now its making sense.
389-ds-base is not _yet_ in RHEL6. Will be there in 6.1 or 6.2.
So is there some obstacle for the 389ds project to host its own yum repo?
Other than being a PITA? But if that is the only way . . .
-- 389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
389-users@lists.fedoraproject.org
-
Aaron Hagopian -
Rich Megginson -
Sean Murray