[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#280561: marked as done (tqsllib-bin: Command-line programs lack documentation)



Your message dated Sat, 23 Jul 2011 13:25:49 -0700
with message-id <1311452749.6054.17.camel@fourier>
and subject line Re: Bug#280561: tqsllib-bin: Command-line programs lack documentation
has caused the Debian Bug report #280561,
regarding tqsllib-bin: Command-line programs lack documentation
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 owner@bugs.debian.org
immediately.)


-- 
280561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280561
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: tqsllib-bin
Version: 1.4-1
Severity: normal

The TQSL suite appears to be largely based on HF paradigms, as opposed to
satellite and VHF+ concepts, such as 'rovers' operating from numerous
locations, sometimes dozens in a given weekend.  The TQSL design seems to
expect one to prepare QSL data separately for each location. 'tqsl' allows
one to submit that data in a graphical manner.  Unfortunately, it appears
that this process would need to be done manually for each location, which
seems impractical for 'rovers'.  I've only done a small amount of roving
and i already have GPS co-ordinates for at least 40 different locations.

Some folks who operate on ECHO and AO-27 literally have literally operated
from hunderds of locations.  Maybe i have some misunderstanding, but i find
entering all of this manually seems unduly burdensome for the kind operators
who are providing rare counties and grid squares for all of the rest of us.
So i'm looking for some means of doing this, at least for myself, without
re-inventing the wheel (i.e. creating yet another logging program, most
likely with its own format which would still have to be translated for
TQSLing).

'tqsllib-bin' has several 'test' programs which potentially might be helpful
in automating that process (or provide a starting point for that process).  
Alas, the documentation is hardly even minimal for these programs, that is,
'tqsl_converter','tqsl_dumptqsldata', 'tqsl_gen_crq', 'tqsl_load_cert, and
'tqsl_station_loc'.  The only thing i could find, via Debian packages, at
the ARRL website, at the SourceForge pages or via Google, were 1-3 line
descriptions in a README file in the source package.  Everything else i 
looked at seemed just to cover the GUI or API.  Looking at the source code
for the programs themselves wasn't much help either.  If they're are worthy
of being in '/usr/bin' i think they should be documented, at least briefly,
in their own package (and/or in a -doc package). Or maybe i missed something
and this bug report is bogus.

While i'm not asking a full-blown 'man' page for each one of them, a better
description of their inputs, outputs, and what they actually do, would be
gratefully appreciated.
			  -- KD6PAG  (Networking Old-Timer, satellite QRPer)

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.4.21
Locale: LANG=C, LC_CTYPE=C

Versions of packages tqsllib-bin depends on:
ii  libc6                       2.3.2.ds1-16 GNU C Library: Shared libraries an
ii  libexpat1                   1.95.6-8     XML parsing C library - runtime li
ii  libssl0.9.7                 0.9.7d-5     SSL shared libraries
ii  libstdc++5                  1:3.3.4-13   The GNU Standard C++ Library v3
ii  tqsllib0                    1.4-1        QSL signing routines for the Logbo
ii  zlib1g                      1:1.2.1.1-7  compression library - runtime

-- no debconf information


--- End Message ---
--- Begin Message ---
Tags: wontfix

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---

Reply to: