Bug 121486

Summary:	emerge of mysql includes bad config file (maybe it's an issue with rt instead?)
Product:	Gentoo Linux	Reporter:	Kaylea Hascall <khascall>
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	Low
Version:	2005.1
Hardware:	x86
OS:	Other
Whiteboard:
Package list:		Runtime testing required:	---

Description Kaylea Hascall 2006-02-03 16:31:59 UTC

Hi!

I did an emerge of mysql, but it doesn't run right "out of the box" as it were. The my.cnf config file isn't installed into /etc/mysql, and the copy that I found in the portage dir has some flaws. In particular, it references multiple mysql components which were installed as mysql-500 rather than plain "mysql". The following fixes help (in each case, I've changed mysql to mysql-500):

err-log         = /var/log/mysql-500/mysql.err
log             = /var/log/mysql-500/mysql.log
datadir         = /var/lib/mysql-500
language        = /usr/share/mysql-500/english

I also ran around and did some symbolic links to tie things together, just in case.

Comment 1 Jakub Moc (RETIRED) gentoo-dev

2006-02-03 16:33:36 UTC

http://www.gentoo.org/doc/en/mysql-upgrade-slotted.xml

Comment 2 Kaylea Hascall 2006-02-03 17:00:59 UTC

I'm not trying to be contrary -- but this is a new install, not an upgrade -- I installed mysql via emerge yesterday, and then installed something that relies on mysql today (rt). So it's not really an upgrade. I suppose this could be the reason rt is masked ~x86, i.e. that it doesn't deal with mysql properly. If that's the case, perhaps this is an easily-resolved issue with the rt emerge?

Comment 3 Jakub Moc (RETIRED) gentoo-dev

2006-02-04 00:45:52 UTC

Uhm, what are you describing is not a bug. That's what eselect-mysql is for, upgrade or not. It creates all the needed symlinks for you. And there's nothing wrong with the config file.