MySQL 5.1.40 - configuration file moved

jase · 2009-11-19 22:03:28

pyther wrote:

I just added export CFLAGS="-march=i686 -mtune=generic -O2 -pipe -fno-strict-aliasing" to the pkgbuild.
These are the default CFLAGS in makepkg with the added -fno-strict-aliasing.
export CFLAGS=$CFLAGS+"-fno-strict-aliasing" might be cleaner
Actually I just applied the said fix in the code. Here is the patch
--- libmysql/libmysql.c.old     2009-11-19 14:26:39.542270424 -0500
+++ libmysql/libmysql.c 2009-11-19 14:28:47.422256556 -0500
@@ -2285,7 +2285,7 @@ mysql_stmt_param_metadata(MYSQL_STMT *st
 
 /* Store type of parameter in network buffer. */
 
-static void store_param_type(char **pos, MYSQL_BIND *param)
+static void store_param_type(uchar **pos, MYSQL_BIND *param)
 {
   uint typecode= param->buffer_type | (param->is_unsigned ? 32768 : 0);
   int2store(*pos, typecode);

I can confirm, it fixes mythtv. Thanks!

Last edited by jase (2009-11-19 22:10:56)

jesso · 2009-11-19 23:34:59

jase wrote:

pyther wrote:
I just added export CFLAGS="-march=i686 -mtune=generic -O2 -pipe -fno-strict-aliasing" to the pkgbuild.
These are the default CFLAGS in makepkg with the added -fno-strict-aliasing.
export CFLAGS=$CFLAGS+"-fno-strict-aliasing" might be cleaner
Actually I just applied the said fix in the code. Here is the patch
--- libmysql/libmysql.c.old     2009-11-19 14:26:39.542270424 -0500
+++ libmysql/libmysql.c 2009-11-19 14:28:47.422256556 -0500
@@ -2285,7 +2285,7 @@ mysql_stmt_param_metadata(MYSQL_STMT *st
 
 /* Store type of parameter in network buffer. */
 
-static void store_param_type(char **pos, MYSQL_BIND *param)
+static void store_param_type(uchar **pos, MYSQL_BIND *param)
 {
   uint typecode= param->buffer_type | (param->is_unsigned ? 32768 : 0);
   int2store(*pos, typecode);
I can confirm, it fixes mythtv. Thanks!

Does anyone know when the package will be available for upgrading?

jesso · 2009-11-19 23:40:21

My amarok does not work.

When I play a song, it quickly scrolls through all the songs and play nothing.

I had no problem before I upgraded.

Do I need to do something?

I understand the socket file moved, but I thought the latest mysql package fixes this.

pyther · 2009-11-20 02:03:46

Here is a bug report requesting the addition of the patch: http://bugs.archlinux.org/task/17214

suradasa · 2009-11-20 17:45:54

I tried this fix, but it didn't work for me. I'll tell you what I did and hopefully someone can tell me where I went wrong.

1) I sync'd ABS and ran makepkg to download the source code

2) I applied the patch to libmysql.c

3) export CFLAGS=$CFLAGS+"-fno-strict-aliasing"

4) I built the pkg using makepkg -e and installed it

5) I restarted /etc/rc.d/mysqld and tried to start the backend. I got the authentication error and when I ran mythtv-setup, I got the same old error described in this thread.

Can anyone see where I went wrong? Any help would be much appreciated...

pyther · 2009-11-20 17:47:48

What does /var/log/mythbackend.log show?

ilpianista · 2009-11-20 17:48:16

suradasa wrote:

Can anyone see where I went wrong? Any help would be much appreciated...

everything work with
mysql 5.1.41-3
mythtv 0.22-3
php 5.3.1-2
if not, remove all your change (php.ini, my.cnf, mysql.sock) and reinstall them

eldragon · 2009-11-20 17:49:06

suradasa wrote:

I tried this fix, but it didn't work for me. I'll tell you what I did and hopefully someone can tell me where I went wrong.
1) I sync'd ABS and ran makepkg to download the source code
2) I applied the patch to libmysql.c
3) export CFLAGS=$CFLAGS+"-fno-strict-aliasing"
4) I built the pkg using makepkg -e and installed it
5) I restarted /etc/rc.d/mysqld and tried to start the backend. I got the authentication error and when I ran mythtv-setup, I got the same old error described in this thread.
Can anyone see where I went wrong? Any help would be much appreciated...

mysql was bumped to 1.5.41-3 to reflect the issue described with mythtv.

