Your message dated Sat, 18 Jul 2009 07:47:15 +0000
with message-id <[email protected]>
and subject line Bug#447713: fixed in mysql-dfsg-5.1 5.1.36-1
has caused the Debian Bug report #447713,
regarding mysql-server-5.0: mysqld chrashes with signal 11, 3-4 times a week
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.)
--
447713: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447713
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server-5.0
Version: 5.0.45-1
Severity: important
One of my mysql server crashes 3-4 times a week, with signal 11. I
downloaded mysql-5.0.45-linux-i686.tar.gz from mysql.com and this server
runs without any problems, with the same command line.
The diff of the mysqladmin variables:
| expire_logs_days | 0 | |
expire_logs_days | 10
| have_dynamic_loading | NO | |
have_dynamic_loading | YES
| have_example_engine | YES | |
have_example_engine | NO
| key_buffer_size | 8388600 | |
key_buffer_size | 16777216
| log_bin | OFF | | log_bin
| ON
| max_allowed_packet | 1048576 | |
max_allowed_packet | 16776192
| max_binlog_size | 1073741824 | |
max_binlog_size | 104857600
| query_cache_size | 0 | |
query_cache_size | 16777216
| server_id | 0 | | server_id
| 1
| storage_engine | MyISAM | |
storage_engine | InnoDB
| table_type | MyISAM | | table_type
| InnoDB
| thread_cache_size | 0 | |
thread_cache_size | 8
| thread_stack | 126976 | |
thread_stack | 131072
| tmpdir | /tmp/ | | tmpdir
| /tmp
| version | 5.0.45 | | version
| 5.0.45-Debian_1-log
| version_comment | MySQL Community Server (GPL) | |
version_comment | Debian etch distribution
| version_compile_machine | i686 | |
version_compile_machine | i486
The crashs couldn't be connected to a particular query.
The resolve_stack_dump produces always the same output:
resolve_stack_dump -s mysqld.sym -n /root/mysql_crash_dump | c++filt
0x81ee880 get_one_option(int, my_option const*, char*) + 208
0xb7cf4bdf _end + -1352870937
0x824bf35 select_describe(JOIN*, bool, bool, bool, char const*) + 821
0x824cfba select_describe(JOIN*, bool, bool, bool, char const*) + 5050
0x8254c86 select_insert::prepare(List<Item>&, st_select_lex_unit*) + 1030
0x82556af delayed_insert::handle_inserts() + 1487
0x8207673 dispatch_command(enum_server_command, THD*, char*, unsigned int) + 339
0x820ab60 MYSQLparse(void*) + 672
0x820b119 MYSQLparse(void*) + 2137
The reportbug failed to exec debconf-show, but here is the output of
debconf-show mysql-server-5.0 executed from console:
* 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
The log entrys:
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 071023 8:33:06 - mysqld got
signal 11;
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: This could be because you hit a
bug. It is also possible that this binary
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: or one of the libraries it was
linked against is corrupt, improperly built,
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: or misconfigured. This error
can also be caused by malfunctioning hardware.
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: We will try our best to scrape
up some info that will hopefully help diagnose
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: the problem, but since we have
already crashed, something is definitely wrong
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: and this may fail.
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]:
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: key_buffer_size=8384512
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: read_buffer_size=131072
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: max_used_connections=101
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: max_connections=100
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: threads_connected=22
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: It is possible that mysqld
could use up to
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: key_buffer_size +
(read_buffer_size + sort_buffer_size)*max_connections = 225787 K
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: bytes of memory
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: Hope that's ok; if not,
decrease some variables in the equation.
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]:
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: thd=0xb1024de8
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: Attempting backtrace. You can
use the following information to find out
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: where mysqld died. If you see
no messages after this, something went
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: terribly wrong...
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: Cannot determine thread,
fp=0xb235b718, backtrace may not be correct.
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: Stack range sanity check OK,
backtrace follows:
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0x81ee880
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0xb7c76bdf
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0x824bf35
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0x824cfba
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0x8254c86
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0x82556af
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0x8207673
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0x820ab60
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0x820b119
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0x820c4a7
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0x820cfe0
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0xb7eb52d3
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: 0xb7cd82fe
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: New value of fp=(nil) failed
sanity check, terminating stack trace!
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: Please read
http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow
instructions on how to resolve the stack trace. Resolved
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: stack trace is much more
helpful in diagnosing the problem, so please do
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: resolve it
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: Trying to get some variables.
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: Some pointers may be invalid
and cause the dump to abort...
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: thd->query at 0x8f8bae0 =
SELECT id,nick,note,UNIX_TIMESTAMP(crdate),email FROM guestbook ORDER BY crdate
DESC LIMIT 9780,12
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: thd->thread_id=101407
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: The manual page at
http://www.mysql.com/doc/en/Crashing.html contains
Oct 23 08:33:06 s...@mamba/mamba mysqld[18829]: information that should help
you find out what is causing the crash.
Oct 23 08:33:06 s...@mamba/mamba mysqld_safe[25374]: Number of processes
running now: 0
Oct 23 08:33:06 s...@mamba/mamba mysqld_safe[29681]: restarted
Oct 23 08:33:06 s...@mamba/mamba mysqld[29117]: 071023 8:33:06 InnoDB:
Database was not shut down normally!
Oct 23 08:33:06 s...@mamba/mamba mysqld[29117]: InnoDB: Starting crash recovery.
Oct 23 08:33:06 s...@mamba/mamba mysqld[29117]: InnoDB: Reading tablespace
information from the .ibd files...
Oct 23 08:33:06 s...@mamba/mamba mysqld[29117]: InnoDB: Restoring possible
half-written data pages from the doublewrite
Oct 23 08:33:06 s...@mamba/mamba mysqld[29117]: InnoDB: buffer...
Oct 23 08:33:06 s...@mamba/mamba mysqld[29117]: 071023 8:33:06 InnoDB:
Starting log scan based on checkpoint at
Oct 23 08:33:06 s...@mamba/mamba mysqld[29117]: InnoDB: log sequence number 0
3801045577.
Oct 23 08:33:06 s...@mamba/mamba mysqld[29117]: InnoDB: Doing recovery: scanned
up to log sequence number 0 3801046010
Oct 23 08:33:06 s...@mamba/mamba mysqld[29117]: 071023 8:33:06 InnoDB:
Starting an apply batch of log records to the database...
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: InnoDB: Progress in percents:
71 72 73 74 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
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: InnoDB: Apply batch completed
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: InnoDB: In a MySQL replication
slave the last master binlog file
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: InnoDB: position 0 139, file
name mysql-bin.000672
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: InnoDB: Last MySQL binlog file
position 0 1368536, file name /var/log/mysql/mysql-bin.000694
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 InnoDB:
Started; log sequence number 0 3801046010
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Note]
Recovering after a crash using /var/log/mysql/mysql-bin
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Note] Starting
crash recovery...
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Note] Crash
recovery finished.
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Warning] Found
invalid password for user: 'swfto...@localhost'; Ignoring user
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Warning] Found
invalid password for user: 'designfo...@localhost'; Ignoring user
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Warning] Found
invalid password for user: 'ads...@localhost'; Ignoring user
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Warning] Found
invalid password for user: 'designad...@localhost'; Ignoring user
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Warning] Found
invalid password for user: '[email protected]'; Ignoring user
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Warning] Found
invalid password for user: '[email protected]'; Ignoring user
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Warning] Found
invalid password for user: '[email protected]'; Ignoring user
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Warning] Found
invalid password for user: '[email protected]'; Ignoring user
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Warning]
Neither --relay-log nor --relay-log-index were used; so replication may
break when this MySQL server acts as a slave and has his hostname changed!!
Please use '--relay-log=/var/run/mysqld/mysqld-relay-bin' to avoid this problem.
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Note]
/usr/sbin/mysqld: ready for connections.
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: Version: '5.0.45-Debian_1-log'
socket: '/var/run/mysqld/mysqld.sock' port: 3306 Debian etch distribution
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Note] Slave
SQL thread initialized, starting replication in log
'mysql-bin.000691' at position 98, relay log
'/var/run/mysqld/mysqld-relay-bin.000552' position: 235
Oct 23 08:33:07 s...@mamba/mamba mysqld[29117]: 071023 8:33:07 [Note] Slave
I/O thread: connected to master 'ma...@empire2:3306', replication
started in log 'mysql-bin.000691' at position 98
Oct 23 09:39:57 s...@mamba/mamba mysqld[29117]: 071023 9:39:57 InnoDB: Error:
trying to declare trx to enter InnoDB, but
Oct 23 09:39:57 s...@mamba/mamba mysqld[29117]: InnoDB: it already is declared.
Oct 23 09:39:57 s...@mamba/mamba mysqld[29117]: TRANSACTION 0 45812224, ACTIVE
0 sec, process no 6713, OS thread id 2987260816, thread declared inside InnoDB 0
Oct 23 09:39:57 s...@mamba/mamba mysqld[29117]: mysql tables in use 1, locked 1
Oct 23 09:39:57 s...@mamba/mamba mysqld[29117]: 1 lock struct(s), heap size 320
Oct 23 09:39:57 s...@mamba/mamba mysqld[29117]: MySQL thread id 1657, query id
31656 mamba.csn.hu 217.13.33.12 intrnews update
Oct 23 09:39:57 s...@mamba/mamba mysqld[29117]: INSERT INTO ad_log (ip,
aduserid, action, hely) VALUES ('catv-5985a08c.catv.broadband.hu', '19',
'view', 'intercoolforumfelul')
Oct 23 09:39:57 s...@mamba/mamba mysqld[29117]:
Regards,
Zsolt
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.18.1-grsec-srv20 (SMP w/1 CPU core; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages mysql-server-5.0 depends on:
ii adduser 3.105 add and remove users and groups
ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy
ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries
ii libdbi-perl 1.59-1 Perl5 database interface by Tim Bu
ii libgcc1 1:4.2.1-4 GCC support library
ii libmysqlclient15off 5.0.45-1 MySQL database client library
ii libncurses5 5.6+20070908-1 Shared libraries for terminal hand
ii libreadline5 5.2-3 GNU readline and history libraries
ii libstdc++6 4.2.1-4 The GNU Standard C++ Library v3
ii libwrap0 7.6.dbs-14 Wietse Venema's TCP wrappers libra
ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip
ii mysql-client-5.0 5.0.45-1 MySQL database client binaries
ii mysql-common 5.0.45-1 MySQL database common files
ii passwd 1:4.0.18.1-11 change and administer password and
ii perl 5.8.8-7 Larry Wall's Practical Extraction
ii psmisc 22.5-1 Utilities that use the proc filesy
ii zlib1g 1:1.2.3.3.dfsg-6 compression library - runtime
Versions of packages mysql-server-5.0 recommends:
ii mailx 1:8.1.2-0.20070424cvs-1 A simple mail user agent
-- debconf-show failed
--- 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 ---
