[Kolab-devel] [Kolab-announce] Issue tracker migration
Jeroen van Meeuwen (Kolab Systems)
vanmeeuwen at kolabsys.com
Wed Feb 1 13:00:08 CET 2012
On 2011-11-22 15:01, Cristian Rigamonti wrote:
> On Mon, Nov 14, 2011 at 05:18:19PM +0000, Jeroen van Meeuwen (Kolab
> Systems) wrote:
>>
>> Please submit those issues to resubmit-issues at kolab.org, and we will
>> work to make sure the existing Roundup issue is properly represented
>> by
>> a new copy in Bugzilla where appropriate.
>
> Hi, here are my bugs that still need a resolution:
>
> - https://roundup.kolab.org/issue4377
>
This ticket is now https://issues.kolab.org/show_bug.cgi?id=547
Note that this is an OpenPKG related tidbit, which could simply be
resolved by using native packages.
> Still need rotation for files listed in
> https://roundup.kolab.org/msg28248
>
> - https://roundup.kolab.org/issue2983
>
> Problem still happening
>
This is a Horde configuration and/or cclient handling issue more so
than anything else.
Configuring Horde with parameters such as (I took this from my FreeBusy
configuration file):
$conf['kolab']['imap']['server'] = 'imap.klab.cc';
$conf['kolab']['imap']['port'] = 143;
$conf['kolab']['imap']['protocol'] =
'imap/tls/novalidate-cert/readonly';
prevents the error from being displayed. Alternatively, you can use SSL
over port 993. You would also no longer need 'allowplaintext: 1' in
/etc/imapd.conf.
> - https://roundup.kolab.org/issue4786
>
> logfile permission error and logfile format incompatibility
>
This is caused by a mix between Kolab OpenPKG and Debian native
packages, for which in order to resolve the issue I'm afraid we're
developing our way out of it using native packaging rather then
prioritizing fixing OpenPKG.
The permission problem is now
https://issues.kolab.org/show_bug.cgi?id=579
The format problem is a logchecker problem more so than a Kolab problem
though, I'm afraid. If logchecker does not allow one to specify the
format for the log file to be checked, I'm not sure what Kolab (within
OpenPKG) is supposed to be able to do about that.
That said, again native packaging should resolve the format issue as in
native packaging, syslog is being used.
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
More information about the devel
mailing list