so, just pacman -Syu and you should be set. remember the frontend needs mysql too. so if you have a different computer with the frontend. you should update that too.

another issue brought by someone in another thread is that old mythtv plugins can produce a database version mismatch and break hell loose

suradasa · 2009-11-20 18:58:40

Ahh, the update was not there in the repository that I was using, so I went back to the "offical" one and update everything. It now works, yay! Of course, plugins don't work. Hopefully, those will get updated soon....

firecat53 · 2009-11-20 20:47:59

mysql-python and mysql working properly with mysql 1.5.41-3 and mysql-python 1.2.3c1-2.

Thanks very much!
Scott

Skripka · 2009-11-21 04:08:53

bash wrote:

everything work with
mysql 5.1.41-3
mythtv 0.22-3
php 5.3.1-2
if not, remove all your change (php.ini, my.cnf, mysql.sock) and reinstall them

Thx for your work Bash...I've wondered how long you'd keep pushing daily SQL updates

georgia_tech_swagger · 2009-11-26 18:14:02

So ... some clarification I found out first hand ... the mysql 5.1.41-3 works with MythTV on i686. It DOES NOT however work on x86_64. x86_64 *requires* the patch mentioned on this thread.

Spider.007 · 2009-11-27 08:37:33

I created symlink as soon as this update broke several packages. Why didn't the package itself contain a symlink; so other applications could be updated silently without problems?

Last edited by Spider.007 (2009-11-27 08:38:34)

ilpianista · 2009-11-27 11:41:53

Spider.007 wrote:

I created symlink as soon as this update broke several packages. Why didn't the package itself contain a symlink; so other applications could be updated silently without problems?

sure, I can put "ln -s /var/run/mysql/mysqld.sock /tmp/mysql.sock" into mysql's PKGBUILD, and add "pacman -S mysql --noconfirm" into /etc/rc.local...

seriously speaking, all packages (ok, except mythtv on x86_64) work now. if it's not so, please file a bug report.

reset your php.ini (look for .pacnew/pacsave) first

Spider.007 · 2009-11-28 15:18:35

bash wrote:

Spider.007 wrote:
I created symlink as soon as this update broke several packages. Why didn't the package itself contain a symlink; so other applications could be updated silently without problems?
sure, I can put "ln -s /var/run/mysql/mysqld.sock /tmp/mysql.sock" into mysql's PKGBUILD, and add "pacman -S mysql --noconfirm" into /etc/rc.local...

All I'm saying is that putting that symlink in the initial package; then rebuild all packages to find the socket in the new location and then removing the symlink in a new package-update would have prevented a lot of problems

ilpianista · 2009-11-28 15:27:48

Spider.007 wrote:

All I'm saying is that putting that symlink in the initial package; then rebuild all packages to find the socket in the new location and then removing the symlink in a new package-update would have prevented a lot of problems

build the first and second mysql packages with the right configure option would have prevented a lot of problems. not that.

Arch Linux

#51 2009-11-19 22:03:28

Re: MySQL 5.1.40 - configuration file moved

#52 2009-11-19 23:34:59

Re: MySQL 5.1.40 - configuration file moved

#53 2009-11-19 23:40:21

Re: MySQL 5.1.40 - configuration file moved

#54 2009-11-20 02:03:46

Re: MySQL 5.1.40 - configuration file moved

#55 2009-11-20 17:45:54

Re: MySQL 5.1.40 - configuration file moved

#56 2009-11-20 17:47:48

Re: MySQL 5.1.40 - configuration file moved

#57 2009-11-20 17:48:16

Re: MySQL 5.1.40 - configuration file moved

#58 2009-11-20 17:49:06

Re: MySQL 5.1.40 - configuration file moved

#59 2009-11-20 18:58:40

Re: MySQL 5.1.40 - configuration file moved

#60 2009-11-20 20:47:59

Re: MySQL 5.1.40 - configuration file moved

#61 2009-11-21 04:08:53

Re: MySQL 5.1.40 - configuration file moved

#62 2009-11-26 18:14:02

Re: MySQL 5.1.40 - configuration file moved

#63 2009-11-27 08:37:33

Re: MySQL 5.1.40 - configuration file moved

#64 2009-11-27 11:41:53

Re: MySQL 5.1.40 - configuration file moved

#65 2009-11-28 15:18:35

Re: MySQL 5.1.40 - configuration file moved

#66 2009-11-28 15:27:48

Re: MySQL 5.1.40 - configuration file moved

Board footer