On Apr 3, 2014, at 3:39 PM, Rich Megginson <rmeggins@xxxxxxxxxx> wrote: > On 04/03/2014 01:35 PM, Michael Gettes wrote: >> Yeah, I hear what you’re saying. 47758 is due to running bleeding edge, i get it. but i had to go there cuz I was having problems with objects getting messed up with .15 in production and even .25 in test and I went to .28 which had the SASL fix on top of .26 which fixed all object problems. The object problems were the emails I sent to the list indicating objects I couldn’t delete or modify and .28 fixed those problems. This is where i feel i was a little trapped and had to come forward to the bleeding edge. there was a method to my madness and didn’t this just willy nilly and hence where i was hoping for .29 to i might have a good mix of things - even if it was on the bleeding edge. i hope this makes sense. > > Yes, and we are working on fixing those issues in EL6.6. So perhaps when EL6.6 is released you will be able to use the OS packages. Rich et al, I've been following this thread with interest. I am however a little confused about the right place and version to get 389: you make a distinction between the source version (versions 1.2.11.28 and 1.3.1.16). Both are stable, 1.3.1 is just newer and potentially more bleeding edge? 1.3.1 also seems to not be available from either the OS or epel repositories. CentOS 6 includes centos-ds-base which is 1.2.11.15 and just includes the base directory server. Epel seems to contain all the accessory utilities (admin server, console, etc). However: On Apr 3, 2014, at 11:48 AM, Rich Megginson <rmeggins@xxxxxxxxxx> wrote: > And that problem is entirely due to running "bleeding edge" software - a new patch/feature urgently requested to be in EL6.6 that we didn't completely backport to epel6. If you were running the standard 389-ds-base in EL6.5 you would not have seen this issue. The 389-ds-base in epel6 contains patches intended for EL6.6 but which have not yet been fully tested. The only way you could get into a real bind is if you have run into an issue due to be fixed in EL6.6 that you urgently need and can't wait for it to be released through the usual EL6.6 channels. I don't see 389-de-base in epel, just adimin server, console etc. And if epel6 contains patches that have not been fully tested and I should avoid it in production but how do I get the admin server, console etc? On Apr 3, 2014, at 10:53 AM, Michael Gettes <gettes@xxxxxxxxx> wrote: > I recognize 389 is a community project and asking for timelines can be problematic. Right now, I am sorta stuck between a rock and a hard place. In production, I am on 1.2.11.15 which has problems that are fixed by 1.2.11.28. I have 1.2.11.28 in test and fixes all my prod problems but introduces a new problem which makes it rather difficult to manage the environment and it would appear this will be corrected in 1.2.11.29. So, I am a little curious as to when we might see 29. I do see on the roadmap 29 has 4 closed and 5 active but no date set. Wouldn't this be a good time for Michael to consider 1.3.1? thanks, -morgan -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
