public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] mysql-4.1.12 call for testers
Date: Tue, 17 May 2005 02:42:54 -0700	[thread overview]
Message-ID: <20050517094254.GB5000@curie-int.orbis-terrarum.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 2074 bytes --]

Ok, the MySQL-4.1 work is finally nearing completing (it doesn't eat my
data anymore, so now you get to see if it eats your data instead).

MySQL-4.1.12 is in the tree (hard-masked), and I would like lots of early testing.
MySQL-4.0.24-r2 is also in the tree (hard-masked) for testing, and contains
some of the improvements in the 4.1 ebuilds, like the new pkg_config, and the
updated init.d script.

Warnings:
This upgrade is going to be very rough (worse than OpenLDAP-2.2).
1. mysqldump everything to SQL (save this backup! going back to 4.0 is harder!)
2. write down your user permissions, and plaintext passwords if you know them.
3. move your old /var/lib/mysql out of the way.
4. emerge unmerge mysql
5. emerge =mysql-4.1*
6. revdep-rebuild as needed (might help to do libwww manually first).
7. ebuild mysql-4.1.12.ebuild config - very important, the main 'mysql' database has a lot of structural changes.
8. make a copy of your SQL from #1, and remove the 'mysql' database.
9. import the edited SQL
10. redo your user permissions.

Many thanks to Francesco Riosa <BastianBalthazarBux@pnpitalia.it> for his hard
work in dealing with MySQL-4.1. He's joining Gentoo soon as a new developer to
help maintain MySQL for the 4.1 and 5.0 series, and hopefully also providing a
package for the official MySQL AB binaries.

There are several supporting ebuilds in the tree as well, so that things can
compile with 4.1 as needed.
dev-db/myodbc-3.51.11
dev-perl/Msql-Mysql-modules-1.2219-r2
net-libs/libwww-5.4.0-r3

I suspect that tetex may need the patch that libwww uses, as tetex bundles a
libwww source IIRC.

If 4.0.24-r2 works fine, I'd like to move it to ~arch on May 20, before I go on
my week-long vacation. If the 4.1 testing goes smoothly, it might be a
candidate for ~arch as soon as early June.

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]

             reply	other threads:[~2005-05-17  9:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17  9:42 Robin H. Johnson [this message]
2005-05-17 12:15 ` [gentoo-dev] mysql-4.1.12 call for testers Lance Albertson
2005-05-17 13:53   ` Francesco Riosa
2005-05-17 17:40     ` Alexander Simonov
2005-05-17 17:54       ` Chris Gianelloni
2005-05-17 18:55       ` Robin H. Johnson
2005-05-17 17:54   ` Rumen Yotov
2005-05-21  6:39     ` Rumen Yotov
2005-05-17 13:16 ` Paul Waring
2005-05-17 14:02   ` Francesco Riosa
2005-05-17 14:14     ` Paul Waring
2005-05-17 17:13   ` Robin H. Johnson

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=20050517094254.GB5000@curie-int.orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --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