public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] mysql-4.1
Date: Thu, 20 Oct 2005 13:34:30 +0800	[thread overview]
Message-ID: <1129786470.15969.25.camel@localhost> (raw)
In-Reply-To: <4357203B.2060500@munat.com>

Running it now - up to the revdep-rebuild stage and no problems.  On an
existing mysql installation, the emerge stops with a message and points
you to an upgrade guide
("http://www.gentoo.org/doc/en/mysql-upgrading.xml").  There is a
paragraph (with warnings) at the bottom for a faster method.  Iam using
the implied "its safer" way!

The slower process involves taking a copy of your existing msql
installation (binaries+databases), emerge -C'ing mysql, rm -rf'ing the
remnants, install/rebuilding deps and then restoring the DB.  Count on
downtime!

BillK



On Wed, 2005-10-19 at 21:42 -0700, Ben Munat wrote:
> I see that MySQL-4.1 has been marked stable... anyone have any warnings I should heed 
> before undertaking the upgrade (from 4.0.25-r2)? Francesco, you still lurking?
> 
> b
-- 
gentoo-server@gentoo.org mailing list



  parent reply	other threads:[~2005-10-20  6:35 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20  4:42 [gentoo-server] mysql-4.1 Ben Munat
2005-10-20  4:49 ` Bertrand CHERRIER
2005-10-20  5:34 ` W.Kenworthy [this message]
2005-10-20  7:03   ` Dave Strydom
2005-10-20  6:51 ` W.Kenworthy
2005-10-20 13:16   ` Francesco R.
2005-10-20 13:42     ` Wolf Giesen
2005-10-20 13:55       ` Dark
2005-10-20 15:41         ` [gentoo-server] mysql-4.1, revdep-rebuild Wolf Giesen
2005-10-21 12:00     ` [gentoo-server] mysql-4.1 William Kenworthy
2005-10-21 13:15       ` Francesco R.
2005-10-20 13:03 ` Francesco R.
2005-10-21  3:18 ` Ben Munat
2005-10-21  4:55   ` Dave Strydom
2005-10-21  6:31     ` Ben Munat
2005-10-21 10:07       ` Francesco R.
2005-10-21 13:17         ` Francesco R.
2005-10-21 13:22         ` Lance Albertson
2005-10-22 12:11           ` Dave Strydom
2005-10-22 12:16             ` Dave Strydom
2005-10-22 13:26               ` Barry Marler
2005-10-22 13:31                 ` Dave Strydom
2005-10-22 13:50                 ` Lance Albertson
2005-10-22 13:55                   ` Dave Strydom
2005-10-22 14:01                     ` Craig Webster
2005-10-22 14:32                       ` Luca Longinotti
2005-10-22 14:51                         ` Craig Webster
2005-10-22 19:43                           ` Francesco R.
2005-10-22 19:46                             ` Craig Webster
2005-10-22 20:57                               ` Francesco R.
2005-10-22 22:13                               ` Luca Longinotti
2005-10-22 22:53                                 ` Petteri Räty
2005-10-22 17:00                   ` Barry Marler
2005-10-23 20:37                     ` [gentoo-server] routing bittorent radu herinean
2005-10-24  8:19                       ` Wolf Giesen
2005-10-24 14:13                       ` Marton Gabor
2005-10-22 19:46                 ` [gentoo-server] mysql-4.1 Francesco R.
  -- strict thread matches above, loose matches on Subject: below --
2005-10-20 13:40 Covington, Chris
2005-10-20 13:50 ` Dark

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=1129786470.15969.25.camel@localhost \
    --to=billk@iinet.net.au \
    --cc=gentoo-server@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