Package: casacore / 3.3.0-4
Metadata
Package | Version | Patches format |
---|---|---|
casacore | 3.3.0-4 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
Do not install test and demonstration executables.patch | (download) |
measures/apps/CMakeLists.txt |
2 1 1 - 0 ! |
do not install test and demonstration executables casacore_{assay,floatcheck} are removed and only used with scons. measuresdata.csh and ms2uvfits should be included in casacore-doc as examples. change measuresdata.csh shebang to /usr/bin/tcsh as in Debian. |
Disable class and collaboration graph generation.patch | (download) |
doxygen.cfg |
6 3 3 - 0 ! |
disable class and collaboration graph generation The graphviz-generated class and collaboration graph occupies 1GB disk space. It is too big to deal with. We turn them off only to save space. Output image format is specified as svg to further save space (bug #751947). |
Disable tests that require data tables.patch | (download) |
coordinates/Coordinates/test/CMakeLists.txt |
12 6 6 - 0 ! |
disable tests that require data tables The data tables are not available during the build of casacore (yet). |
Disable known test failures.patch | (download) |
casa/IO/test/CMakeLists.txt |
4 2 2 - 0 ! |
disable known test failures https: //bugs.debian.org/cgi-bin/bugreport.cgi?bug=838424#15 These tests fail, probably due to the test itself. From I'm not sure what to do about the other two tests that fail on arm64, "tLSQaips" and "tLSQFit", because those two generate a load of output text containing floating-point numbers and compare that text with an expected output. It might not be so easy to make that work on all architectures. Perhaps one could simply disable those two tests. Preferably one would still run them, so that we can see what happens in the logs, but not have the build fail if only those tests fail. |
Loose some tests tFFTServer tests.patch | (download) |
scimath/Mathematics/test/tFFTServer.cc |
2 1 1 - 0 ! |
loose some tests tfftserver tests This shall help to compile for mips64el and hppa. |
Make the check for NFS a bit more portable BSD.patch | (download) |
casa/OS/Directory.cc |
19 14 5 - 0 ! |
make the check for nfs a bit more portable (bsd) And provide a fallback (f.e. for HURD).However, there is probably no real use case for that, since also other file systems may be slow or lack certain features. |
Enable hostinfo for kFreeBSD.patch | (download) |
casa/aipsenv.h |
2 1 1 - 0 ! |
enable hostinfo for kfreebsd |
Fix compilation for GNU Hurd.patch | (download) |
casa/OS/HostInfo.cc |
7 7 0 - 0 ! |
fix compilation for gnu hurd However, the tests still fail. |
Fall back to older cmake functions to find Python 3.patch | (download) |
python3/CMakeLists.txt |
2 1 1 - 0 ! |
fall back to older cmake functions to find python 3 This is a workaround that cmake will fail when the default Python version is not the newest one. Reference: #945825 |
Use python3 in bang path of test utilities.patch | (download) |
build-tools/casacore_floatcheck |
2 1 1 - 0 ! |
use python3 in bang path of test utilities |
Use FFTW instead of FFTPack in Fits IDI to MS table conve.patch | (download) |
msfits/MSFits/FitsIDItoMS.cc |
48 18 30 - 0 ! |
use fftw instead of fftpack in fits-idi to ms table converter The FitsIDItoMS class is the only class that was still dependent on the FFTPack Fortran code. By rewriting it to use FFTW, the FFTPack code can be removed. This required implementing a wrapper for the real even FFT in the FFTW class, as that was not available. The FFTW class should be rewritten to have a more sensible interface. I've added some TODO comments for that. Despite the use of a mutex, the FFTW wrapper is also not thread safe. Closes: #957065 |
Fix type of DUMMY variable.patch | (download) |
scimath_f/lawson.f |
4 2 2 - 0 ! |
fix type of dummy variable |