Custom Query (95 matches)

Here's an except of my data:

*begin ; 111: <REDACTED>
*date 1983.07.13

*team <REDACTED>
*team <REDACTED>
*units tape feet
*calibrate BACKCOMPASS 180.00
*calibrate BACKCLINO 0.00 -1.00

*data normal from to tape compass backcompass clino backclino
;From       To          Distance    Compass     BackCompass Clino       BackClino  
<...REDACTED>
HC14        HC15        10.7        296         296         -26         -26               
HC15        HC16        1.3         -           -           DOWN        DOWN      

Cavern complains that "CLINO and BACKCLINO readings must be of the same type" for the DOWN/DOWN line, but not the -26/-26 line.

Is this invalid Survex data or is it a bug in Cavern?

Running aven on a 64bit linux (fedora 16) laptop only displays an error message "Bug in program detected! Please report this to the authors" and then exits. Running aven from the command line displays:

[james@jumbo ~]$ aven
Bad memory access
[james@jumbo ~]$

Running aven through GDB (with no debugging symbols) gives

(gdb) file /usr/bin/aven
Reading symbols from /usr/bin/aven...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/aven /usr/bin/aven
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Detaching after fork from child process 11340.
Detaching after fork from child process 11341.
Detaching after fork from child process 11342.

Program received signal SIGSEGV, Segmentation fault.
0x0000003d6e653136 in glClearColor () from /usr/lib64/libGL.so.1

Any ideas? version 1.2.2 was working fine ...

There are 2 errors with the survex.spec file when attempting to build a RPM for fedora 23. These are:

1) The survex mime file has moved from /usr/share/mime/survex* to /usr/share/mime/packages/survex.xml so the %files section of the spec file needs updating, and

2) Fedora 23 has upgraded to RPM version 4.13, which is fussier about empty package files. By default an empty 'survex-debug' package will be built, which will now cause the rpmbuild process to fail. Google suggests that the 'fix' for this is to include

# workaround for rpm 4.13 %define _empty_manifest_terminate_build 0

in the spec file - I just added this before the %description section and the build then worked fine.

Cheers, James