-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.0.4 build failure and cassandane failures with libical3 #2200
Comments
I guess I just need to pull 1966c22 back to 3.0. |
That works, but appears to trigger two new cassandane failures. I know that some of the cassandane tests are iffy on 3.0 anyway, so I'll probably just disable them and get on with life. But maybe they do turn up some real issues.
|
We haven't upgraded cyrus-imapd to libical3 support, AFAIK. @ksmurchison should know best. If you can, please use the vendored Cyrus 3rd party libraries at https://github.com/cyrusimap/cyruslibs There's definitely the plan to make Cyrus IMAPd work with the vanilla libical3 release, though. We just haven't put effort into it. |
Well, that's what 1966c22 is, at least in part. And as far as I can tell, it does work, except for the two cassandane issues above. And admittedly, I don't really understand those failures, which is why I provided them. Regarding the vendored libraries, using them isn't really an option (it's terrible practice for a distro), and even if it were, well, the version of libical in there is... 3.0. |
Looks like this was fixed on 3.0 by 299d89a, which was included in 3.0.6 |
So libical3 is out but unfortunately the current stable cyrus doesn't build with it:
Unfortunately I haven't had much chance to dig into it further.
The text was updated successfully, but these errors were encountered: