Closed jasontibbitts closed 5 years ago
That's because the libical library in your Fedora mock image doesn't include the Boolean value patch from September, 2016: https://github.com/libical/libical/commit/877cefda414d56b1d029e275da4840467dba2626
I rebuilt Cyrus with libical current master in a custom installation directory, and the test passed.
Unfortunately, libical's latest stable version is 2.0, which doesn't include the patch yet. From what I understand, 2.1 is coming soon, and luckily one of libical's core maintainers is also core maintainer for cyrus-imapd. If you require a stable version to package Cyrus with, we might check with @ksmurchison on the release plans.
Oh, hmm, I had asked on the IRC channel and was told that 2.0 was just fine. I know there's a configure warning output when you're "only" running the current stable libical, but nobody could identify any breakage it would cause. I guess now we know.
As always, I'm very reluctant to use a bundled libical as then I'd be responsible for worrying about libical security issues as well. But I guess I may have to do that if I want a RHEL package anyway, as RHEL7 only has libical 1.0.1.
I guess this isn't a problem anymore, since JMAP is gone from 3.0 and libical 2.0 is old news
This is the last of my unexplained failures, and it happens consistently across all architectures. This is with 3.0.2 plus the two patches from #2042, and a Cassandane checkout from June 22. In this case, libical has been compiled with the flag allowing empty properties, though that doesn't appear to make any difference for this test.
This is the syslog output: