| Summary: | MySQL 4.1.9 ebuild | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jasmin Buchert <jasmin-genbug> |
| Component: | New packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | enhancement | CC: | farcepest, gurligebis, jameslporter, Mess1214, tradergt, vivo, volchok |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 83011 | ||
| Attachments: |
mysql-4.1.9-mysqld-safe-sh.diff
mysql-4.1.9-thrssl.patch mysql-4.1.9.ebuild mysql-CAN-2005-0004.diff mysql-4.1.9.ebuild mysql-4.1.8-CAN-2005-0004.diff (fixed) my.cnf-4.1 mysql-4.1.9.ebuild mysql-4.1.9.ebuild mysql-4.1.19-ndb.diff |
||
|
Description
Jasmin Buchert
2005-01-17 18:08:30 UTC
Created attachment 48801 [details]
mysql-4.1.9-mysqld-safe-sh.diff
Created attachment 48802 [details]
mysql-4.1.9-thrssl.patch
Created attachment 48803 [details]
mysql-4.1.9.ebuild
Created attachment 48804 [details, diff] mysql-CAN-2005-0004.diff I just saw that there's a vulnerability at bug #77805. The patch for 4.1.8 there applys cleanly to 4.1.9. Created attachment 48805 [details]
mysql-4.1.9.ebuild
Updated the ebuild to apply mysql-CAN-2005-0004.diff.
Created attachment 48911 [details, diff]
mysql-4.1.8-CAN-2005-0004.diff (fixed)
Fixed typo in patch
the updated mysql-CAN-2005-0004.diff did not apply on my machine.
I had to add the command: "cd mysql-4.1.9" before the call to "epatch ${FILESDIR}/mysql-CAN-2005-0004.diff" - then the ebuild worked correctly.
I would like to suggest some changes to the default /etc/mysql/my.cnf file. MySQL-4.1 adds a lot of support for character sets. The default character set is latin1, which is probably uncontroversial, although some may prefer to use ascii. However, the default collation (how the character set is sorted) is latin1_swedish_ci. I suspect Swedish is not a real popular choice. I also suspect that many users will only discover this after creating some tables. What I propose to add to mysql.cnf is the default settings, commented out, to the [mysqld] section: # Character set and collation (sort order) for MySQL-4.1 #default-character-set = latin1 #default-collation = latin1_swedish_ci At least then there's a hint to the administrator that the configuration option exists. Also, since my.cnf seems to come from the Portage files directory, the change won't break <dev-db/mysql-4.1*. (It would also be nice if skip-innodb were not commented out when USE=innodb is set.) Created attachment 48997 [details]
my.cnf-4.1
Updated my.cnf:
- Usage of set-variable is deprecated since MySQL 4.0.2. Use new syntax.
- Added some options from the my-medium.cnf example (for systems with
32M-64M RAM). Also added a reference to other examples with values for
different system configurations.
Created attachment 48999 [details]
mysql-4.1.9.ebuild
- Fix CAN-2005-0004 patch not applying
- Comment out skip-innodb in my.cnf when USE=innodb
- Use $FILESDIR/my.cnf-4.1
I don't know why but yesterday night I was looking exactly for this bug and I've not found it ... I will change my looking glass. So I've continued to post at #77805 http://bugs.gentoo.org/show_bug.cgi?id=77805#c26 http://bugs.gentoo.org/attachment.cgi?id=49070 Can you take a look at that? Trash the patches regading ... the patches and keep the ewarn's changes. Created attachment 49100 [details] mysql-4.1.9.ebuild Updated the ebuild with the ewarn message from bug #77805 and the default collation is now latin1_general_ci. Created attachment 49372 [details, diff] mysql-4.1.19-ndb.diff this patch is needed for preventing ndb nodes to crash on high load. see http://bugs.mysql.com/bug.php?id=7928 Comment on attachment 49372 [details, diff] mysql-4.1.19-ndb.diff this patch is needed for preventing ndb nodes to crash on high load. see http://bugs.mysql.com/bug.php?id=7928 The last proposed ebuild has this: PDEPEND="perl? ( >=dev-perl/DBD-mysql-2.9004 ) ruby? ( >=dev-ruby/mysql-ruby-2.5 )" You could also add "python? ( >=dev-python/mysql-python-1.1.9 )" to that list. steps to convert mysql databases from latin1 to utf8 # /usr/bin/mysqldump \ --user=USER \ --password=PASSWORD \ --host=localhost \ --allow-keywords \ --skip-comments \ --create-options \ --delete-master-logs \ --disable-keys \ --extended-insert \ --lock-all-tables \ --master-data \ --verbose \ -r backup-file.sql \ --all-databases # /usr/bin/sed -i "s/CHARSET=latin1/CHARSET=utf8/" backup-file.sql # /usr/bin/sed -i "s/CHARACTER SET latin1/CHARACTER SET utf8/" backup-file.sql # /usr/bin/sed -i \ "s/character set latin1 collate latin1/character set utf8 collate utf8/" \ backup-file.sql # /usr/bin/mysql -uUSER -pPASSWORD test < backup-file.sql Is there any reason this hasn't been added to portage yet? Thanks. finally I've putted it on my site at url: http://www.francesco-riosa.com/gentoo/mysql-5.0.ebuild.tar.gz some infos at http://www.francesco-riosa.com/gentoo/ the ebuild is only sligtly modified from the one here proposed and not tested (it's still compiling) but I have a running version on ~amd64 of mysql-4.1.9 with very few differences from this one enjoy 4.1.10 is out, fixes bug 77805 too 4.1.10 has been released, I'll try porting the ebuild :) Bjarke Istrup Pedersen, I'm maintaining an alternative suite of ebuilds for mysql, waiting for the new mysql series to be included in portage tree. Testers are needed, can you try to use this overlay? http://www.francesco-riosa.com/gentoo/mysql_stable-r1.ebuild.tar.gz you may want to mask >=mysql-5.0 before install it. Also if you have already a $OVERLAY/dev-db/mysql you may want to backup/remove it before. Other info at: http://www.francesco-riosa.com/gentoo/ thank you Just copied the 4.1.9 ebuild and remove the CAN patch (included), and it builds fine. Why wouldnt you just go to Francesco Riosa page and get his.. He is doing a good job of keeping 4.1 up to date. As well as 5 I did it before he posted the link :) hehe, didn't see he had posted it already, guess I should start reading things a bit more detailed :) please replace the link at #21 with: http://www.francesco-riosa.com/gentoo/mysql_overlay-latest.tar.gz and please emerge with # FEATURES="maketest" emerge mysql if you have the time, sending me "emerge --info" + "emerge output" both, failing or successfull is *veeeeery* apreciated :-) Right now there are no way to install MySQL 4.1.x from official gentoo portage tree (mysql 4.1.8 is gone from mirrors and mysql 4.1.(9|10) is not there). May be it's time to include something ? With the recent Portage tree reshuffling, the mysql-5.0.2 build no longer wants to build, since sys-apps/procps no longer exists; it was moved to sys-process/procps. Could be the 4.1.10 build is broken as well; both should be checked. I masked 5* since I really didn't want it yet anyway. thanks Andy, I've answered to a similar question at http://bugs.gentoo.org/show_bug.cgi?id=83011#c4 today Why isn't this in portage! I would like to be able to use mysql administrator and query browser, since mysqlgui has no longer been supported for some time now...We really need to get the 4.1 in the tree...why all the overlay crap? james porter: it's called insufficent time on my part (6 weeks left of a university degree). If you'd see the post Francesco made to the gentoo-dev mailing list today, you'd see that I'm officially supporting what he is doing, and that the overlay content will be merged to the tree reasonably soon. Ok, I can understand. Are you the only dev that maintains mysql section of the tree? Thanks for working on it. I can't wait to see mysql administrator and mysql query browser under linux. About comment #32 I don't know if this packages work with 4.0.24 I know for sure both work fine on "~x86" and "amd64" boxes with mysql-4.1.10a, at least using socket connections. Download the "overlay for mysql-4.1.10a" from bug #83011 If you need that version. For further comments about please open another bug. Even on ~x86 I can't get get 4.1 am I doing something wrong? I can't make mysql-administrator restore my back-up from my windows mysql server with 4.1 *** This bug has been marked as a duplicate of 83011 *** |
