Possible issue when upgrading to cyrus 3.0.8 using replication ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I have a server that I can't update running cyrus 2.5.10 which contain mailboxes that have existed from 2.3 and earlier (around 300Gb total). My plan is to update by enabling replication with a new server running Debian Buster (so cyrus 3.0.8) and then shutting down the old server. There was a problem when upgrading to 3.x.x with mailboxes created with cyrus 2.3 or before and that was fixed in 3.0.11 (see https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.11.html and https://github.com/cyrusimap/cyrus-imapd/issues/2839 for the bug report)

Does this upgrade path suffer from the same issue ? I am not familiar with the inner-workings of cyrus. It appears that the Debian maintainers have not backported the patch in 3.0.8 (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933163 and I looked at the source code)

Cheers,
Adrien
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux