Great confusion about horde CVS and pardus ebuild patches (problem turba)

[komputnik]

Hello list,
you are my last instance of stating my question about the cvs situation about the kolab integration in horde.
I have a runnning instance of kolab on my 64bit Pure Machine.
I ported my own dist. to pure 64bit which is working quite good.
Then i startet to use the horde frontend for my users. It was quite a pain to get horde working with kolab. As far as i can tell, 6 months ago, the kolab auth didn't work, so i startet with imap auth which worked for me.
Calender and Addressbook i got to work only of reading hours and hours of mailinglist entries. So, finally i got a working config.
Due to little probs, i checked out the new cvs release of horde (HEAD), so there are new features i want to use.
Now, i am back on the beginning, with the turba integration, having heavy troubles with core config issue.
Last week ,i checked the ebuild patches (which are not on the horde cvs) to get it working.
So i was only a little bit satisfied with the result.
With the patchsets i got turba working, but horde fails to address any user in the searchbar.
Also, if adding a user from the inbox always the same error occurs, but the user was added to the addressbook in imap.
The error: undefined index "full name" etc.

Yesterday there was a major upgrade to turba from horde, not from Gunnar, which make turba independend to the horde_vfs mysql integration. Now the patched of ebuold don't work anymore. The turba integration failes completely
on the configuration. The last cvs from hordeframework is used.
error: call to a member function on a non-object in /var/www/horde/turba/lib/Driver/kolab.php on line 58
Settings:
$conf['menu']['import_export'] = true;
$conf['menu']['apps'] = array();
$conf['client']['addressbook'] = 'kolab';
$conf['shares']['source'] = 'kolab_global';
$conf['comments']['allow'] = true;
$conf['documents']['type'] = 'horde';

So, is there any way to make turba working with current cvs source ?
Who is now responsible for the turba integration with kolab ?
I am quite confused what source i have to take.

Many thanks in advance

Komputnik

[Gunnar Wrobel]

Well the current situation is still bound to be unsatisfying. Originally there were that many patches to Horde that p@rdus provided separate horde packages. This was bad because it was hard to figure out the incorporated changes and you practically had to use the ebuilds in order to get Horde working.

Now most of the work has been integrated in Horde and thus the packages now rely on daily Horde CVS snapshots and provide some minor patches. This still has drawbacks since working on CVS is always a pain (at least for the users that desire stability).

Right now I was away for two weeks and just catching up again. So the ebuild patches and Horde CVS may be out of sync. I am currently working on this.

In any case if you use your own CVS based Horde checkout and apply the patches manually instead of using the provided ebuilds you will definitely be on your own. The possibilities for errors in such a configuration are vast and you will need indepth knowledge of the Horde code in order to avoid errors.

The whole situation will improve once Horde-3.2 has been released and the ebuilds will use released packages.

Cheers,

Gunnar

[komputnik]

Well the current situation is still bound to be unsatisfying. Originally there were that many patches to Horde that p@rdus provided separate horde packages. This was bad because it was hard to figure out the incorporated changes and you practically had to use the ebuilds in order to get Horde working.

Now most of the work has been integrated in Horde and thus the packages now rely on daily Horde CVS snapshots and provide some minor patches. This still has drawbacks since working on CVS is always a pain (at least for the users that desire stability).

Right now I was away for two weeks and just catching up again. So the ebuild patches and Horde CVS may be out of sync. I am currently working on this.

In any case if you use your own CVS based Horde checkout and apply the patches manually instead of using the provided ebuilds you will definitely be on your own. The possibilities for errors in such a configuration are vast and you will need indepth knowledge of the Horde code in order to avoid errors.

The whole situation will improve once Horde-3.2 has been released and the ebuilds will use released packages.

Cheers,

Gunnar

Many thanks for the very competent answer. As i have seen, you have changed your rep already to the new horde cvs "flattening model" update.
Does that mean, i can completely remove db config from turba, because of storing the complete info in a new xml and i don't need the turba tables anymore ?
I am convinced, the patches will help me so much, that the turba plug will do the things well at least.

Kind regards

Komputnik

[Gunnar Wrobel]

Yesterday there was a major upgrade to turba from horde, not from Gunnar, which make turba independend to the horde_vfs mysql integration. Now the patched of ebuold don't work anymore. The turba integration failes completely
on the configuration. The last cvs from hordeframework is used.
error: call to a member function on a non-object in /var/www/horde/turba/lib/Driver/kolab.php on line 58

Many thanks for the very competent answer. As i have seen, you have changed your rep already to the new horde cvs "flattening model" update.

My updates from yesterday should actually remove the error you have reported above.

Does that mean, i can completely remove db config from turba, because of storing the complete info in a new xml and i don't need the turba tables anymore ?

I don't use a db for horde anymore. There are still some parts of horde (perms, history etc.) that require a db but this is minor stuff. I believe that Turba should have all necessary features even if you don't use a db. I'll have to check how the virtual addressbooks are handled but this should be a thing that is based on preferences.

Cheers,

Gunnar

[Gunnar Wrobel]

There were some additional fixes necessary for Turba to work correctly. I'm still not 100% certain that everything works correctly so make sure you update CVS frequently