Your message dated Wed, 30 Mar 2005 01:47:08 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#302032: fixed in arpack++ 2.2-3
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; 29 Mar 2005 19:25:11 +0000
>From [EMAIL PROTECTED] Tue Mar 29 11:25:10 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c129020.adsl.hansenet.de (localhost.localdomain) [213.39.129.20] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DGMKs-0004si-00; Tue, 29 Mar 2005 11:25:10 -0800
Received: from aj by localhost.localdomain with local (Exim 4.50)
        id 1DGMKt-0006VC-Oi; Tue, 29 Mar 2005 21:25:11 +0200
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
From: Andreas Jochens <[EMAIL PROTECTED]>
Subject: arpack++: FTBFS: Missing Build-Depends on 'libg2c0-dev, blas-dev, 
lapack3-dev, libarpack2-dev'
Message-Id: <[EMAIL PROTECTED]>
Date: Tue, 29 Mar 2005 21:25:11 +0200
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: arpack++
Version: 2.2-1
Severity: serious
Tags: patch

When building 'arpack++' in a clean 'unstable' chroot,
I get the following error:

checking dependency style of gcc... gcc3
checking for log in -lm... yes
checking for s_copy in -lg2c... no
you need g2c.
make: *** [build] Error 1

Please add the missing Build-Depends on 
'libg2c0-dev, blas-dev, lapack3-dev, libarpack2-dev'
to debian/control.

Regards
Andreas Jochens

diff -urN ../tmp-orig/arpack++-2.2/debian/control ./debian/control
--- ../tmp-orig/arpack++-2.2/debian/control     2005-03-29 21:08:53.569587855 
+0200
+++ ./debian/control    2005-03-29 21:08:51.403993892 +0200
@@ -1,7 +1,7 @@
 Source: arpack++
 Section: math
 Priority: optional
-Build-Depends: debhelper ( >= 4 ), g++ ( >> 2.95 )
+Build-Depends: debhelper ( >= 4 ), libg2c0-dev, blas-dev, lapack3-dev, 
libarpack2-dev
 Maintainer: Christophe Prud'homme <[EMAIL PROTECTED]>
 Standards-Version: 3.6.1
 

---------------------------------------
Received: (at 302032-close) by bugs.debian.org; 30 Mar 2005 06:55:20 +0000
>From [EMAIL PROTECTED] Tue Mar 29 22:55:20 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 1DGX6l-0005uS-00; Tue, 29 Mar 2005 22:55:19 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DGWyq-0004Cu-00; Wed, 30 Mar 2005 01:47:08 -0500
From: Christophe Prud'homme <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#302032: fixed in arpack++ 2.2-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 30 Mar 2005 01:47:08 -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: arpack++
Source-Version: 2.2-3

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

arpack++_2.2-3.diff.gz
  to pool/main/a/arpack++/arpack++_2.2-3.diff.gz
arpack++_2.2-3.dsc
  to pool/main/a/arpack++/arpack++_2.2-3.dsc
libarpack++2-dev_2.2-3_i386.deb
  to pool/main/a/arpack++/libarpack++2-dev_2.2-3_i386.deb
libarpack++2_2.2-3_i386.deb
  to pool/main/a/arpack++/libarpack++2_2.2-3_i386.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.
Christophe Prud'homme <[EMAIL PROTECTED]> (supplier of updated arpack++ 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: Wed, 30 Mar 2005 08:19:00 +0200
Source: arpack++
Binary: libarpack++2-dev libarpack++2
Architecture: source i386
Version: 2.2-3
Distribution: unstable
Urgency: low
Maintainer: Christophe Prud'homme <[EMAIL PROTECTED]>
Changed-By: Christophe Prud'homme <[EMAIL PROTECTED]>
Description: 
 libarpack++2 - Object-oriented version of the ARPACK package (runtime)
 libarpack++2-dev - Object-oriented version of the ARPACK package (development)
Closes: 302032 302094
Changes: 
 arpack++ (2.2-3) unstable; urgency=low
 .
   * really fix build-depends
   * FTBFS: Missing Build-Depends on 'libg2c0-dev, blas-dev, lapack3-dev,
     libarpack2-dev' (closes: #302032)
   * FTBFS: you need blas (closes: #302094)
Files: 
 597ee3c680147a34a3ee74bd4ee0a475 656 devel optional arpack++_2.2-3.dsc
 860559d9fdf5ae2b7e402f266997d2dc 2701 devel optional arpack++_2.2-3.diff.gz
 021e471ae8db86b1993f8ef64c3c0a27 7128 libs optional libarpack++2_2.2-3_i386.deb
 bd6454b1134d5cf10885c46c65942694 422024 libdevel optional 
libarpack++2-dev_2.2-3_i386.deb

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

iD8DBQFCSka6oY+0C9S+FFARAmmFAJ4rHygWwpcjKl380NKPxbZTu8HQVQCgjZcb
GXo/f6N5NXugNwl8aBTf8cg=
=q91y
-----END PGP SIGNATURE-----


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

Reply via email to