Your message dated Tue, 13 Dec 2005 14:10:09 +0100
with message-id <[EMAIL PROTECTED]>
and subject line closing
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 2 Dec 2005 11:41:22 +0000
>From [EMAIL PROTECTED] Fri Dec 02 03:41:22 2005
Return-path: <[EMAIL PROTECTED]>
Received: from xwis.net ([195.13.63.187])
by spohr.debian.org with esmtp (Exim 4.50)
id 1Ei9I1-0006yj-JE
for [EMAIL PROTECTED]; Fri, 02 Dec 2005 03:41:21 -0800
Received: from olaf by xwis.net with local (Exim 4.54)
id 1Ei9Hz-0004Rw-CX; Fri, 02 Dec 2005 12:41:19 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Olaf van der Spek <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mysql-server-5.0: Server crashing
X-Mailer: reportbug 3.17
Date: Fri, 02 Dec 2005 12:41:19 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: mysql-server-5.0
Version: 5.0.13rc-1
Severity: grave
Justification: causes non-serious data loss
Hi,
I just upgraded a server from 4.1 to 5.0 and now the MySQL server keeps
crashing.
The 5.0 version in testing is pre-stable and two months old.
I'm aware of the gcc dependency issue and asked vorlon on IRc about it:
[12:35] <vorlon> XTF: doing *anything* to try to circumvent the
dependencies your package picks up when built in a pristine unstable
environment is wrong.
If there's a significant RC bug in a package that you're trying to get
fixed, testing-proposed-updates is an option, but if it's a C++-related
package that won't work either.
So would testing-proposed-updates be an option?
I think the gcc issue might last a few weeks at least.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-686-smp
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Versions of packages mysql-server-5.0 depends on:
ii adduser 3.79 Add and remove users and groups
ii debconf [debconf 1.4.59 Debian configuration management sy
ii libc6 2.3.5-8 GNU C Library: Shared libraries an
ii libdbi-perl 1.48-2 Perl5 database interface by Tim Bu
ii libgcc1 1:4.0.2-2 GCC support library
ii libmysqlclient15 5.0.13rc-1 mysql database client library
ii libncurses5 5.5-1 Shared libraries for terminal hand
ii libreadline5 5.0-11 GNU readline and history libraries
ii libstdc++6 4.0.2-2 The GNU Standard C++ Library v3
ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra
ii mailx 1:8.1.2-0.20050715cvs-1 A simple mail user agent
ii mysql-client-5.0 5.0.13rc-1 mysql database client binaries
ii mysql-common 5.0.13rc-1 mysql database common files (e.g.
ii passwd 1:4.0.13-7 change and administer password and
ii perl 5.8.7-7 Larry Wall's Practical Extraction
ii psmisc 21.8-1 Utilities that use the proc filesy
ii zlib1g 1:1.2.3-8 compression library - runtime
mysql-server-5.0 recommends no packages.
-- debconf information:
mysql-server-5.0/really_downgrade: false
mysql-server-5.0/start_on_boot: true
mysql-server-5.0/mysql_update_hints1:
mysql-server-5.0/nis_warning:
mysql-server-5.0/postrm_remove_databases: false
* mysql-server-5.0/mysql_install_db_notes:
---------------------------------------
Received: (at 341705-done) by bugs.debian.org; 13 Dec 2005 13:10:13 +0000
>From [EMAIL PROTECTED] Tue Dec 13 05:10:13 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail3b.westend.com ([212.117.79.78] helo=mail3b1.westend.com)
by spohr.debian.org with esmtp (Exim 4.50)
id 1Em9v3-0000ys-4T
for [EMAIL PROTECTED]; Tue, 13 Dec 2005 05:10:13 -0800
Received: from localhost (localhost [127.0.0.1])
by mail3b1.westend.com (Postfix) with ESMTP id 933CABF32
for <[EMAIL PROTECTED]>; Tue, 13 Dec 2005 14:10:11 +0100 (CET)
Received: from mail3b1.westend.com ([127.0.0.1])
by localhost (mail3b [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 22626-07 for <[EMAIL PROTECTED]>;
Tue, 13 Dec 2005 14:10:09 +0100 (CET)
Received: by mail3b1.westend.com (Postfix, from userid 1000)
id 818AFBF3C; Tue, 13 Dec 2005 14:10:09 +0100 (CET)
Date: Tue, 13 Dec 2005 14:10:09 +0100
From: Christian Hammers <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: closing
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-2.0 required=4.0 tests=BAYES_00,ONEWORD autolearn=no
version=2.60-bugs.debian.org_2005_01_02
5.0.16 is ready to go into testing but held by this bug.
I was under the impression that tagging it as "notfound 5.0.16"
would be sufficient but it seems not to be.
Olaf, if the problem persists, contact me then I will reopen the bug,
of course.
bye,
-christian-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
