Your message dated Sun, 20 Mar 2005 05:02:31 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#300390: fixed in libdb2-ruby 0.5.4-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; 19 Mar 2005 12:57:39 +0000
>From [EMAIL PROTECTED] Sat Mar 19 04:57:39 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail-out.m-online.net [212.18.0.9] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DCdWN-0008KG-00; Sat, 19 Mar 2005 04:57:39 -0800
Received: from mail.m-online.net (svr20.m-online.net [192.168.3.148])
        by mail-out.m-online.net (Postfix) with ESMTP id 543506F82;
        Sat, 19 Mar 2005 13:57:38 +0100 (CET)
Received: from atari.stigge.org (ppp-82-135-2-178.mnet-online.de [82.135.2.178])
        by mail.m-online.net (Postfix) with ESMTP id 01F075F9DF;
        Sat, 19 Mar 2005 13:57:31 +0100 (CET)
Received: from [192.168.5.99] (localhost [127.0.0.1])
        by atari.stigge.org (Postfix) with ESMTP id B521E100B945E;
        Sat, 19 Mar 2005 13:57:31 +0100 (CET)
From: Roland Stigge <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: libdb2-ruby: FTBFS: extconf.rb failed
Message-Id: <[EMAIL PROTECTED]>
Date: Sat, 19 Mar 2005 13:57:31 +0100 (CET)
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: libdb2-ruby
Version: 0.5.3-1
Severity: serious

Hi,

building the package libdb2-ruby in a clean build environment
(with pbuilder) on i386 results in:

=========================================================================
[...]
dh_testdir
rm -rf build-tree-1.6 build-tree-1.8
tar -zcf debian/src.tgz Changes README.en bdb.html bdb.rd bdbxml docs examples 
extconf.rb src tests tmp util
mkdir build-tree-1.6 build-tree-1.8
tar -C build-tree-1.6 -zxf debian/src.tgz
tar -C build-tree-1.8 -zxf debian/src.tgz
ruby1.6 -C build-tree-1.6 extconf.rb --with-db-version=2
extconf.rb: Entering directory `src'
checking for db_version() in -ldb2... yes
creating Makefile
extconf.rb: Leaving directory `src'
ruby1.8 -C build-tree-1.8 extconf.rb --with-db-version=2
extconf.rb: Entering directory `src'
checking for db_version() in -ldb2... yes
creating Makefile
extconf.rb: Leaving directory `src'
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of
necessary libraries and/or headers.  Check the mkmf.log file for more
details.  You may need configuration options.

Provided configuration options:
        --with-opt-dir
        --with-opt-include=${opt-dir}/include
        --with-opt-lib=${opt-dir}/lib
        --with-make-prog=make
        --srcdir=.
        --curdir=/tmp/buildd/libdb2-ruby-0.5.3/build-tree-1.8
        --ruby=/usr/bin/ruby1.8
make: *** [configure-stamp] Error 1
=========================================================================

build-tree-1.8/src/mkmf.log looks like this:

=========================================================================
have_library: checking for db_version() in -ldb2... -------------------- yes

"gcc -o conftest -I/home/ernie/temp/debian/libdb2-ruby-0.5.3/build-tree-1.8/src 
-I/usr/lib/ruby/1.8/i386-linux -I/usr/include  -Wall -g -O2  -fPIC conftest.c  
-L"/usr/lib" -L"/usr/lib"      -lruby1.8-static -ldb2  -lpthread -ldl -lcrypt 
-lm   -lc"
conftest.c: In function `t':
conftest.c:4: warning: implicit declaration of function `db_version'
checked program was:
/* begin */

/*top*/
int main() { return 0; }
int t() { db_version(); return 0; }
/* end */

--------------------
=========================================================================

Thanks for considering.


--
DARTS - Debian Archive Regression Test Suite
http://darts.alioth.debian.org/

Please note that this report has not been generated fully automatically.
DARTS just helped finding the problem.

---------------------------------------
Received: (at 300390-close) by bugs.debian.org; 20 Mar 2005 10:12:06 +0000
>From [EMAIL PROTECTED] Sun Mar 20 02:12:06 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DCxPh-00056S-00; Sun, 20 Mar 2005 02:12:05 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DCxGR-0005Ai-00; Sun, 20 Mar 2005 05:02:31 -0500
From: akira yamada <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#300390: fixed in libdb2-ruby 0.5.4-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 20 Mar 2005 05:02:31 -0500
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=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Source: libdb2-ruby
Source-Version: 0.5.4-1

We believe that the bug you reported is fixed in the latest version of
libdb2-ruby, which is due to be installed in the Debian FTP archive:

libdb2-ruby1.6_0.5.4-1_i386.deb
  to pool/main/libd/libdb2-ruby/libdb2-ruby1.6_0.5.4-1_i386.deb
libdb2-ruby1.8_0.5.4-1_i386.deb
  to pool/main/libd/libdb2-ruby/libdb2-ruby1.8_0.5.4-1_i386.deb
libdb2-ruby_0.5.4-1.diff.gz
  to pool/main/libd/libdb2-ruby/libdb2-ruby_0.5.4-1.diff.gz
libdb2-ruby_0.5.4-1.dsc
  to pool/main/libd/libdb2-ruby/libdb2-ruby_0.5.4-1.dsc
libdb2-ruby_0.5.4.orig.tar.gz
  to pool/main/libd/libdb2-ruby/libdb2-ruby_0.5.4.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.
akira yamada <[EMAIL PROTECTED]> (supplier of updated libdb2-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: Sun, 20 Mar 2005 18:11:01 +0900
Source: libdb2-ruby
Binary: libdb2-ruby1.8 libdb2-ruby1.6
Architecture: source i386
Version: 0.5.4-1
Distribution: unstable
Urgency: high
Maintainer: akira yamada <[EMAIL PROTECTED]>
Changed-By: akira yamada <[EMAIL PROTECTED]>
Description: 
 libdb2-ruby1.6 - Interface to Berkeley DB for Ruby 1.6
 libdb2-ruby1.8 - Interface to Berkeley DB for Ruby 1.8
Closes: 300390
Changes: 
 libdb2-ruby (0.5.4-1) unstable; urgency=high
 .
   * new upstream version.
   * extconf.rb: added "$makefile_created = true" to avoid "extconf.rb
     failed".  (closes: #300390)
Files: 
 fa9d4ff0819ca8edb9e4f3b596f0e166 650 interpreters optional 
libdb2-ruby_0.5.4-1.dsc
 b85ea8f645cdacee70fa46cc6d61754c 268068 interpreters optional 
libdb2-ruby_0.5.4.orig.tar.gz
 0ce1176aa1acf37a795a91c14818b652 5447 interpreters optional 
libdb2-ruby_0.5.4-1.diff.gz
 7ce962bd354be5dab00f5fce7e58024d 160224 interpreters optional 
libdb2-ruby1.6_0.5.4-1_i386.deb
 94362bd1b662703fb0fcd50a0f8f61a2 160378 interpreters optional 
libdb2-ruby1.8_0.5.4-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCPULuXzkxpuIT8aARAnEyAJ9M7UslfNjAZPoRU+QhB5vRXA4GWgCfcXBs
/qOoPBTczoQIqWNNhK29qJE=
=wy7V
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to