2003-01-12 18:07:36

by Shane Shrybman

[permalink] [raw]
Subject: [FIXED] 2.5 evolution problem

Hi,

The bug causing problems with the evolution address book is fixed in
2.5.56. I don't know if it was fixed in 2.5.55 or 2.5.56 but it was
broken in 2.5.54.

This bug(#112) is listed as RESOLVED at bugme.osdl.org. Should it be
moved to CLOSED?

Also how would one find out what the resolution was at bugme.osdl.org?
Is there a pointer to patch or cset that I missed somewhere there?

Regards,

Shane


2003-01-12 18:38:37

by Robert Love

[permalink] [raw]
Subject: Re: [FIXED] 2.5 evolution problem

On Sun, 2003-01-12 at 13:16, Shane Shrybman wrote:

> The bug causing problems with the evolution address book is fixed in
> 2.5.56. I don't know if it was fixed in 2.5.55 or 2.5.56 but it was
> broken in 2.5.54.

It was fixed in 2.5.55.

It works for me now, too, without using a hacked ORBit.

> This bug(#112) is listed as RESOLVED at bugme.osdl.org. Should it be
> moved to CLOSED?

I guess so.

> Also how would one find out what the resolution was at bugme.osdl.org?
> Is there a pointer to patch or cset that I missed somewhere there?

Not sure if you can.

You can find the fix posted to lkml, though - Michael Meeks posted it.
It was a simple fix in the getpeername() code as we thought.

Robert Love

2003-01-12 19:18:11

by Shane Shrybman

[permalink] [raw]
Subject: Re: [FIXED] 2.5 evolution problem

On Sun, 2003-01-12 at 13:47, Robert Love wrote:
> On Sun, 2003-01-12 at 13:16, Shane Shrybman wrote:
>
> > The bug causing problems with the evolution address book is fixed in
> > 2.5.56. I don't know if it was fixed in 2.5.55 or 2.5.56 but it was
> > broken in 2.5.54.
>
> It was fixed in 2.5.55.
>
> It works for me now, too, without using a hacked ORBit.
>
> > This bug(#112) is listed as RESOLVED at bugme.osdl.org. Should it be
> > moved to CLOSED?
>
> I guess so.

Ok, I will send a note to the bug owner.

>
> > Also how would one find out what the resolution was at bugme.osdl.org?
> > Is there a pointer to patch or cset that I missed somewhere there?
>
> Not sure if you can.
>
> You can find the fix posted to lkml, though - Michael Meeks posted it.
> It was a simple fix in the getpeername() code as we thought.

Ah yes I see it now, thanks.
>
> Robert Love

Shane