why are we stuck on 2.2?

[Brian J. Murrell]

Binary package hint: cyrus-imapd-2.2

Upstream Cyrus IMAPD (http://www.cyrusimap.org/) is well into their 2.4 development series. Why are we stuck with 2.2, with for example, an non-working IDLE command?

[Julian Taylor (jtaylor)]

there are 2.3 (http://packages.qa.debian.org/c/cyrus-imapd-2.3.html) and 2.4 (http://packages.qa.debian.org/c/cyrus-imapd-2.4.html) in debian experimental which is not sync automatically to ubuntu.

you could request a sync with debian exp. https://wiki.ubuntu.com/SyncRequestProcess
but this must be done soon as feature freeze is on the 24. Feb

or ask the debian maintainers to upload it to unstable and get it auto synced for natty+1

[Julian Taylor (jtaylor)]

when you try to get the new version in ubuntu please also evaluate if the old one can be removed (e.g. ask the debian maintainers what their plan is)

[Brian J. Murrell (brian-interlinx)]

On 11-02-23 09:10 AM, Julian Taylor wrote:
> there are 2.3 (http://packages.qa.debian.org/c/cyrus-imapd-2.3.html) and
> 2.4 (http://packages.qa.debian.org/c/cyrus-imapd-2.4.html) in debian
> experimental which is not sync automatically to ubuntu.
>
> you could request a sync with debian exp. https://wiki.ubuntu.com/SyncRequestProcess
> but this must be done soon as feature freeze is on the 24. Feb
>
> or ask the debian maintainers to upload it to unstable and get it auto
> synced for natty+1

Or I could just do what I did and that's to enable Alessandro Bono's
cyrus-imapd PPA (https://launchpad.net/~a.bono/+archive/cyrus-imapd).