From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: News item: MySQL 5.1 bump
Date: Tue, 16 Feb 2010 04:20:27 +0000 (UTC) [thread overview]
Message-ID: <pan.2010.02.16.04.20.28@cox.net> (raw)
In-Reply-To: 20100216001408.GA346@orbis-terrarum.net
Robin H. Johnson posted on Tue, 16 Feb 2010 00:14:08 +0000 as excerpted:
> Title: MySQL 5.1 unmasking and upgrade procedures Author: Robin H.
> Johnson <robbat2@gentoo.org> Content-Type: text/plain
> Posted: 2010-02-15
> Revision: 2
> News-Item-Format: 1.0
> Display-If-Installed: <dev-db/mysql-5.1
>
> The 5.1 series of MySQL is going to be unmasked at the same time as the
> release of this news item. When upgrading from an older major version
> (including 5.0), you will be required to rebuild everything linked to
> the libmysqlclient.so.15.
>
> You can do this by installing app-portage/gentoolkit and running: #
> revdep-rebuild --library libmysqlclient.so.15
>
> If you use the Portage 2.2 series, you may also use: # emerge
> @preserved-rebuild
>
> The official upgrade docs are available here:
> http://dev.mysql.com/doc/refman/5.1/en/upgrade.html
FWIW, there's a lot of folks running mysql now that weren't before, due to
the kde 4 thing. I'm one of them, so this is of personal interest.
From your reply to Dawid W, it appears that database upgrades will need to
be done as well. Please specifically mention that, perhaps by changing
the reference to the official upgrade docs as so:
"""
Note that existing databases will need converted as well,
again including those upgrading from 5.0 to 5.1.
Details can be found in the official upgrade docs at:
http://dev.mysql.com/doc/refman/5.1/en/upgrade.html
"""
If you wish to put the unofficial upgrade recommendation in too, that
would be fine.
Hopefully that'll cover us users that don't particularly care about
databases, we just want our kde to work... and it'll continue to do so.
=:^) (IOW, are there any particularly different procedures for upgrading
databases in user's $HOME dirs? Perhaps a note for kde users telling them
where their databases are located so they /can/ back them up, etc.)
Thanks!
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2010-02-16 4:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 21:21 [gentoo-dev] News item: MySQL 5.1 bump Robin H. Johnson
2010-02-15 21:32 ` Samuli Suominen
2010-02-15 21:41 ` Robin H. Johnson
2010-02-16 0:08 ` Thilo Bangert
2010-02-15 21:51 ` [gentoo-dev] " Nikos Chantziaras
2010-02-15 22:12 ` Robin H. Johnson
2010-02-16 10:27 ` Nikos Chantziaras
2010-02-15 22:03 ` [gentoo-dev] " Ulrich Mueller
2010-02-15 22:06 ` Dawid Węgliński
2010-02-15 22:15 ` Robin H. Johnson
2010-02-15 22:54 ` Dawid Węgliński
2010-02-16 0:14 ` Robin H. Johnson
2010-02-16 4:20 ` Duncan [this message]
2010-02-16 4:33 ` [gentoo-dev] " Robin H. Johnson
2010-02-16 6:11 ` Duncan
2010-02-16 6:26 ` Robin H. Johnson
2010-02-16 10:14 ` Duncan
2010-02-16 10:34 ` Duncan
2010-02-16 14:37 ` Petteri Räty
2010-02-16 18:48 ` Joshua Saddler
2010-02-16 19:20 ` Robin H. Johnson
2010-02-16 19:48 ` Joshua Saddler
2010-02-21 2:23 ` [gentoo-dev] " Robin H. Johnson
2010-02-21 12:01 ` Richard Freeman
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=pan.2010.02.16.04.20.28@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@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