Your message dated Fri, 20 Jan 2012 12:47:33 +0000
with message-id <e1rodst-0008lh...@franck.debian.org>
and subject line Bug#641242: fixed in cp2k 2.1.637-2.1
has caused the Debian Bug report #641242,
regarding cp2k: FTBFS anywhere but (linux-)i386
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
641242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cp2k
Version: 2.1.637-2
Severity: serious
Justification: fails to build from source
The automatic builds of cp2k have all failed. On amd64 and ia64,
configure claims that the compiler cannot create executables, perhaps
on account of specifying -m32 without declaring the necessary build
dependencies (though I haven't actually looked at the source; that's
just a guess). The remaining architectures appear to be explicitly
unsupported, but the failure messages use an odd set of uname options:
have a look at cp2k/tools/get_arch_code
your system is a Linux-#1 Mon Aug 8 15:22:45 UTC 2011-2.6.32-armv5tel
but get_arch_code is not able to deal with that
Could you please take a look?
Thanks!
--- End Message ---
--- Begin Message ---
Source: cp2k
Source-Version: 2.1.637-2.1
We believe that the bug you reported is fixed in the latest version of
cp2k, which is due to be installed in the Debian FTP archive:
cp2k_2.1.637-2.1.debian.tar.gz
to main/c/cp2k/cp2k_2.1.637-2.1.debian.tar.gz
cp2k_2.1.637-2.1.dsc
to main/c/cp2k/cp2k_2.1.637-2.1.dsc
cp2k_2.1.637-2.1_amd64.deb
to main/c/cp2k/cp2k_2.1.637-2.1_amd64.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 641...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Aron Xu <a...@debian.org> (supplier of updated cp2k 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 ftpmas...@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 20 Jan 2012 19:59:16 +0800
Source: cp2k
Binary: cp2k
Architecture: source amd64
Version: 2.1.637-2.1
Distribution: unstable
Urgency: low
Maintainer: Debichem Team <debichem-de...@lists.alioth.debian.org>
Changed-By: Aron Xu <a...@debian.org>
Description:
cp2k - Ab Initio Molecular Dynamics
Closes: 641242
Changes:
cp2k (2.1.637-2.1) unstable; urgency=low
.
* Non-maintainer upload.
* Build-Depend on flex and bison, to fix FTBFS (Closes: #641242)
Checksums-Sha1:
1a1cfb0c149d0938bb77792964abb875c572180f 1673 cp2k_2.1.637-2.1.dsc
379cc5792f31fce281f71ca11f1b37866f5ad4fc 4892 cp2k_2.1.637-2.1.debian.tar.gz
d111888b30bc5df8c1407cd64d9548da24c6b3c9 9252642 cp2k_2.1.637-2.1_amd64.deb
Checksums-Sha256:
65ea02552b55976459f92221d4dea35b79b888f8808f86aa5cc4491b27e4f172 1673
cp2k_2.1.637-2.1.dsc
a73f825c18bca38af40cdb063016292e5e5f1853abc564b187fa5f5052eca5d1 4892
cp2k_2.1.637-2.1.debian.tar.gz
aff4c6f4bcedef0e3e817bcc508c76ab67da3396dab8d8fdf72751b0947ebf6b 9252642
cp2k_2.1.637-2.1_amd64.deb
Files:
e06089b061f957a8e24542bc409b30fa 1673 science optional cp2k_2.1.637-2.1.dsc
b15822fae2641bfae3bb00c76e953fc6 4892 science optional
cp2k_2.1.637-2.1.debian.tar.gz
75681e2ddc1c28c57012d2f45bcd0b09 9252642 science optional
cp2k_2.1.637-2.1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQEcBAEBCgAGBQJPGV+jAAoJEIAhAkTu07wNXH8IAMg+egFHxcQ/btYhCI+9n/Q6
zs2iRAn8NKQyY7Uf59ZGaZAonVlnZgkHN+5Zowm3Xtu7PjCWz4uRRW6VtAxGPpPG
eEOSeMGQmFB+koEVQgiRpL4enef8KJpXGA7N5yx0IXzJKZMZSph45lVOhki+9w6i
giNjqE8A64XryQFpU6XI3/ojBxmlQWLwh4/HPHViRPPtfyuunG7N19b7Gk8/dxQD
33cfStyOc7Tgjk/xuGVCW4/Ask3eJc/40i+2zOluuVKPxKM2ZPmrPxJj0J+wqZZN
dabF2q2Y6FaM+jGfmCKN04haKXF+Fl9ONnMdoNcXJRGErrD507UaZzdPkJfG2oI=
=EIyn
-----END PGP SIGNATURE-----
--- End Message ---
