kolab on openSUSE natively is a little bit back

Carsten Burghardt carsten at cburghardt.com
Mon May 4 07:15:28 CEST 2009


Quoting "Richard Bos" <ml at radoeka.nl>:

> Op zaterdag 02 mei 2009 03:14:08 schreef Thomas Spuhler:
>> On Friday 01 May 2009, Richard Bos wrote:
>> > Op donderdag 30 april 2009 21:41:23 schreef Carsten Burghardt:
>> > > > What version of perl-ldap to you have? I found this link
>> > > > https://www.intevation.de/roundup/kolab/issue1755
>> > >
>> > > Well, the version is perl-ldap-0.39-5.2 from the kolab suse repository
>> > > but it does not contain the fix. Thanks for spotting this. I assume the
>> > > package is too old.
>> >
>> > It's not.  I have the same and it is working fine.
>> > kolab2:~ # rpm -q perl-ldap
>> > perl-ldap-0.39-5.3
>> >
>> > At the moment I can't think of a reason why you can't start ldap.  I
>> > believe I have seen the same thing, perhaps it is mentioned in issue1755.
>>
>> you have -5.3 vs. -5.2
>> different build but what else?
>
> That's a very minimal difference.  That number is added by the openSUSE build
> service, when a build is restarted.  This might be triggered by a  
> package that
> is needed as build dependency for the perl-ldap package.

Well, I installed the package from the kolab suse repository and at  
least on my system the patch is not included. Once I patched it  
manually the cookie parsing problem was gone.


Carsten




More information about the users mailing list