Hi Peter, by chance I've seen this bug explaining why eGroupWare still sits in experimental. Is there a way to automatically subscribe me to these kind of bugs, so I or the eGroupWare project in general can react?
Some first comments on the issues you mentioned: - There is no migration path from the old LDAP addressbook to the new one. The releasenotes (www.egroupware.org/wiki/releasenotes1.4) contain a link describing the changes in addressbook (www.egroupware.org/wiki/AddresbookAccountsConcept) which contains at the end a link describing how to Update an LDAP based addressbook (www.egroupware.org/egroupware/index.php?menuaction=phpbrain.uikb.view_article&art_id=57). As LDAP is used by quite a small percentage of our users (with usually a high sysadmin skill level), we choose to not provide a more automatized procedure for the upgrade. There also a readme describing the new LDAP addressbook backend, linked right where you switch the addressbook from SQL to LDAP (also offering automatized export SQL --> LDAP): www.egroupware.org/egroupware/addressbook/doc/README - Addressbook ACLs change meaning without notice, meaning people won't be able to read what they used to be able to. This might be an other documentation issue, as there are some reasons not to do an automatized conversion: it might not always do what's desired. The issues can be resolved easily by each user by moving the contacts he want to share into the appropriate group addressbook. We might have an automatic solution moving all non-private contacts which are available via a group-grant to other group-members, it the respective group addressbook. We choose not to do that automatic, as it might not always give you the expected result, eg. when you made a contact available to multiple groups, while other people made there contacts available to an other set of groups. There's been several mails on the lists describing in detail what to do: 3 clicks by each user or one line of SQL by the admin and the issue is fixed - Shared folders no longer work with Felamimail and Courier IMAP. Unfortunately the FMail developer abandoned the current FMail codebase and noone else fixed that bug so far, thought I'm not even sure there's a bug report for it in the projects bug tracker. - icalsrv is completely broken. Really. You are talking about 1.4.002? Many people reported it working better then ever (specially with Lightning/Sunbird) in 1.4.002. There was a bug with one of the other iCal clients with the content-type, which was fixed after 1.4.002 in svn and which will be included in the next maintainance release 1.4.003 How can we actively work together to resolve these issues and get a current eGroupWare versions again in Debian? Ralf eGroupWare admin -- Ralf Becker eGroupWare Training & Support ==> http://www.egroupware-support.de Outdoor Unlimited Training GmbH [www.outdoor-training.de] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 (0)631 31657-0
