Your message dated Sat, 18 Jul 2009 07:47:15 +0000
with message-id <[email protected]>
and subject line Bug#447028: fixed in mysql-dfsg-5.1 5.1.36-1
has caused the Debian Bug report #447028,
regarding REPEAT() function crashes entire server when referencing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
447028: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447028
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server-5.0
Version: 5.0.32-7etch1
Severity: important
One of our MySQL servers has crashed 3 times during the last 5 days.
The server is heavily used, but there is no visble relationship
between the load on the server and the crashes, since one of the
crashes occurred at 1 AM. After every crash mysqld_safe restarted the
server, so for a little time there were no connections possible. Each
crash gives more or less the same errorlog. I've made a stacktrace
using resolve_stack_dump, and have attached the combined logfile and
the combined stacktraces of the 3 crashes. They are in chronological
order: 2007-10-12, 2007-10-15, 2007-10-17.
All three stacktraces are very similar, which leads me to think that
this problem must be reproducible. However, over 40 GB of databases
and 1000 queries/second on average doesn't make it easy to isolate the
problem :-).
Only the last errorlog mentions a hint of a query. Could
that be the problem?
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (600, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.20.4-fwsh-byte
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages mysql-server-5.0 depends on:
ii adduser 3.102 Add and remove users and groups
ii debconf [debconf-2.0] 1.5.11 Debian configuration management sy
ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries
ii libdbi-perl 1.53-1 Perl5 database interface by Tim Bu
ii libgcc1 1:4.1.1-21 GCC support library
ii libmysqlclient15off 5.0.32-7etch1 mysql database client library
ii libncurses5 5.5-5 Shared libraries for terminal hand
ii libreadline5 5.2-2 GNU readline and history libraries
ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3
ii libwrap0 7.6.dbs-13 Wietse Venema's TCP wrappers libra
ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip
ii mysql-client-5.0 5.0.32-7etch1 mysql database client binaries
ii mysql-common 5.0.32-7etch1 mysql database common files (e.g.
ii passwd 1:4.0.18.1-7 change and administer password and
ii perl 5.8.8-7 Larry Wall's Practical Extraction
ii psmisc 22.3-1 Utilities that use the proc filesy
ii zlib1g 1:1.2.3-13 compression library - runtime
Versions of packages mysql-server-5.0 recommends:
ii mailx 1:8.1.2-0.20050715cvs-1 A simple mail user agent
-- debconf information:
mysql-server/root_password: (password omitted)
mysql-server-5.0/really_downgrade: false
mysql-server-5.0/need_sarge_compat: false
mysql-server-5.0/start_on_boot: true
mysql-server/error_setting_password:
mysql-server-5.0/nis_warning:
mysql-server-5.0/postrm_remove_databases: false
mysql-server-5.0/need_sarge_compat_done: true
mysqld got signal 8;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=268435456
read_buffer_size=131072
max_used_connections=357
max_connections=750
threads_connected=16
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
1894138 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x77f308e0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x78cbb6b8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81c0659
0x817a812
0x817b767
0x8143be8
0x814d400
0x8208784
0x821440c
0x8209e85
0x820fc37
0x8209e85
0x820fc37
0x8209e85
0x820fc37
0x8209e85
0x820fc37
0x8213997
0x821fefd
0x8221c20
0x822248e
0x81d74a5
0x81dba17
0x81dbed0
0x81dd198
0x81ddba4
0xb7f55240
0xb7d903de
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow
instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x785100a0 is invalid pointer
thd->thread_id=16722517
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
pure virtual method called
terminate called without an active exception
Fatal signal 11 while backtracing
Fatal signal 6 while backtracing
071012 20:00:38 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
071012 20:01:38 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 4048875227.
InnoDB: Doing recovery: scanned up to log sequence number 0 4048877244
071012 20:01:38 InnoDB: Starting an apply batch of log records to the
database...
InnoDB: Progress in percents: 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90
91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 324, file name mysql-bin.000025
InnoDB: Last MySQL binlog file position 0 9944799, file name
/srv/db/mysql-bin.000316
071012 20:01:39 InnoDB: Started; log sequence number 0 4048877244
071012 20:01:39 [Note] Recovering after a crash using /srv/db/mysql-bin
071012 20:01:39 [Note] Starting crash recovery...
071012 20:01:39 [Note] Crash recovery finished.
071012 20:01:40 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.32-Debian_7etch1-log' socket: '/var/run/mysqld/mysqld.sock'
port: 3306 Debian etch distribution
mysqld got signal 8;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=268435456
read_buffer_size=131072
max_used_connections=689
max_connections=750
threads_connected=10
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
1894138 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x7b76aa50
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x7ac796b8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81c0659
0x817a812
0x817b767
0x8143be8
0x814d400
0x8208784
0x821440c
0x8209e85
0x820fc37
0x8209e85
0x820fc37
0x8209e85
0x820fc37
0x8209e85
0x820fc37
0x8213997
0x821fefd
0x8221c20
0x822248e
0x81d74a5
0x81dba17
0x81dbed0
0x81dd198
0x81ddba4
0xb7f10240
0xb7d4b4ae
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow
instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x7bfaa7d8 is invalid pointer
thd->thread_id=7348090
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
071017 0:49:32 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
071017 0:50:37 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 1 1783333500.
InnoDB: Doing recovery: scanned up to log sequence number 1 1783333500
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 324, file name mysql-bin.000025
InnoDB: Last MySQL binlog file position 0 28884411, file name
/srv/db/mysql-bin.000415
071017 0:50:37 InnoDB: Started; log sequence number 1 1783333500
071017 0:50:37 [Note] Recovering after a crash using /srv/db/mysql-bin
071017 0:50:37 [Note] Starting crash recovery...
071017 0:50:37 [Note] Crash recovery finished.
071017 0:50:38 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.32-Debian_7etch1-log' socket: '/var/run/mysqld/mysqld.sock'
port: 3306 Debian etch distribution
mysqld got signal 8;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=268435456
read_buffer_size=131072
max_used_connections=58
max_connections=750
threads_connected=35
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
1894138 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x7c083980
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
Cannot determine thread, fp=0x7bbfd6b8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x81c0659
0x817a812
0x817b767
0x8143be8
0x814d400
0x8208784
0x821440c
0x8209e85
0x820fc37
0x8209e85
0x820fc37
0x8209e85
0x820fc37
0x8209e85
0x820fc37
0x8213997
0x821fefd
0x8221c20
0x822248e
0x81d74a5
0x81dba17
0x81dbed0
0x81dd198
0x81ddba4
0xb7f77240
0xb7db24ae
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow
instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x9af3d90 = SELECT `cms_pages`.`id` as `id` ,
`cms_pages`.`node_id` as `node_id` , `cms_pages`.`article_date` as
`article_date` , `cms_pages`.`name` as `name` , `cms_pages`.`form_id` as
`form_id` , `cms_pages`.`article_order` as `article_order` ,
`cms_pages`.`published` as `published` , `cms_pages`.`gallery_id` as
`gallery_id` , `cms_pages`.`poll_id` as `poll_id` , `cms_pages`.`date_added`
as `date_added` , `cms_pages`.`user_added` as `user_added` ,
`cms_pages`.`date_modified` as `date_modified` , `cms_pages`.`user_modified`
as `user_modified`
, concat(repeat(' ',
cms_nodes.level-1),cms_nodes_to_lang.name, ' - ', cms_pages_to_lang.title) as
title
FROM `cms_pages`
INNER JOIN `db005831_socof000`.`cms_nodes` ON
`db005831_socof000`.`cms_nodes`.`id`=`cms_pages`.`node_id`
INNER JOIN `db005831_socof000`.`cms_nodes_to_lang` ON
`db005831_socof000`.`cms_nodes_to_lang`.`node_id`=`cms_nodes`.`id`
INNER JOIN `db005831_socof000`.`cms_pages_to_lang` ON
`db005831_socof000`.`cms_pages_to_
thd->thread_id=608147
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.
pure virtual method called
pure virtual method called
terminate called without an active exception
terminate called without an active exception
pure virtual method called
Fatal signal 6 while backtracing
terminate called recursively
pure virtual method called
pure virtual method called
pure virtual method called
pure virtual method called
pure virtual method called
terminate called recursively
pure virtual method called
terminate called recursively
pure virtual method called
terminate called recursively
071017 12:37:08 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
071017 12:38:22 InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 1 1795496028.
InnoDB: Doing recovery: scanned up to log sequence number 1 1795496028
InnoDB: In a MySQL replication slave the last master binlog file
InnoDB: position 0 324, file name mysql-bin.000025
InnoDB: Last MySQL binlog file position 0 85316845, file name
/srv/db/mysql-bin.000420
071017 12:38:23 InnoDB: Started; log sequence number 1 1795496028
071017 12:38:23 [Note] Recovering after a crash using /srv/db/mysql-bin
071017 12:38:24 [Note] Starting crash recovery...
071017 12:38:24 [Note] Crash recovery finished.
071017 12:38:24 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.0.32-Debian_7etch1-log' socket: '/var/run/mysqld/mysqld.sock'
port: 3306 Debian etch distribution
0x81c0659 handle_segfault + 681
0x817a812 _ZN16Item_func_repeat7val_strEP6String + 162
0x817b767 _ZN16Item_func_concat7val_strEP6String + 39
0x8143be8 _ZN4Item13save_in_fieldEP5Fieldb + 72
0x814d400 _ZN17Item_result_field20save_in_result_fieldEb + 32
0x8208784 _Z10copy_funcsPP4Item + 52
0x821440c _Z9end_writeP4JOINP13st_join_tableb + 124
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8213997 _Z9do_selectP4JOINP4ListI4ItemEP8st_tableP9Procedure + 247
0x821fefd _ZN4JOIN4execEv + 2157
0x8221c20
_Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_sel
+ 304
0x822248e _Z13handle_selectP3THDP6st_lexP13select_resultm + 318
0x81d74a5 _Z21mysql_execute_commandP3THD + 9557
0x81dba17 _Z11mysql_parseP3THDPcj + 471
0x81dbed0 _Z16dispatch_command19enum_server_commandP3THDPcj + 1120
0x81dd198 _Z10do_commandP3THD + 136
0x81ddba4 handle_one_connection + 2308
0xb7f55240 _end + -1350121744
0xb7d903de _end + -1351976818
0x81c0659 handle_segfault + 681
0x817a812 _ZN16Item_func_repeat7val_strEP6String + 162
0x817b767 _ZN16Item_func_concat7val_strEP6String + 39
0x8143be8 _ZN4Item13save_in_fieldEP5Fieldb + 72
0x814d400 _ZN17Item_result_field20save_in_result_fieldEb + 32
0x8208784 _Z10copy_funcsPP4Item + 52
0x821440c _Z9end_writeP4JOINP13st_join_tableb + 124
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8213997 _Z9do_selectP4JOINP4ListI4ItemEP8st_tableP9Procedure + 247
0x821fefd _ZN4JOIN4execEv + 2157
0x8221c20
_Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_sel
+ 304
0x822248e _Z13handle_selectP3THDP6st_lexP13select_resultm + 318
0x81d74a5 _Z21mysql_execute_commandP3THD + 9557
0x81dba17 _Z11mysql_parseP3THDPcj + 471
0x81dbed0 _Z16dispatch_command19enum_server_commandP3THDPcj + 1120
0x81dd198 _Z10do_commandP3THD + 136
0x81ddba4 handle_one_connection + 2308
0xb7f10240 _end + -1350404368
0xb7d4b4ae _end + -1352259234
0x81c0659 handle_segfault + 681
0x817a812 _ZN16Item_func_repeat7val_strEP6String + 162
0x817b767 _ZN16Item_func_concat7val_strEP6String + 39
0x8143be8 _ZN4Item13save_in_fieldEP5Fieldb + 72
0x814d400 _ZN17Item_result_field20save_in_result_fieldEb + 32
0x8208784 _Z10copy_funcsPP4Item + 52
0x821440c _Z9end_writeP4JOINP13st_join_tableb + 124
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8209e85 _Z20evaluate_join_recordP4JOINP13st_join_tableiPc + 405
0x820fc37 _Z10sub_selectP4JOINP13st_join_tableb + 119
0x8213997 _Z9do_selectP4JOINP4ListI4ItemEP8st_tableP9Procedure + 247
0x821fefd _ZN4JOIN4execEv + 2157
0x8221c20
_Z12mysql_selectP3THDPPP4ItemP13st_table_listjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_sel
+ 304
0x822248e _Z13handle_selectP3THDP6st_lexP13select_resultm + 318
0x81d74a5 _Z21mysql_execute_commandP3THD + 9557
0x81dba17 _Z11mysql_parseP3THDPcj + 471
0x81dbed0 _Z16dispatch_command19enum_server_commandP3THDPcj + 1120
0x81dd198 _Z10do_commandP3THD + 136
0x81ddba4 handle_one_connection + 2308
0xb7f77240 _end + -1349982480
0xb7db24ae _end + -1351837346
--- End Message ---
--- Begin Message ---
Source: mysql-dfsg-5.1
Source-Version: 5.1.36-1
We believe that the bug you reported is fixed in the latest version of
mysql-dfsg-5.1, which is due to be installed in the Debian FTP archive:
libmysqlclient-dev_5.1.36-1_amd64.deb
to pool/main/m/mysql-dfsg-5.1/libmysqlclient-dev_5.1.36-1_amd64.deb
libmysqlclient15-dev_5.1.36-1_all.deb
to pool/main/m/mysql-dfsg-5.1/libmysqlclient15-dev_5.1.36-1_all.deb
libmysqlclient16_5.1.36-1_amd64.deb
to pool/main/m/mysql-dfsg-5.1/libmysqlclient16_5.1.36-1_amd64.deb
mysql-client-5.1_5.1.36-1_amd64.deb
to pool/main/m/mysql-dfsg-5.1/mysql-client-5.1_5.1.36-1_amd64.deb
mysql-client_5.1.36-1_all.deb
to pool/main/m/mysql-dfsg-5.1/mysql-client_5.1.36-1_all.deb
mysql-common_5.1.36-1_all.deb
to pool/main/m/mysql-dfsg-5.1/mysql-common_5.1.36-1_all.deb
mysql-dfsg-5.1_5.1.36-1.diff.gz
to pool/main/m/mysql-dfsg-5.1/mysql-dfsg-5.1_5.1.36-1.diff.gz
mysql-dfsg-5.1_5.1.36-1.dsc
to pool/main/m/mysql-dfsg-5.1/mysql-dfsg-5.1_5.1.36-1.dsc
mysql-dfsg-5.1_5.1.36.orig.tar.gz
to pool/main/m/mysql-dfsg-5.1/mysql-dfsg-5.1_5.1.36.orig.tar.gz
mysql-server-5.1_5.1.36-1_amd64.deb
to pool/main/m/mysql-dfsg-5.1/mysql-server-5.1_5.1.36-1_amd64.deb
mysql-server_5.1.36-1_all.deb
to pool/main/m/mysql-dfsg-5.1/mysql-server_5.1.36-1_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Christian Hammers <[email protected]> (supplier of updated mysql-dfsg-5.1 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 01 Jul 2009 20:54:58 +0200
Source: mysql-dfsg-5.1
Binary: libmysqlclient16 libmysqlclient15-dev libmysqlclient-dev mysql-common
mysql-client-5.1 mysql-server-5.1 mysql-server mysql-client
Architecture: source all amd64
Version: 5.1.36-1
Distribution: experimental
Urgency: low
Maintainer: Debian MySQL Maintainers <[email protected]>
Changed-By: Christian Hammers <[email protected]>
Description:
libmysqlclient-dev - MySQL database development files
libmysqlclient15-dev - MySQL database development files - empty transitional
package
libmysqlclient16 - MySQL database client library
mysql-client - MySQL database client (metapackage depending on the latest
versio
mysql-client-5.1 - MySQL database client binaries
mysql-common - MySQL database common files (e.g. /etc/mysql/my.cnf)
mysql-server - MySQL database server (metapackage depending on the latest
versio
mysql-server-5.1 - MySQL database server binaries
Closes: 447028 447713 450535 470854 508406 515145 526254 533999 535492 535500
Changes:
mysql-dfsg-5.1 (5.1.36-1) experimental; urgency=low
.
[TODO]
* Link libmysqlclient.so to libmysqlclient_r.so to help applications
like Apache where some modules, like libaprutil, want to use the thread
safe library and some, like PHP, do not. As the client library just copies
data between client and server, we do not expect significant performance
losses. (thanks to Stefan Fritsch). Closes: #450535
.
Add the following to libmysqlclient16.links:
usr/lib/libmysqlclient_r.so.16.0.0 usr/lib/libmysqlclient.so.16.0.0
.
* Ex-maintainer upload :)
* New upstream release.
* SECURITY: Upstream fix for "mysql client does not escape strings in
--html mode." (CVE-2008-4456) Closes: #526254
* Upstream fixes REPEAT() function. Closes: #447028
* Upstream fixes problems when mixing ORDER and GROUP BY. Closes: #470854
* There were many innodb fixes in the last two years, probably
also for this unreproducible crash. CLoses: #447713
* Removed amd64 specific -fPIC compiler option that was introduced
especially for building the NDB cluster module which is no longer
part of this package (thanks to Modestas Vainius). Closes: #508406
* Put /etc/mysql/conf.d to mysql-server-5.1.dirs (thanks to Alexander
Gerasiov). Closes: #515145
* Fixed mysql-test suite by adding 50_mysql-test__db_test.dpatch.
It now passes 100% of the tests again. Also Closes: #533999
* Preinst now prevents Installation if NDB configuration is detected.
* Applied Ubuntu patch that fixes privilege bootstrapping in postinst
(thanks to Mathias Gug). Closes: #535492
* Applied Ubuntu patch that sets the debconf prio for the root password
question to high and prevents it from being asked on 5.0 -> 5.1 upgrades
(thanks to Mathias Gug). Closes: #535500
* Removed the check for ISAM tables as the only supported upgrade path is
from lenny's MySQL-5.0.
* Added /etc/mysql/conf.d/mysqld_safe_syslog.cnf which enables mysqld_safe
to pipe all mysqld output into the syslog. The reason for not letting dpkg
handle it via a normal config file change was that my.cnf is usually
heavily tuned by the admin so the setting would go lost too easily.
* Updated mysqlreport to version 3.5 (including two minor patches by me).
Checksums-Sha1:
9318a87ccf4f044052d15d7c3b837e1d19c11b8a 1652 mysql-dfsg-5.1_5.1.36-1.dsc
c5efbf1821742d2e7b1c02511d266de117c19b0a 18263034
mysql-dfsg-5.1_5.1.36.orig.tar.gz
3d864cab767100ccd58dba90440d5742c8fc8694 283528 mysql-dfsg-5.1_5.1.36-1.diff.gz
77f3bb147cb5156a6f48a800ec8fbd3e9005623d 54884
libmysqlclient15-dev_5.1.36-1_all.deb
e685fc0564a49e5374c48e4d823d1f9ce79e6cc8 60446 mysql-common_5.1.36-1_all.deb
a9b8c080debd736712939631b5c9eedcec268cbf 55068 mysql-server_5.1.36-1_all.deb
11042c2b51d709bc8279d57770693c2d0feedcf7 54936 mysql-client_5.1.36-1_all.deb
b4196190051238f621e6c865b65138ae556bfef7 1953306
libmysqlclient16_5.1.36-1_amd64.deb
67b4bbe30243644a4c30de69f860d81523d14a97 6678002
libmysqlclient-dev_5.1.36-1_amd64.deb
ba502cb869281064a7862acba13c3bcb03f0394c 9115414
mysql-client-5.1_5.1.36-1_amd64.deb
46d7a1be6707fb5fe7bbedda2657eb24ded3668c 10732690
mysql-server-5.1_5.1.36-1_amd64.deb
Checksums-Sha256:
b74eea53f321837c1054b70734b3bde6ef235db1737cdebfb5d3e9d5ac05ef9d 1652
mysql-dfsg-5.1_5.1.36-1.dsc
a2a70518069d93f6bb3d1561db4d2e622db9d9c08acd99b0f9509d3eedb9b47b 18263034
mysql-dfsg-5.1_5.1.36.orig.tar.gz
b0c54fdca2b544fcc9f5336a67a747df1319a5fb41838dffa6556c8510d2143e 283528
mysql-dfsg-5.1_5.1.36-1.diff.gz
8321c34a66ce39a75e1fab6596d9d07bd0a5fd01806e2e8b2b4f21ee1f3a923e 54884
libmysqlclient15-dev_5.1.36-1_all.deb
0d9ca1595df1801286e9df03ab38763182fbf2444a3f42bb0464c6bf129b921a 60446
mysql-common_5.1.36-1_all.deb
212ea536178c8dc8a0ffa72fa0d0338ff1122126b2e8592520fc44e655c0bc2b 55068
mysql-server_5.1.36-1_all.deb
01c47078f14b518b571cc673673e9221b2f8e601702f82ba54ff95632f8613fb 54936
mysql-client_5.1.36-1_all.deb
e74cfbc7c6020da35324452817bf4f2cbad9a22723e65821e9d797d0c0f15f44 1953306
libmysqlclient16_5.1.36-1_amd64.deb
65b27dd8eaf10446273d393249ee4ccf5367a869eef1ea0ec72cf191b4766bf2 6678002
libmysqlclient-dev_5.1.36-1_amd64.deb
5af25a00a5fa01dd5c4ba5339026477b683a525c1665aa8cba419a88d753146d 9115414
mysql-client-5.1_5.1.36-1_amd64.deb
e743bbba3eac77237714718f50ff933acc1ddba6436f14bc938d41acba3f7510 10732690
mysql-server-5.1_5.1.36-1_amd64.deb
Files:
2e91cb7645287cc50125122d712fba74 1652 misc optional mysql-dfsg-5.1_5.1.36-1.dsc
02a83e864464b4ce78bda453061e6b32 18263034 misc optional
mysql-dfsg-5.1_5.1.36.orig.tar.gz
9e59959fd0e59d08024475a69e79f706 283528 misc optional
mysql-dfsg-5.1_5.1.36-1.diff.gz
73b60780efce81d54ae8c6a4fc997a86 54884 libdevel optional
libmysqlclient15-dev_5.1.36-1_all.deb
fca1cbc3e7ea7953cb881b356b8c5103 60446 database optional
mysql-common_5.1.36-1_all.deb
07c696ba56b2dd5911c85043644d9030 55068 database optional
mysql-server_5.1.36-1_all.deb
464af2e560a25bc4280d608549afcf85 54936 database optional
mysql-client_5.1.36-1_all.deb
958b6344244bc80c1e07269d1f5e62fe 1953306 libs optional
libmysqlclient16_5.1.36-1_amd64.deb
e579a7e9754714ff0388e44d02755238 6678002 libdevel optional
libmysqlclient-dev_5.1.36-1_amd64.deb
7bc700db8e7afa4e1602c4ed534e9ae7 9115414 misc optional
mysql-client-5.1_5.1.36-1_amd64.deb
4fa4b94879e00166d170d964d1d6ebf4 10732690 misc optional
mysql-server-5.1_5.1.36-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkpheVcACgkQr/RnCw96jQF5wwCeN//Hq/Q1V4PENEWX8gCquaaj
A5YAoJY0WU3eepppyD8kp5GsV/Vt/zf9
=oByX
-----END PGP SIGNATURE-----
--- End Message ---
