Your message dated Tue, 18 Oct 2016 17:19:30 +0000
with message-id <e1bwy30-0007ph...@franck.debian.org>
and subject line Bug#840016: fixed in aoflagger 2.8.0-2
has caused the Debian Bug report #840016,
regarding aoflagger: FTBFS on non-x86
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.)


-- 
840016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: aoflagger
Version: 2.8.0-1
Severity: important
Justification: fails to build from source

Builds of aoflagger for non-x86 architectures have been failing due
to the unconditional use of <xmmintrin.h> and the insufficiently
conditional use of -msse2 (observed on the non-release architecture
sparc64).  Since casacore still FTBFS on most architectures, that
leaves amd64 as the only architecture on which aoflagger successfully
builds.

Could you please take a look and either fix aoflagger to build on a
wider range of architectures (subject to B-D avaiability) or, if
that's infeasible, restrict its Architecture field so the autobuilders
don't waste time on it?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

--- End Message ---
--- Begin Message ---
Source: aoflagger
Source-Version: 2.8.0-2

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

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 840...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher <oleb...@debian.org> (supplier of updated aoflagger 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...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 18 Oct 2016 15:01:17 +0200
Source: aoflagger
Binary: aoflagger libaoflagger0 aoflagger-dev
Architecture: source
Version: 2.8.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team <debian-astro-maintain...@lists.alioth.debian.org>
Changed-By: Ole Streicher <oleb...@debian.org>
Description:
 aoflagger  - Find RFI in radio astronomical observations
 aoflagger-dev - Find RFI in radio astronomical observations (development files)
 libaoflagger0 - Find RFI in radio astronomical observations (shared lib)
Closes: 840016
Changes:
 aoflagger (2.8.0-2) unstable; urgency=medium
 .
   * Add static library
   * Limit to x86 architectures. Closes: #840016
   * Make uscan more restrictive to exclude path names in version number
Checksums-Sha1:
 b3d9566b3a35a79515fd5fee5ff2547f82c9cdbd 2419 aoflagger_2.8.0-2.dsc
 9d1442d1f625874c527e5631d306bf462f892def 7656 aoflagger_2.8.0-2.debian.tar.xz
Checksums-Sha256:
 b8766daca9dbabf46abe3c6acc28d37263b89c5aad82bb41d48e280e1c657816 2419 
aoflagger_2.8.0-2.dsc
 abeec3fd1a08fa1e8a350700631beb63fb8d89441032d40bbb31b9bc9ea2af72 7656 
aoflagger_2.8.0-2.debian.tar.xz
Files:
 66de0a9ff1c98dae41179b84d4d6b171 2419 science optional aoflagger_2.8.0-2.dsc
 c5a1ae686569f30eebb0338a84f937eb 7656 science optional 
aoflagger_2.8.0-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJYBiyzAAoJEHEVr9B3ENz3FNUP/2YvBxDmXG2o11ZqjMv61G7g
36IE9K0iO1UQbCO+9bei7KeSGRYPe7MH4N+qJ1xju3hN/PDvbdN+VNj5Bm8BrNve
5mGG/eb5LGIW1yG8XahXiV8cwIaVnafCafskGPgTHO6N1wq1iG1BuB9uas+IvOpq
azMTOuOtxxii/uFzxV5vW5iv+6irPy+5zA39pixzf8SwqBr+mcyp+xNlHDvdLuaL
BBVv8+WRiWN77roarE1DB2WgWqZN7zrdX+apxSP4AxUDmP/82A0S94P254r0f9UU
CsjoB3KHhaJPu6oV8ymFoudBLu+zNgPxwIFFM0F3KyzpxJVwQDTyk2/fTwLCSJqt
rI1BBOF75yOTGUHiWzKPUL3rYeoGY65pNJptHc/4qpWKAUwjXP60W6NeFD5D3iP3
vmzSIne3CjYKLwycaCMXhkmnV/GxtjRSNxeiOe841boWGAlsnv7A535ywZS6yRfp
PHo8IQJHhs1VjLPCGSeNqhbt7sFvWaXTAtqErtCORc8d0ZlX4VIVfbewPfqGSWb7
ZPG1OvvVIDSTeiuwukZhzfgrhVItu+MLTuZclO5hGLsmn/4wYGg7JyxGI8u+mcCA
evql7toHAL8mxDXJLkLqC8qy93fh1lruVW1JneI1lmxHy+n9J3HBZeLbqtWnp4GQ
xxXb58t4ftpz1wQGNXus
=eJql
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to