From rmayorga at debian.org Mon Sep 1 07:50:10 2014 From: rmayorga at debian.org (=?UTF-8?Q?Ren=C3=A9?= Mayorga) Date: Mon, 1 Sep 2014 07:50:10 +0000 Subject: Bug#760134: Updating the cyrus-imapd-2.4 Uploaders list Message-ID: <20140901075010.GA4962@mail.rmayorga.org> Package: cyrus-imapd-2.4 Version: 2.4.16-4+deb7u1 Severity: minor User: mia at qa.debian.org Usertags: mia-teammaint benjamin at debian.org has retired, so can't work on the cyrus-imapd-2.4 package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. -- Ren? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: From Ross.Boylan at ucsf.edu Tue Sep 23 01:51:59 2014 From: Ross.Boylan at ucsf.edu (Boylan, Ross) Date: Tue, 23 Sep 2014 01:51:59 +0000 Subject: finding the code and upgrade notes Message-ID: It would be good if the COPYRIGHT had a pointer to the Debian source code. It would be nice if the code were browseable online. https://tracker.debian.org/pkg/cyrus-imapd-2.4 does have a browse link for the VCS, but clicking on it only gives you a directory with 2 icons. I was looking for this because I was looking for upgrade notes and hoping they were in the source. Is that where to look for them? Thanks. Ross Boylan From Ross.Boylan at ucsf.edu Tue Sep 23 01:45:10 2014 From: Ross.Boylan at ucsf.edu (Boylan, Ross) Date: Tue, 23 Sep 2014 01:45:10 +0000 Subject: multi-step "upgrade" Message-ID: I'm reconstructing a system that was on Lenny to be either Wheezy (likely) or maybe testing. It included Cyrus imap (2.2) and SASL. Any advice for how to go about this? I have backups; in fact the system now seems to be running OK as Lenny, but it's no longer trustworthy (various file-system and lower-level problems). I know that upgrades are only guaranteed one step at a time but a) I would like to avoid all the steps and b) it's not exactly an upgrade since I don't want to start from the existing system. More like install wheezy and then restore old data. Some of my files are Berkeley DB. I suppose this means I have to reconstruct enough of a Lenny system to dump them, and then migrate or restore them (not sure exactly how). The upstream upgrade notes are somewhat unclear (http://cyrusimap.org/docs/cyrus-imapd/2.4.17/install-upgrade.php). Literally the headings imply that only the "Upgrading from 2.2.x or earlier" section is relevant (if going straight to 2.4.17), but I assume I actually need to read through the whole thing for all higher versions to figure out what to do. My /usr/lib/cyrus/cyrus-db-types.active: ANNOTATION skiplist DBENGINE BerkeleyDB4.2 DUPLICATE berkeley-nosync MBOX skiplist PTS berkeley QUOTA quotalegacy SEEN skiplist SUBS flat TLS berkeley-nosync Hmm, maybe the berkely db's don't need to be reconstructed. Thanks. Ross Boylan P.S. squatter has failed every time it's run from well before the latest problems, and so there may be something else that was corrupt already. Other than that, no noticeable problems. Also, I tried a lenny->squeeze upgrade in a VM (when stable was squeeze) and it did not go well. From Ross.Boylan at ucsf.edu Tue Sep 23 01:59:06 2014 From: Ross.Boylan at ucsf.edu (Boylan, Ross) Date: Tue, 23 Sep 2014 01:59:06 +0000 Subject: finding the code and upgrade notes In-Reply-To: References: Message-ID: >It would be nice if the code were browseable online. https://tracker.debian.org/pkg/cyrus-imapd-2.4 does have a browse link for the VCS, but clicking on it only gives you a directory with 2 icons. Silly me: the "browse source code" link on the other side of the page had what I wanted. What's the other "browse" like (by the VCS) for? Ross From dwhite at olp.net Tue Sep 23 13:50:58 2014 From: dwhite at olp.net (Dan White) Date: Tue, 23 Sep 2014 08:50:58 -0500 Subject: multi-step "upgrade" In-Reply-To: References: Message-ID: <20140923135057.GB3721@dan.olp.net> On 09/23/14?01:45?+0000, Boylan, Ross wrote: >I'm reconstructing a system that was on Lenny to be either Wheezy (likely) >or maybe testing. It included Cyrus imap (2.2) and SASL. Any advice for >how to go about this? The path of least resistance for such a big jump would be to migrate your IMAP store with an imapsync script, or an imap client such as mutt. That won't allow for upgrading a system in place obviously. >I know that upgrades are only guaranteed one step at a time but a) I would >like to avoid all the steps and b) it's not exactly an upgrade since I >don't want to start from the existing system. More like install wheezy >and then restore old data. >My /usr/lib/cyrus/cyrus-db-types.active: >ANNOTATION skiplist >DBENGINE BerkeleyDB4.2 >DUPLICATE berkeley-nosync >MBOX skiplist >PTS berkeley >QUOTA quotalegacy >SEEN skiplist >SUBS flat >TLS berkeley-nosync Another advantage of synchronizing over imap is the ability to move to newer database formats. >P.S. squatter has failed every time it's run from well before the latest >problems, and so there may be something else that was corrupt already. >Other than that, no noticeable problems. Also, I tried a lenny->squeeze >upgrade in a VM (when stable was squeeze) and it did not go well. If you're using sieve scripts, those will likely need to be moved over manually and recompiled, or transferred over managesieve. -- Dan White