On Thu, 2008-09-11 at 14:42 +0200, Julien Kerihuel wrote: > [0x5] EMSABP provider merging > ============================= > > There is a task we omitted to tag as "blocker" and prevent from any > proper EMSABP provider merge and which is OpenChange provisioning. > > I've started to work on this issue since Tuesday. So far I have > (locally) updated the python scripts and modules and I'm currently > working on updating the openchange ldif files so we can add new classes > into samba4 schema, modify existing ones and add records openchange > needs into the sam database. > > However, we have not been touching the ldif files for a ... very very > long time and it appears that they require some changes - which I have > not finished to identify yet. Furthermore, I was basing the provisioning > task update over samba4-alpha5 release and there has been many changes > in samba4 git after the release got cut down. > > This is yet another reason (see libmapi-0.8 release schedule post) why > we need to upgrade from alpha5 release to recent git revision. > > When this task is completed, I'll be able to push a preliminary commit > and have the underlying data required to test emsabp step by step and > fix the implementation.
Hi List, This is a quick status update on the EMSABP merging process - I have been quite silent this week on this task. I have locally updated samba4 to the latest git rev but openchange doesn't work anymore with latest revisions. There are problems with fragmented/reassembled DCERPC packets. In the meantime metze provided me some patches for librpc and dcerpc_server which - on openchange side - seems to fix the problem - but which on samba4 doesn't yet pass the quicktest-fail. Conclusion, metze plan to rework these patches next week prior it can be pushed in samba4 v4-0-test. When it is on git, I'll update openchange build system to use this revision. I anyway now have a temporary samba4 version I can use to test (and update) provisioning scripts and ldif files, thus keep working step by step on the merging. It sounds like before the end of week I'll be able to push a full update for openchange provision - subject to further updates during emsabp merging if I encounter issues. Cheers, Julien. -- Julien Kerihuel [EMAIL PROTECTED] OpenChange Project Manager GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
