public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] old cyrus-imapd from overlay
Date: Wed, 29 Feb 2012 08:23:56 +0100	[thread overview]
Message-ID: <2903d5e2c4c4f8eb8f074b6b3c3b6858.squirrel@www.antarean.org> (raw)
In-Reply-To: <4F4CF416.80304@xunil.at>

On Tue, February 28, 2012 4:34 pm, Stefan G. Weichinger wrote:
>
> Greets,
>
> does anyone have experience with cyrus-imapd on gentoo?
>
> I have to migrate an ancient suse-10.1-server, it runs:
>
> # rpm -qa | grep cyrus
> cyrus-sasl-2.1.21-3
> cyrus-sasl-devel-2.1.21-3
> cyrus-imapd-2.2.12-13
>
> portage gives me cyrus-imapd-2.4.12 which is fine but I don't know if
> upgrading this far is possible without problems.
>
> I found the OSSDL-overlay, but cyrus-imapd-2.2.13 fails to build ...
>
> * does anyone have experience with upgrading cyrus-imapd?
>
> * does anyone have a running older release/ebuild where the migration
> should be safe?
>
> pls no advice to use dovecot etc, the job here is to possibly move over
> /var/spool/imap and "press play" (simplified, you get the picture).
>
> A change of software might be considered later, right now I have to
> maintain a running server while moving to newer hardware and OS.
>
> Thanks, Stefan

Stefan,

I haven't had problems with upgrading, but I didn't "wait" this long.
Eg. I didn't migrate from 2.1 to 2.4 directly.

I would suggest you check on the cyrus-imap mailing list (see bottom of
email) for tips. Installing it is simple, but there are a few changes with
some of the files.

A safer method would be running the 2 versions in parallel and using
imapsync or something similar to copy the email over to the new version.

--
Joost

cyrus-imap list info:

List-Id: Discussion group for Cyrus email system
     <info-cyrus.lists.andrew.cmu.edu>
List-Unsubscribe: <https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus>,
     <mailto:info-cyrus-request@lists.andrew.cmu.edu?subject=unsubscribe>
List-Archive: <http://lists.andrew.cmu.edu/pipermail/info-cyrus>
List-Post: <mailto:info-cyrus@lists.andrew.cmu.edu>
List-Help: <mailto:info-cyrus-request@lists.andrew.cmu.edu?subject=help>
List-Subscribe: <https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus>,
     <mailto:info-cyrus-request@lists.andrew.cmu.edu?subject=subscribe>





  reply	other threads:[~2012-02-29  7:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 15:34 [gentoo-user] old cyrus-imapd from overlay Stefan G. Weichinger
2012-02-29  7:23 ` J. Roeleveld [this message]
2012-02-29  8:10   ` Stefan G. Weichinger
2012-02-29  8:35     ` J. Roeleveld
2012-02-29  8:55       ` Stefan G. Weichinger
2012-02-29 21:27       ` [gentoo-user] SOLVED: " Stefan G. Weichinger
2012-03-02 20:23         ` Stefan G. Weichinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2903d5e2c4c4f8eb8f074b6b3c3b6858.squirrel@www.antarean.org \
    --to=joost@antarean.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox