Bug#856055: NetCDF import broken on amd64

2017-02-24 Thread Timo Korvola

Package: dx
Version: 1:4.4.4-9+b1

Import of NetCDF files produces incorrect integer values on systems 
where long is not 32 bits.  This can be seen by running the attached 
nctest.net and importing nctest.nc.  The file can be inspected with

ncdump.  The connections, being int valued, will be imported incorrectly.

The attached patch should fix the problem.  The erroneous code assumed 
that the NetCDF type NC_LONG corresponds to long.  However, NC_LONG is a 
deprecated alias for NC_INT and by definition 32 bits, whereas long 
varies by platform.  These days it is better to leave such type 
conversions to the NetCDF library, which provides likely more efficient 
and correct routines.


The patch also fixes a debug output routine, which casts pointers into 
unsigned int for printing.  It seems that the routine is never called 
but at least compiler warnings are eliminated.


--
Timo Korvola<URL:http://www.iki.fi/tkorvola>


nctest.nc
Description: Cdf file
//
// time: Fri Feb 24 00:10:21 2017
//
// version: 3.2.0 (format), 4.4.4 (DX)
//
//
// MODULE main
// workspace: width = 321, height = 499
// layout: snap = 0, width = 50, height = 50, align = NN
//
macro main(
) -> (
) {
// 
// node FileSelector[1]: x = 72, y = 14, inputs = 0, label = FileSelector
// output[1]: visible = 1, type = 32, value = "/home/thk/src/test/nctest.nc"
// output[2]: visible = 1, type = 32, value = "nctest.nc"
//
// 
// node Import[1]: x = 90, y = 118, inputs = 6, label = Import
//
main_Import_1_out_1 = 
Import(
main_FileSelector_1_out_1,
main_Import_1_in_2,
main_Import_1_in_3,
main_Import_1_in_4,
main_Import_1_in_5,
main_Import_1_in_6
) [instance: 1, cache: 1];
// 
// node AutoColor[1]: x = 138, y = 191, inputs = 10, label = AutoColor
//
main_AutoColor_1_out_1,
main_AutoColor_1_out_2 = 
AutoColor(
main_Import_1_out_1,
main_AutoColor_1_in_2,
main_AutoColor_1_in_3,
main_AutoColor_1_in_4,
main_AutoColor_1_in_5,
main_AutoColor_1_in_6,
main_AutoColor_1_in_7,
main_AutoColor_1_in_8,
main_AutoColor_1_in_9,
main_AutoColor_1_in_10
) [instance: 1, cache: 1];
// 
// node AutoGlyph[1]: x = 201, y = 278, inputs = 7, label = AutoGlyph
// input[2]: defaulting = 0, visible = 1, type = 32, value = "text"
//
main_AutoGlyph_1_out_1 = 
AutoGlyph(
main_AutoColor_1_out_1,
main_AutoGlyph_1_in_2,
main_AutoGlyph_1_in_3,
main_AutoGlyph_1_in_4,
main_AutoGlyph_1_in_5,
main_AutoGlyph_1_in_6,
main_AutoGlyph_1_in_7
) [instance: 1, cache: 1];
// 
// node Tube[1]: x = 114, y = 280, inputs = 4, label = Tube
//
main_Tube_1_out_1 = 
Tube(
main_AutoColor_1_out_1,
main_Tube_1_in_2,
main_Tube_1_in_3,
main_Tube_1_in_4
) [instance: 1, cache: 1];
// 
// node Collect[1]: x = 177, y = 360, inputs = 2, label = Collect
//
main_Collect_1_out_1 = 
Collect(
main_Tube_1_out_1,
main_AutoGlyph_1_out_1
) [instance: 1, cache: 1];
// 
// node Image[1]: x = 175, y = 437, inputs = 49, label = Image
// input[1]: defaulting = 0, visible = 0, type = 67108863, value = "Image_1"
// input[4]: defaulting = 0, visible = 0, type = 1, value = 1
// input[5]: defaulting = 0, visible = 0, type = 8, value = [0.0407761 
0.608095 3.3903]
// input[6]: defaulting = 0, visible = 0, type = 8, value = [1.05857 
-0.449439 16.9762]
// input[7]: defaulting = 1, visible = 0, type = 5, value = 7.32305
// input[8]: defaulting = 0, visible = 0, type = 1, value = 640
// input[9]: defaulting = 0, visible = 0, type = 5, value = 0.75
// input[10]: defaulting = 0, visible = 0, type = 8, value = [0.0102178 
0.996991 0.076841]
// input[11]: defaulting = 0, visible = 0, type = 5, value = 30.0001
// input[12]: defaulting = 0, visible = 0, type = 1, value = 1
// input[14]: defaulting = 0, visible = 0, type = 1, value = 1
// input[15]: defaulting = 1, visible = 0, type = 32, value = "none"
// input[16]: defaulting = 1, visible = 0, type = 32, value = "none"
// input[17]: defaulting = 1, visible = 0, type = 1, value = 1
// input[18]: defaulting = 1, visible = 0, type = 1, value = 1
// input[19]: defaulting = 0, visible = 0, type = 1, value = 0
// input[29]: defaulting = 1, visible = 0, type = 3, value = 0
// input[41]: defaulting = 0, visible = 0, type = 32, value = "navigate"
// depth: value = 24
// window: position = (0.3708,0.4114), size = 0.3893x0.4971, screen = 0
// internal caching: 1
//
main_Image_1_out_1,
main_Image_1_out_2,
main_Image_1_out_3 = 
Image(
main_Image_1_in_1,
main_Collect_1_out_1,
main_Image_1_in_3,
main_Image_1_in_4,
main_Image_1_in_5,
main_Image_1_in_6,
main_Image_1_in_7,
main_Image_1_in_8,
main_Image_1_in_9,
main_Image_

Bug#773731: Seems improved in Jessie or systemd

2015-05-09 Thread Timo Korvola
Upgrading to Jessie sneaked systemd into my machine, and now I am able 
to boot with a cached volume.  Looks like /usr now gets mounted before 
the other filesystems are checked.  As long as one does not try to cache 
root or /usr it should work (I have root and /usr fully on SSD).  I 
don't know if sysvinit boot scripts remain broken or anything about upstart.


Still need to make sure you have thin-provisioning-tools though.

--
Timo KorvolaURL:http://www.iki.fi/tkorvola


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#773731: cache_check should be on root

2015-03-21 Thread Timo Korvola

On 21.03.2015 13:28, Bastian Blank wrote:

The binaries from thin-provisioning-tools depends on libstdc++, so they
must reside in /usr.


Ditto for cache_check.  This seems to be getting complicated.

In order to support cached root, cache_check and hence libstdc++ need to 
be on initrd.  The boot scripts could be modified to activate all volume 
groups before mounting root.  Then it should not matter if cache_check 
is not on the actual root.


Another possibility would be to do fsck and mounting in three phases 
instead of two: first fsck and mount root, then /usr and other 
non-cached volumes and finally cached volumes.  Root and /usr could not 
be cached then.


Or maybe just link statically to libstdc++.

--
Timo KorvolaURL:http://www.iki.fi/tkorvola


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#773731: cache_check should be on root

2015-03-20 Thread Timo Korvola
Looks like the problem on system was not cache_check missing from the 
initrd, as I was not trying to cache root. The problem was cache_check 
missing from the actual root fs. vgchange -aay, executed after mounting 
root but before fsck, failed for the cached volumes. I suppose 
cache_check should be moved to /sbin. Maybe also the thin provisioning 
utilities if needed to fix #774560.


--
Timo KorvolaURL:http://www.iki.fi/tkorvola


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#773731: thin-provision-tools

2015-03-19 Thread Timo Korvola
On Sat, 17 Jan 2015 07:59:48 +0200 Aleksi Suhonen 
debian-reportbug-2...@ssd.axu.tm wrote:

I ran into this problem too.  Installing thin-provisioning-tools

 fixed the problem.

That did not quite fix it for me: fsck still failed at boot because 
cache_check was not on the initrd.

A similar story: [http://forums.debian.net/viewtopic.php?f=5t=119644].
See also bug #774560.

--
Timo KorvolaURL:http://www.iki.fi/tkorvola


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#427963: print-camera-list broken?

2008-12-16 Thread Timo Korvola
In addition to the mistyped ATTRS instead of ATTR, there is this bogus
line in the beginning of /etc/udev/libgphoto2.rules (generated by
/usr/lib/libgphoto2/print-camera-list during installation):

SUBSYSTEM!=usb|usb_device, GOTO=libgphoto2_rules_end

According to the udev manual page wildcards should work but nothing
is said about |.  Changing that line in the rule file to

SUBSYSTEM!=usb_device, GOTO=libgphoto2_rules_end

and replacing ATTRS with ATTR would seem to help.

-- 
Timo KorvolaURL:http://www.iki.fi/tkorvola



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#475001: texmacs: Refuses to work with Maxima 5.13

2008-04-08 Thread Timo Korvola
Package: texmacs
Version: 1:1.0.6.11-5
Severity: important

Trying to start a Maxima session produces:
ed Unsupported version of maxima: 5.13.0
maxima]
Editing the case statement in /usr/lib/texmacs/TeXmacs/bin/tm_maxima
would seem to fix the problem.  The startup command for versions 5.11
and 5.12 appears to work also for 5.13.

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (750, 'stable'), (600, 'testing'), (550, 'unstable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.24-1-686
Locale: LANG=C, LC_CTYPE=fi_FI (charmap=ISO-8859-1)

Versions of packages texmacs depends on:
ii  findutils  4.2.28-1etch1 utilities for finding files--find,
ii  ghostscript-x [gs-gpl] 8.62.dfsg.1-2 The GPL Ghostscript PostScript/PDF
ii  groff  1.18.1.1-12   GNU troff text-formatting system
ii  gs-gpl 8.62.dfsg.1-2 Transitional package
ii  guile-1.8-libs 1.8.4+1-2 Main Guile libraries
ii  libc6  2.7-10GNU C Library: Shared libraries
ii  libfreetype6   2.3.5-1+b1FreeType 2 font engine, shared lib
ii  libgcc11:4.3.0-1 GCC support library
ii  libgmp3c2  2:4.2.1+dfsg-4Multiprecision arithmetic library
ii  libltdl3   1.5.22-4  A system independent dlopen wrappe
ii  libstdc++6 4.3.0-1   The GNU Standard C++ Library v3
ii  libx11-6   2:1.0.3-7 X11 client-side library
ii  libxext6   2:1.0.4-1 X11 miscellaneous extension librar
ii  texlive-base   2007-13   TeX Live: Essential programs and f
ii  texlive-extra-utils2007.dfsg.1-2 TeX Live: TeX auxiliary programs
ii  texlive-font-utils 2007.dfsg.1-2 TeX Live: TeX font-related program
ii  texlive-math-extra 2007.dfsg.1-1 TeX Live: Advanced math typesettin
ii  texmacs-common 1:1.0.6.11-5  WYSIWYG mathematical text editor u
ii  xbase-clients  1:7.1.ds1-2   miscellaneous X clients
ii  zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime

Versions of packages texmacs recommends:
ii  imagemagick 7:6.2.4.5.dfsg1-0.14 Image manipulation programs
ii  ispell  3.1.20.0-4.3 International Ispell (an interacti
ii  libjpeg-progs   6b-13Programs for manipulating JPEG fil
ii  librsvg2-bin2.14.4-3 command-line and graphical viewers
ii  libtiff-tools   3.8.2-7  TIFF manipulation and conversion t
ii  netpbm  2:10.0-11Graphics conversion tools
pn  texmacs-extra-fonts none   (no description available)
ii  xfig1:3.2.5-alpha5-9 Facility for Interactive Generatio

-- no debconf information



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



Bug#240423: apt-cache policy emulation

2005-04-16 Thread Timo Korvola
I think the natural place for this would be the version list produced
by the v key.  It is currently just a simple list of version numbers
with plenty of screen space available.  It could be made to look more
like the output of apt-cache policy, perhaps by adding the repository
info as leaves to the version numbers.

-- 
Timo KorvolaURL:http://www.iki.fi/tkorvola


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