Your message dated Sun, 3 Jul 2016 11:46:27 +0200
with message-id <[email protected]>
and subject line closing bugs reported against ancient mysql-5.1
has caused the Debian Bug report #574514,
regarding mysql-server-5.1: mysqlhotcopy - can't use locks with log tables
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.)


-- 
574514: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574514
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server-5.1
Version: 5.1.44-3~bpo50+1
Severity: normal


mysql-zrm complained with an error from mysqlhotcopy:

dailyrun:backup:ERROR: Output of command: 'mysqlhotcopy' is {
DBD::mysql::db do failed: You can't use locks with log tables. at 
/usr/bin/mysqlhotcopy line 452.
}

Here is the upstream bug report which includes a patch:

http://bugs.mysql.com/bug.php?id=43594

I checked the latest source package from sid before filing this report.

-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-bpo.1-amd64 (SMP w/3 CPU cores)
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.1 depends on:
ii  adduser                3.110             add and remove users and groups
ii  debconf [debconf-2.0]  1.5.24            Debian configuration management sy
ii  libc6                  2.7-18lenny2      GNU C Library: Shared libraries
ii  libdbi-perl            1.605-1           Perl5 database interface by Tim Bu
ii  libgcc1                1:4.3.4-6~bpo50+1 GCC support library
ii  libmysqlclient16       5.1.44-3~bpo50+1  MySQL database client library
ii  libstdc++6             4.3.4-6~bpo50+1   The GNU Standard C++ Library v3
ii  libwrap0               7.6.q-16          Wietse Venema's TCP wrappers libra
ii  lsb-base               3.2-20            Linux Standard Base 3.2 init scrip
ii  mysql-client-5.1       5.1.44-3~bpo50+1  MySQL database client binaries
ii  mysql-common           5.1.44-3~bpo50+1  MySQL database common files (e.g. 
ii  passwd                 1:4.1.1-6+lenny1  change and administer password and
ii  perl                   5.10.0-19lenny2   Larry Wall's Practical Extraction 
ii  psmisc                 22.6-1            Utilities that use the proc filesy
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages mysql-server-5.1 recommends:
ii  bsd-mailx [mailx]  8.1.2-0.20071201cvs-3 A simple mail user agent
ii  libhtml-template-p 2.9-1                 HTML::Template : A module for usin

Versions of packages mysql-server-5.1 suggests:
ii  tinyca                        0.7.5-2    simple graphical program for certi

-- debconf information:
* mysql-server/root_password_again: (password omitted)
* mysql-server/root_password: (password omitted)
  mysql-server/error_setting_password:
  mysql-server-5.1/start_on_boot: true
  mysql-server-5.1/postrm_remove_databases: false
  mysql-server-5.1/nis_warning:
  mysql-server-5.1/really_downgrade: false
  mysql-server/password_mismatch:
  mysql-server/no_upgrade_when_using_ndb:



--- End Message ---
--- Begin Message ---
This bug has been reported against an ancient version of mysql (5.1),
that was last released with Debian 6.0 (squeeze). But even squeeze-lts
has now reached end-of-life and is no longer supported.
The bug is assumed to be fixed (or no longer relevant) in newer mysql
(or mariadb) releases and therefore I'm closing this report now. If the
problem is still reproducible in the currently supported versions
(mysql-5.6/mysql-5.7), feel free to provide more information, reopen
and reassign this bug report.

Andreas

--- End Message ---

Reply via email to