Your message dated Tue, 12 Jun 2007 09:17:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#424644: fixed in blitz++ 1:0.9-4
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)

--- Begin Message ---
Package: libblitz0
Version: 1:0.9-3
Severity: grave
Justification: renders package unusable



When linking with the Blitz library, for instance with

g++ somesource.cpp -lblitz

I get the error:

/usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib64/libblitz.so: file not 
recognized: File format not recognized

The same applies to using nm on /usr/lib/libblitz.so.0.0.0

If the package is build locally from source, the error vanishes and everything 
is fine.




-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (700, 'stable'), (600, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages libblitz0 depends on:
ii  atlas3-base [libatlas.so.3]   3.6.0-20.6 Automatically Tuned Linear Algebra
ii  g++                           4:4.1.1-15 The GNU C++ compiler

libblitz0 recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
Source: blitz++
Source-Version: 1:0.9-4

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

blitz++_0.9-4.diff.gz
  to pool/main/b/blitz++/blitz++_0.9-4.diff.gz
blitz++_0.9-4.dsc
  to pool/main/b/blitz++/blitz++_0.9-4.dsc
libblitz-doc_0.9-4_all.deb
  to pool/main/b/blitz++/libblitz-doc_0.9-4_all.deb
libblitz0-dev_0.9-4_i386.deb
  to pool/main/b/blitz++/libblitz0-dev_0.9-4_i386.deb
libblitz0_0.9-4_i386.deb
  to pool/main/b/blitz++/libblitz0_0.9-4_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.
Andreas Tille <[EMAIL PROTECTED]> (supplier of updated blitz++ 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: Thu, 07 Jun 2007 11:20:23 +0200
Source: blitz++
Binary: libblitz0 libblitz0-dev libblitz-doc
Architecture: source all i386
Version: 1:0.9-4
Distribution: unstable
Urgency: low
Maintainer: Konstantinos Margaritis <[EMAIL PROTECTED]>
Changed-By: Andreas Tille <[EMAIL PROTECTED]>
Description: 
 libblitz-doc - C++ template class library for scientific computing
 libblitz0  - C++ template class library for scientific computing
 libblitz0-dev - C++ template class library for scientific computing
Closes: 424644
Changes: 
 blitz++ (1:0.9-4) unstable; urgency=low
 .
   * Simple reupload that triggers recompile on AMD64
     Closes: #424644
Files: 
 569bcf092976a2975a8f5f29ae2368ea 800 devel extra blitz++_0.9-4.dsc
 24c12185b5ead11e73454dd2a7ca6b60 12320 devel extra blitz++_0.9-4.diff.gz
 7d1df700a82afee75cbed67c1ed18e01 1467932 doc extra libblitz-doc_0.9-4_all.deb
 56ea8c1104553ee9ff9a33c443bebb87 111294 libs extra libblitz0_0.9-4_i386.deb
 9a7c392053f5fe2450f21807c5e21322 305568 devel extra 
libblitz0-dev_0.9-4_i386.deb

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

iD8DBQFGbmEsYDBbMcCf01oRAkJ0AJ449nLJ+L6ploKGePhSzu2EHPUqfACgvPD5
k+g80r6grA4Ii6iGQsturLw=
=8p/1
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to