[gentoo-user] my apologies for the mess with this release of MySQL 5.0.16
my apologies for the mess with this release of MySQL 5.0.16 and for the
one will come with the dev-db/mysql-4.1.15-r1 ebuild
Here is the relevant list of bugs opened (and closed) as a consequence
of the new ebuild.
[Bug 113451] mysql-4.1.15 re-keyworded as -* with no note in changelog
as to why
[Bug 113440] typo in mysql-5.0.16-r2 init script
[Bug 113356] /etc/init.d/mysql script fails to start server in
mysql-5.0.16
[Bug 113352] mysql-5.0.16-r1 does not
create /usr/lib{64}/libmysqlclient.so.15 symlink
[Bug 113334] mysql MD5 mysql-extras-20050920.tar.bz2 VERIFY FAILED! (old
ebuild has correct value)
If you installed 5.0.16, the 1st and don't want to re-emerge it, follow
these steps:
(may need to adjust the path accordingly with ARCH and personal
settings)
# emerge --sync
# cp /usr/portage/dev-db/mysql/files/mysql-slot.rc6 /etc/init.d/mysql
# chmod +x /etc/init.d/mysql
# cd /usr/lib{64}
# for i in libmysqlclient.so libmysqlclient_r.so ; do \
for j in .15 .15.0 .15.0.0 ; do \
echo ln -s /usr/lib/${i}.15.0.0 ${i}${j} \
; done \
; done
# chown -R mysql:mysql /var/run/mysqld/
Regards,
Francesco R.
--
gentoo-user@gentoo.org mailing list
Re: [gentoo-user] How to alter ./configure flags from emerge
Alle 15:01, mercoledì 23 novembre 2005, Harry Putnam el ga butta: |I noticed while emerging mysql that the ./configure flags used | during compile contained one that says: --without-docs | |Not a good plan for someone knowing zip about mysql. How can I |change that to --with-docs from cmdline? | |Another thing I noticed is this: | | [...] --with-big-tables --without-docs --without-big-tables | |What gives with that...? That's a bug in the ebuild, the next one will fix this. As a mitigating factor the rightmost option override the left ones. In the ebuild the rightmost is set by use flags. readline: the use flag has always worked in inversed mode, but it's too late to discuss about it, it will be removed in the next ebuilds (always linking to the system readline) also the configure option you see at compile time may _not_ be the same the ebuild used, _but_ what the ebuild set always override the MySQL default. just in case you are thnking to play with mysql-5.0.16 wait for dev-db/mysql-5.0.16-r2 -- r2 but be advised that it's shiny new and ... buggy. Cheers, Francesco R. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Re: How to alter ./configure flags from emerge
Alle 19:37, mercoledì 23 novembre 2005, Harry Putnam el ga butta: |Francesco R. [EMAIL PROTECTED] writes: | | |[...] Snipped good info here ... Thanks | | also the configure option you see at compile time may _not_ be | the same the ebuild used, _but_ what the ebuild set always | override the MySQL default. | |So we cannot really tell what is passed to the compiler? The output |of emerge is just nonsense compared to what really happens? The output of emerge _is_ what really happens, as it's the output from the build system (auto* tools and gcc) Consider the first configure you find: /var/tmp/portage/mysql-5.0.16-r2/work/mysql Source unpacked. * before to use federated engine be sure to read * http://dev.mysql.com/doc/mysql/en/federated-limitations.html * econf: updating mysql/bdb/dist/config.guess with /usr/share/gnuconfig/config.guess * econf: updating mysql/bdb/dist/config.sub with /usr/share/gnuconfig/config.sub * econf: updating mysql/config.guess with /usr/share/gnuconfig/config.guess * econf: updating mysql/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man [..] --without-big-tables --build=i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu for example --build=i686-pc-linux-gnu it's not directly setted by the ebuild (speaking of ebuild code, not the portage one) and this other (sub)configure, it also contain option not setted by the ebuild. --- config.status: executing default commands configure: configuring in innobase configure: running /bin/sh './configure' --prefix=/usr '--prefix=/usr' [..] --cache-file=/dev/null --srcdir=. checking build system type... i686-pc-linux-gnu --- As a final ans side note, it's gentoo policy that the ebuild set all the configure options avaiable to it (but it's not _mandated_ to leave the user the possibility to select them via use-flags). -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] How to alter ./configure flags from emerge
Alle 15:01, mercoledì 23 novembre 2005, Harry Putnam el ga butta: |I noticed while emerging mysql that the ./configure flags used | during compile contained one that says: --without-docs | |Not a good plan for someone knowing zip about mysql. How can I |change that to --with-docs from cmdline? | |Another thing I noticed is this: | | [...] --with-big-tables --without-docs --without-big-tables | |What gives with that...? /me damn stupid, I've forgot to mention that readding the documentation from MySQL is planned in a short term. It has been splitted out from the source distribuited .tar.gz about at ?4.1.12? :P -- gentoo-user@gentoo.org mailing list
[gentoo-user] Be careful with MySQL-5.0.16 (cahnges ebuild and rc-script)
From Bugzilla Bug 113241 mysql-5.0.16 is out Thanks for the fast report, here it is : -ChangeLog Version bump for the 5.0 series. The ebuild has been rewritten, it's the first step to slot the mysql database server. (diff 5.0.16 and 5.0.16-r30 if you don't belive at it) Also the rc scripts are changed, hopefully bug #109380 is gone (Thanks to Rodrigo Severo for shaping it). It's possible from now start more than one server tweaking the /etc/conf.d/mysql . The future of slotted MySQL is still uncertain but the rc script will be kept. More than uncertain is the slotting of MySQL-4.0 too. reassuming, be careful playing with these ebuilds, never ever ~ARCH keywords has been so unstable. -/ChangeLog--- Again _be_ careful, this stuff has been nigtly tested, the build system is'nt changed very much so if it start it should behave good, anything related to the script (also the MySQL provided see patch 080...) may be not functioning Additionally, the syntax of the /etc/conf.d/mysql script may still change. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] mysql update questions
Alle 01:22, sabato 19 novembre 2005, Mark Knecht el ga butta: |Hi, | What are my options? This mysql thing has been hanging out for a |long time. I was scared off by two things: | |1) I run MythTV which uses mysql. I have a database on my server | (this machine) that I'm worried about losing or messing up. Backup as described in http://www.gentoo.org/doc/en/mysql-upgrading.xml; replace revdep-rebuild with revdep-rebuild --soname=libmysqlclient.so.12 grep the ebuild for einfo or follow them during emerge | |2) I *think* that if I update this server then I have to update all | of my MythTV frontend boxes also as I've heard that Myth required | both the frontend and the backend to run the same versions. Maybe the following options (put them in my.cnf of the server) help #Use old password encryption method (needed for 4.0 and #older clients). old-passwords #Disallow authentication for accounts that have old # (pre-4.1) passwords. secure-auth Don't switch collation and charachter set to utf8 http://forums.gentoo.org/viewtopic-t-399371-highlight-mysql.html | | Does anyone have direct experience with this? I'm sort of worried |about creating problems that take days (or longer) to fix. | Sorry not me [...] A bit too short answer but it's very late in the morning here ... good night -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Pin an ebuild (mysql)
Alle 00:31, domenica 6 novembre 2005, David Corbin ha scritto: Even better, is there a way to have both versions of mysql installed? Portage admit more version of a package if the package itself explicitly say it is SLOTted. Slotting MySQL is planned but the roadmap has not been defined, it can be two months or one year, until we have it. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MySQL 4.1 upgrade questions
Nice, I was using the database named mysql for my data so that fits like a glove with the other software that accesses mysql. The grant tables are in the mysql database, so passwording that database secures my data and the grant tables right? Is it OK to leave the test database as is? For a security hardened database you should drop the test database and all users with % access. Also you can play with bind-address and skip-networking in the my.cnf upstream Docs: http://dev.mysql.com/doc/refman/4.1/en/security.html What I've understud from your post is that in your config the mysql database is used to keep your data, this is a dangerous, that database is managed in a special way by MySQL (and never minded to keep extraneous data). create your own database with the CREATE DATABASE name; SQL command than USE name to switch to it. Cheers -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MySQL 4.1 upgrade questions
Alle 19:39, martedì 25 ottobre 2005, Grant ha scritto: Hello, I'm upgrading my server from mysql 4.0 to 4.1 by following the instructions here: http://www.gentoo.org/doc/en/mysql-upgrading.xml I noticed this piece of instruction: emerge --config =mysql-4.1.micro_version What does that do? From what I remember, I need to password the grant table and create a new table for my data with the proper name, username, and password. Does that sounds right? Does the emerge --config command take you through any of that or do I need to figure out (remember) how to do it manually? In it's older (and deprecated) form was ebuild path/name.ebuild config . Basically it run the pkg_config() function inside the ebuild itself. Specifically MySQL pkg_config() actions are the following: - check that no mysql server are running on the box or die - check that datadir (/var/lib/mysql) is empty or die - ask for a password - install the databases (mysql test) - fill the help tables for command line client - fill the timezone tables - set the _mysql_ root password -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] MySQL 5.0 unmasked, but what does the upgrade entail?
Alle 12:44, venerdì 21 ottobre 2005, Dave Nebinger ha scritto: The devs have finally un-hard-masked MySQL (still soft masked by ~x86 keyword). But, in their wisdom, they block the 4.1 to 5.0 unless you define MYSQL_STRAIGHT_UPGRADE=1 before starting the emerge. This because there are issues, with a stright upgrade. Take a look at these upstream docs. http://dev.mysql.com/doc/refman/5.0/en/upgrading-grant-tables.html http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html http://dev.mysql.com/doc/refman/5.0/en/news-5-0-x.html http://dev.mysql.com/doc/refman/5.0/en/mysql-fix-privilege-tables.html The procedure to upgrade should be very similar to the one described by our docs for 4.0 - 4.1 http://www.gentoo.org/doc/en/mysql-upgrading.xml I originally allowed ~x86 because I wanted the 4.1 version of the db, and everything has been working fine on my end. But now it's time to consider whether or not to keep the ~x86 keyword and move to the 5.0 branch or remove it to stay at 4.1. Depend on how much time and effort you want to destiny to this, at the moment will not very much supported and the efforts are still 97% on 4.1 series that we have stabilized from few days. Timings ? An upstream developer in his blog mentioned that MySQL will be considered Generally Avaiable that mean stable on november. Minimum for stable in Gentoo tree is one month, but I don't think it will be so soon (2 or 3 months is more doable). Has anyone out there done the 4 to 5 upgrade? What will I need to do post-install to migrate my databases? Rebuild all the packages that use libmysql and reload the data. Also I hestitate to ask if I should do the upgrade; I know folks will say that it is still soft masked and that's a reason not to do it, but that kind of response I can do without. A reason outside of the soft-mask that says why I should not upgrade would be a lot more valuable. It's doable, it's unsupported, upgrading a database is rarely a easy joke, only a full reading of the previous links could give you an answer. A google search did not turn up anything gentoo specific about the upgrade, but I'm still looking for general 4 to 5 upgrading procedures (hmm, maybe I'll even get to submit a wiki article or something ;-) Because nothing exist yet ;-) . Feel free to write all you think worth to be shared. Thanks in advance! Dave Cheers -- gentoo-user@gentoo.org mailing list
[gentoo-user] MySQL 4.0 = 4.1 upgrade
Please notice that MySQL-5.0 has been erroneously unmasked for few hours but it will return under the package.mask cover at next rsync. The MySQL herd is pleased to announce that Mysql 4.1 has been unmasked today and is now marked unstable. Hope that it's possible to stabilize it soon, here there is a upgrade path. .--- | propedeutic readings: http://dev.mysql.com/doc/mysql/en/upgrading-from-4-0.html http://dev.mysql.com/doc/mysql/en/news-4-1-x.html http://dev.mysql.com/doc/mysql/en/replication-upgrade-4-0.html .--- | Upgrade path: [[[ User with a old (4.0.24 ??) mysql start from here ]]] quickpkg dev-db/mysql cmd# emerge -av --buildpkg =mysql-4.0.25-r2 cmd# ebuild \ /var/db/pkg/dev-db/mysql-4.0.25-r2/mysql-4.0.25-r2.ebuild config # Insert some kind of data fex attached backup_mysql_4.0.sql.gz [[[ User with a recent version of mysql start from here ]]] cmd# mysqldump \ -uroot \ -p$PASSWORD \ -hlocalhost \ --all-databases \ --all \ --opt \ --allow-keywords \ --flush-logs \ --hex-blob \ --master-data \ --max_allowed_packet=16M \ --result-file=BACKUP_MYSQL_4.0.SQL # check the backup file, try one one load on a mysql-4.0 server cmd# /etc/init.d/mysql stop cmd# quickpkg dev-db/mysql cmd# rm -rf /var/lib/mysql/ [[[ Real upgrade start here ]]] cmd# emerge -C mysql cmd# rm -rf /var/lib/mysql/ /var/run/mysqld/ /var/log/mysql cmd# emerge -av --buildpkg =mysql-4.1.14 cmd# revdep-rebuild cmd# ebuild /var/db/pkg/dev-db/mysql-4.1.14/mysql-4.1.14.ebuild config cmd# /etc/init.d/mysql start cmd# cat backup_mysql_4.0.sql \ | mysql \ -uroot \ -p$PASSWORD \ -hlocalhost \ --max_allowed_packet=16M cmd# mysql_fix_privilege_tables \ --defaults-file=/etc/mysql/my.cnf \ --user=root \ --password=$PASSWORD cmd# /etc/init.d/mysql restart -- gentoo-user@gentoo.org mailing list
