Hi Nic,
Damn! That interface is really frustrating in terms of inability to debug.
One possible culprit in all this is b56e391c9579b3c4c9fd6e64fa29e627ec358339.
I've just copied that back to 3.0 asc665af571dc1f9d870d53f2aa4ea29bb5cd52738 .
Are you able to try with that added?
Cheers,
Bron
Hi,
I've just attached the real release files from the 3.0.7 release (from 18th of
May) to the GitHub "release" tag for it, as an experiment to see what happens:
https://github.com/cyrusimap/cyrus-imapd/releases
So far I can see that it's now listing it as the "latest release" (correct) "3
min
Bron,
Answering my own question, I now see that the fix you refer to is in
cfb3054, imap/mailbox.c on 1/2/2017, which is in both master and 3.0...
However, I've still got the problem, so same failed assertion, but
different bug?
-nic
On 07/24/2018 12:10 PM, Nic Bernstein wrote:
Bron, et
Anthony,
I think this is a different error, just hitting the same assertion
tripwire. I'm getting a problem in reconstruct(8), but your is showing
up in imapd.
-nic
On 07/26/2018 04:16 AM, Anthony Prades via Cyrus-devel wrote:
Hi,
Same problem here.
Context:
Upgrade cyrus from 2.4.20
Hi,
Same problem here.
Context:
Upgrade cyrus from 2.4.20 to Cyrus 3.0.7.
As our spool is very big, we plan to run reconstruct -V max in a second
time as it seems to be possible from 2.5
(https://www.cyrusimap.org/2.5/imap/release-notes/2.5/x/2.5.0.html).
After upgrade binaries, mailbox are
