Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Bob Nielsen <nielsen@oz.net>
To: Linux Hams <linux-hams@vger.kernel.org>,
	Debian Hams <debian-hams@lists.debian.org>
Subject: Re: ARRL's LoTW with Debian Sarge
Date: Tue, 23 Sep 2003 17:34:44 -0700	[thread overview]
Message-ID: <20030924003444.GA24050@n7xy.net> (raw)
In-Reply-To: <20030918031442.GA708@localhost>

Has anybody tried TrustedQSL version 1.07?  When I get to the point of
creating the signed file, tqsl gives me the following error and then
dies:

tqsl: relocation error: tqsl: undefined symbol: tqsl_setADIFConverterDateFilte
 
I was able to create files with 1.06, but the LOTW system doesn't
appear to like them and gives me this (I did successfully go through
the certificate process):

2003-09-23 17:30:41 LOTW_QSO:  Error in record 3: No recognized signing specification in tCONTACT record

I didn't have any of these problems with the beta-test versions.

This is on a Debian (mostly Sarge with a bit of Sid) system, using
alien to convert the files.  I also tried compiling from source, but
had trouble with both trustedqsl (configure can't locate tqsllib even if
I specify the location) and tqsllib (/usr/bin/ld: cannot find -liberty).

Puzzled,
Bob, N7XY

On Wed, Sep 17, 2003 at 10:14:42PM -0500, Nate Bargmann wrote:
> Hello everyone.
> 
> For most on this list what I'm about describe is probably old hat, but
> there may be some newcomers that would find this helpful in the list
> archives.
> 
> As most are probably aware, the American Radio Relay League has been
> working for a few years on a way to digitally sign log submissions for
> electronic application for their various awards.  In the October 2003 
> issue of QST (Amateur Windows?  8-) it has been announced that this 
> program was opened to general use as of 15 September 2003.  On the 
> Logbook of The World web page:
> 
> http://www.arrl.org/lotw/
> 
> there is a library and programs for signing and generating log data for
> Linux.  These programs are provided in binary form only for Red Hat 7.2
> and 8.0 releases and are RPMs.  Also provided are source RPMs for the
> library and the applications.  These archives are not directly
> installable as managed packages on my Linux distribution of choice, 
> Debian, so they must be converted using a utility called Alien.
> 
> Having never needed Debian's Alien before, I decided this was as good of
> a time as any to try it.  I grabbed the RH 8.0 RPMs and the source RPMs,
> just in case.
> 
> I installed alien, rpm, libwxbase2.4, and libwxgtk2.4 as the web page
> said the programs depended on WXWin 2.4.
> 
> Converting the RPMs to .deb's was straightforward with alien and
> installation with dpkg completed without error.  I attempted to start
> tqsl, but the startup failed.  A quick ldd /usr/bin/tqsl revealed a
> dependency on libcrypto.so.2 that was not found.  Using the package
> search page on the Debian site:
> 
> http://www.debian.org/distrib/packages
> 
> I found that it was a part of the libssl0.9.7 and libssl0.9.6 packages,
> the latter version being in the oldlibs section.
> 
> Well, I created a symlink to libcrypto.so.0.9.7 named libcrypto.so.2:
> 
> ln -s libcrypto.so.0.9.7 libcrypto.so.2
> 
> (actually I used Midnight Commander, but this is generic--don't forget
> you'll need to be root as these files reside in /usr/lib) and tried
> again.  Running tqsl worked fine, but tqslcert failed with a relocation
> error.
> 
> Poking around in the README in the tqsllib archive I found where the
> library is dependent on OpenSSL 0.9.6.  So I redid my symlink to point
> to libcrypto.so.0.9.6 and tqslcert loaded and ran.
> 
> In tqslcert I was able to create my certificate request and am now
> waiting for the authentication process.
> 
> One quirk or bug I noticed in tqslcert is that if the Help button is
> clicked and then the help window is backgrounded, the window that called
> the help window is frozen and will remain so until the help window is
> closed.  This may be a problem in WxWin, I don't know.
> 
> So there you have it, my micro-HOWTO on LoTW on Debian Sarge (Testing).
> 
> 73, de Nate >>
> 
> P.S. I keep this system updated about once per week.  An older Testing
> snapshot may or may not work.  The same caveat may apply to Sid
> (Unstable).
> 
> -- 
>  Wireless | Amateur Radio Station N0NB          | "We have awakened a
>  Internet | n0nb@networksplus.net               | sleeping giant and
>  Location | Bremen, Kansas USA EM19ov           | have instilled in him
>   Amateur radio exams; ham radio; Linux info @  | a terrible resolve".
>              http://www.qsl.net/n0nb/           | - Admiral Yamamoto


  parent reply	other threads:[~2003-09-24  0:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18  3:14 ARRL's LoTW with Debian Sarge Nate Bargmann
2003-09-18  3:42 ` Bob Nielsen
2003-09-18 13:22 ` [Ham-Linux] " Robert Wooldridge
2003-09-24  0:34 ` Bob Nielsen [this message]
2003-09-26 17:47   ` ARRL's LoTW with Debian Sarge (solved) Bob Nielsen
2003-09-26 23:08     ` w9ya
2003-09-30  5:58       ` ARRL's LoTW Wilbert Knol

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030924003444.GA24050@n7xy.net \
    --to=nielsen@oz.net \
    --cc=debian-hams@lists.debian.org \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox