Re: configure: wslay v1.1.1 required but the latest one is 1.1.0

2020-06-20 Thread Anatoli
FYI, the wslay developer just released the 1.1.1 version with the commit in question so the dependency is ok now. More details here: https://github.com/cyrusimap/cyrus-imapd/issues/3070 On 5/6/20 05:11, Anatoli wrote: > Ellie, > > You're right, I haven't checked well the dates! > > I just

Re: configure: wslay v1.1.1 required but the latest one is 1.1.0

2020-06-05 Thread Anatoli
Ellie, You're right, I haven't checked well the dates! I just asked the author of Wslay if he could tag a new release. Hope we get an answer soon. Regards, Anatoli On 4/6/20 21:10, ellie timoney wrote: > The commit was authored in 2015, but the pull request was only merged to > wslay master

Re: configure: wslay v1.1.1 required but the latest one is 1.1.0

2020-06-04 Thread ellie timoney
The commit was authored in 2015, but the pull request was only merged to wslay master last November. The fix is not in 1.1.0, but it's also not in our cyruslibs version (unless my submodule is out of date, which it might be, but I thought I updated it correctly the other day). So, since the

Re: configure: wslay v1.1.1 required but the latest one is 1.1.0

2020-06-03 Thread Ken Murchison
Yes, 1.1.0 is probably sufficient, unless this bug is an issue with Cyrus: https://github.com/tatsuhiro-t/wslay/pull/47 On 6/3/20 1:19 AM, ellie timoney wrote: Cool, thanks for confirming that. So far it's sounding like 1.1.0 is probably adequate, but I'll wait a little bit to see if Ken

Re: configure: wslay v1.1.1 required but the latest one is 1.1.0

2020-06-02 Thread ellie timoney
Cool, thanks for confirming that. So far it's sounding like 1.1.0 is probably adequate, but I'll wait a little bit to see if Ken has any input once he's been online On Wed, Jun 3, 2020, at 2:58 PM, Anatoli wrote: > Hi Ellie, > > > When you configure it with your patch applied and 1.1.0