Your message dated Fri, 19 Aug 2005 07:02:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#299166: fixed in mysql-ruby 2.6.3-1
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; 12 Mar 2005 08:17:13 +0000
>From [EMAIL PROTECTED] Sat Mar 12 00:17:13 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (minbar.dodds.net)
[66.93.39.86] (postfix)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DA1o8-0007VX-00; Sat, 12 Mar 2005 00:17:13 -0800
Received: by minbar.dodds.net (Postfix, from userid 1000)
id 040F51A103; Sat, 12 Mar 2005 00:17:11 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Steve Langasek <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: mysql-ruby must be rebuilt against libmysqlclient12
X-Mailer: reportbug 3.8
Date: Sat, 12 Mar 2005 00:17:11 -0800
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: mysql-ruby
Severity: grave
Packages connected to apache, odbc, and scripting languages
(python/perl/php/ruby) are in the process of transitioning from
libmysqlclient10 to libmysqlclient12 for sarge. Because libmysqlclient
does not include versioned symbols, it is not possible for multiple
versions of this library to be loaded by a process without causing
segfaults. Since libmysql-ruby1.6 and libmysql-ruby1.8 will be loaded
by processes that may also have loaded libmysqlclient12, depending on
libmysqlclient10 is therefore a grave bug in mysql-ruby.
Please rebuild mysql-ruby against libmysqlclient12 by updating your
build depends to point to libmysqlclient12-dev.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
---------------------------------------
Received: (at 299166-close) by bugs.debian.org; 19 Aug 2005 14:21:01 +0000
>From [EMAIL PROTECTED] Fri Aug 19 07:21:01 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1E67Ri-0001Z3-00; Fri, 19 Aug 2005 07:02:10 -0700
From: Dmitry Borodaenko <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#299166: fixed in mysql-ruby 2.6.3-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 19 Aug 2005 07:02:10 -0700
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 2
Source: mysql-ruby
Source-Version: 2.6.3-1
We believe that the bug you reported is fixed in the latest version of
mysql-ruby, which is due to be installed in the Debian FTP archive:
libmysql-ruby1.8_2.6.3-1_i386.deb
to pool/main/m/mysql-ruby/libmysql-ruby1.8_2.6.3-1_i386.deb
libmysql-ruby_2.6.3-1_all.deb
to pool/main/m/mysql-ruby/libmysql-ruby_2.6.3-1_all.deb
mysql-ruby_2.6.3-1.diff.gz
to pool/main/m/mysql-ruby/mysql-ruby_2.6.3-1.diff.gz
mysql-ruby_2.6.3-1.dsc
to pool/main/m/mysql-ruby/mysql-ruby_2.6.3-1.dsc
mysql-ruby_2.6.3.orig.tar.gz
to pool/main/m/mysql-ruby/mysql-ruby_2.6.3.orig.tar.gz
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.
Dmitry Borodaenko <[EMAIL PROTECTED]> (supplier of updated mysql-ruby 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.7
Date: Fri, 19 Aug 2005 14:50:10 +0300
Source: mysql-ruby
Binary: libmysql-ruby libmysql-ruby1.8
Architecture: source all i386
Version: 2.6.3-1
Distribution: unstable
Urgency: low
Maintainer: Dmitry Borodaenko <[EMAIL PROTECTED]>
Changed-By: Dmitry Borodaenko <[EMAIL PROTECTED]>
Description:
libmysql-ruby - MySQL module for Ruby
libmysql-ruby1.8 - MySQL module for Ruby 1.8
Closes: 276719 299166
Changes:
mysql-ruby (2.6.3-1) unstable; urgency=low
.
* New upstream version. Closes: #276719.
* Acknowledged NMU by Steve Langasek. Closes: #299166.
* Removed ruby1.6 version of the library due to pending removal of ruby1.6.
* Fixed a glitch in copyright file.
* Removed obsolete examples and tomito-extconf.rb patch.
Files:
04ca0c8650d31841c45980485643e076 647 interpreters optional
mysql-ruby_2.6.3-1.dsc
46aa76b8f6167d227446c244446e2e37 20522 interpreters optional
mysql-ruby_2.6.3.orig.tar.gz
e57e195ec99aa26c0885efdd7ec4192f 4392 interpreters optional
mysql-ruby_2.6.3-1.diff.gz
a99855159199b9703fc6767ca19deff3 4762 interpreters optional
libmysql-ruby_2.6.3-1_all.deb
936933c3af30654224ff2b9d69e8db65 30398 interpreters optional
libmysql-ruby1.8_2.6.3-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iEYEARECAAYFAkMFyEQACgkQxhqJXoXuPg77TACguE4g5Woo2AqL5wb3MY/oi1Eh
FPYAnigk1qgVw1gQ8M5T0LXNLWdaKc4+
=PQq5
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
