Bug#1050768: xastir: Drop unused libproj-dev build dependency

[David A Aitcheson]

Christoph,

de Dave KB3EFS

Keeping the B-D is a must so that offline maps can be built from online 
sources provided by the U.S. Government.


Please consult with Tom Russo KM5VY (the last developer to touch the 
entire Xastir source code) before any changes. I have CC'd him with this 
email.


Thank you.

73
Dave
KB3EFS

PS - Yes I see the other emails that are going back and forwards while I 
was typing this.




On 8/29/23 10:07, Christoph Berg wrote:

Control: tags -1 moreinfo

Re: Bas Couwenberg

Your package build depends on libproj-dev but doesn't link to libproj nor 
include proj.h.

Xastir uses libgeotiff-dev, which depends on libproj-dev, so dropping
the B-D wouldn't make it not use it.

Since configure.ac contains an explicit check for libproj before it
tries to check for libgeotiff, I think keeping the B-D does have some
value.

Christoph

Bug#887959: FLDIGI 4.0.13 aborts with fatal error on setting Hardware PTT

[David A Aitcheson]

Debian Hamradio Maintainers 

Please close this bug (#887959) as it is being redirected to a more
apropos list.

Thank You. de Dave KB3EFS

-

Tim Isom 

de Dave KB3EFS. I amCC'ing the LinuxHam listserve where you well be
assisted by the actual developer and several others that are very
familiar with the workings of this program.

Please go to https://groups.io/g/linuxham and sign up as a member of the
group so the Fl suite group can be of direct assistance to you.

Several members of the group have contributed to a Wiki that is
essentially a road-map of how-to get FlDigi working with a minimum of pain.

Please note that a newer version is available and you well be assisted
in conversion to building from source on GitHub as that is the primary
source code location now.

The information you have provided is excellent and is in line with what
others have experienced, thus the newer version that you are just now
aware of.

73
Dave
KB3EFS



On 01/21/2018 10:28 PM, Tim Isom wrote:
> Package: FLDIGI
>   Version: 4.0.13-16
> On initial setup, when reaching the Hardware PTT config - select RTS
> and DTR, check use separate serial port PTT and specify port, the
> program aborts when initialize is pushed with the following
> information captured.
>
> In windows XP and windows 7 professional 64 bit -no issues,
> configuration proceeds as expected and program functions.
>
>
> tim@Radio1 ~ $ fldigi
> I: main: appname: fldigi
> I: main: HomeDir: /home/tim/.fldigi/
> I: main: RigsDir: /home/tim/.fldigi/rigs/
> I: main: ScriptsDir: /home/tim/.fldigi/scripts/
> I: main: PalettesDir: /home/tim/.fldigi/palettes/
> I: main: LogsDir: /home/tim/.fldigi/logs/
> I: main: PicsDir: /home/tim/.fldigi/images/
> I: main: HelpDir: /home/tim/.fldigi/help/
> I: main: MacrosDir: /home/tim/.fldigi/macros/
> I: main: WrapDir: /home/tim/.fldigi/wrap/
> I: main: TalkDir: /home/tim/.fldigi/talk/
> I: main: TempDir: /home/tim/.fldigi/temp/
> I: main: LoTWDir: /home/tim/.fldigi/LOTW/
> I: main: KmlDir: /home/tim/.fldigi/kml/
> I: main: PskMailDir: /home/tim/
> I: main: DATA_dir: /home/tim/.fldigi/data/
> I: main: NBEMS_dir: /home/tim/.nbems/
> I: main: ARQ_dir: /home/tim/.nbems/ARQ/
> I: main: ARQ_files_dir: /home/tim/.nbems/ARQ/files/
> I: main: ARQ_recv_dir: /home/tim/.nbems/ARQ/recv/
> I: main: ARQ_send: /home/tim/.nbems/ARQ/send/
> I: main: WRAP_dir: /home/tim/.nbems/WRAP/
> I: main: WRAP_recv_dir: /home/tim/.nbems/WRAP/recv/
> I: main: WRAP_send_dir: /home/tim/.nbems/WRAP/send/
> I: main: WRAP_auto_dir: /home/tim/.nbems/WRAP/auto/
> I: main: ICS_dir: /home/tim/.nbems/ICS/
> I: main: ICS_msg_dir: /home/tim/.nbems/ICS/messages/
> I: main: ICS_tmp_dir: /home/tim/.nbems/ICS/templates/
> I: main: FLMSG_dir: /home/tim/.nbems/
> I: main: FLMSG_dir_default: /home/tim/.nbems/
> I: main: FLMSG_WRAP_dir: /home/tim/.nbems/WRAP/
> I: main: FLMSG_WRAP_recv_dir: /home/tim/.nbems/WRAP/recv/
> I: main: FLMSG_WRAP_send_dir: /home/tim/.nbems/WRAP/send/
> I: main: FLMSG_WRAP_auto_dir: /home/tim/.nbems/WRAP/auto/
> I: main: FLMSG_ICS_dir: /home/tim/.nbems/ICS/
> I: main: FLMSG_ICS_msg_dir: /home/tim/.nbems/ICS/messages/
> I: main: FLMSG_ICS_tmp_dir: /home/tim/.nbems/ICS/templates/
> I: testCommPorts: Found serial port
> /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_002E25D9-if00-port0
> I: testCommPorts: Found serial port
> /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_002E25D9-if01-port0
> ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
> ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM
> cards.pcm.center_lfe
> ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
> ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching
> channel map
> ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching
> channel map
> ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching
> channel map
> ALSA lib pcm_route.c:867:(find_matching_chmap) Found no matching
> channel map
> Cannot connect to server socket err = No such file or directory
> Cannot connect to server request channel
> jack server is not running or cannot be started
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
> 4294967295, skipping unlock
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for
> 4294967295, skipping unlock
> I: initInterface: No xcvr control selected
> I: readFreqList: # rfcarrier rig_mode carrier mode usage
> I: readFreqList: 1000500 USB 800 CW 
> I: readFreqList: 1807000 USB 1000 BPSK31 
> I: readFreqList: 3505000 USB 800 CW 
> I: readFreqList: 358 USB 1000 BPSK31 
> I: readFreqList: 7005000 USB 800 CW 
> I: readFreqList: 703 USB 1000 BPSK31 
> I: readFreqList: 707 USB 1000 BPSK31 
> I: readFreqList: 10135000 USB 1000 BPSK31 
> I: readFreqList: 14005000 USB 800 CW 
> I: readFreqList: 1407 USB 1000 BPSK31 
> I: readFreqList: 

Bug#876626: [Xastir] Bug#876626: Xastir loose TCP/IP data afer 12 hours of use

[David A Aitcheson]

Matthieu

Please clarify when the problem starts, is it after 12 HOURS or is it
after 12 DAYS? I rarely run my computer beyond 24 hours and probably
only run Xastir about 10 hours at a stretch so I may not be seeing the
issues you are seeing.

Once you convert to building from source for Xastir updating is simple,
just run a included "update" script that does a everything for you. I am
currently running Xastir V2.0.9 (8a3999d) Compiled (from source) on
Monday September 18 2017 at 17:17:00 EDT on my Laptop running Ubuntu
14.04.04-LTS

73
Dave
KB3EFS


On 09/26/2017 05:27 PM, MLHPUB wrote:
> Hello Ian,
>
> I don't know about latest snapshots.
> Maybe it does not occur with 2.0.9 version but I am not comfortable
> with upgrade outside of Debian repositiories...
>
> Regards,
>
> Matthieu
> F4ACU
>
> On Sun, 24 Sep 2017 10:55:13 +0100 "Iain R. Learmonth"
> <i...@debian.org> wrote:
>> Hi,
>>
>> On Sun, Sep 24, 2017 at 05:20:44AM -0400, David A Aitcheson wrote:
>> > > I usually use Xastir during all day, only with a TCP/IP to APRS-IS
>> > > connection at this moment (no radio link).
>> > > After more than 12 days uptime, Xastir loose many data from
>> APRS-IS :
>> > >
>> > > - ACK messages are not received
>> > > - positions reports (even visible on aprs.fi) are not displayed
>> > >
>> > > There is a kind of latency time on RX data from APRS-IS.
>> > >
>> > > It is necessary to quit and restart Xastir to retreive en normal
>> > > behavior.
>>
>> My question would be: does this occur in the latest Xastir snapshots?
>>
>> It's been a long time since there was a release of Xastir and I'm
>> sure the
>> Debian package is missing a number of fixes that have been applied
>> upstream.
>>
>> It's been on my todo list for a while to just update to a git
>> snapshot to
>> get some fixes into the Debian package, but I've not yet had time. If
>> someone can tell me this doesn't happen if you build from source then
>> that
>> would be an easy fix.
>>
>> Thanks,
>> Iain.
>>
>
>

Bug#798947: chirp: unsupported firmware: N5R3409BFP3-25. Please package more often

[David A Aitcheson]

Colin, Iain, Bdale, and All,

I expect that this reply is going to cause significant backlash by some.
Yes I realize that uttering "Launchpad" is a *sin* according to some in
the Debian world.

Note that I use Chirp on an Ubuntu 14.04 LTS system and stay very up to
date.

To that end I think 99.% of your packaging work is already done
for you.

I direct your attention to
http://ppa.launchpad.net/dansmith/chirp-snapshots/ubuntu/pool/main/c/chirp-daily/
and the 'deb' files contained within.

After all we are a _Ham Radio Community_ and should be able to support
each other no matter what the OS of choice is.

73
Dave
KB3EFS



On 10/31/2015 04:38 AM, Colin Tuckley wrote:
> On 30/10/15 04:25, Bdale Garbee wrote:
>
>> The packages in Debian currently reflect the latest upstream release.  I
>> don't have the time or motivation to package unreleased versions of
>> chirp for experimental.
> chirp has moved to rolling releases so the current Debian package is not
> the latest release.
>
> According to the control file the package is maintained by the Debian
> Hamradio  Maintainers, do you have any objections to another team member
> working on the package?
>
> 73, Colin G8TMV
>

Bug#761837: xastir: Please update to new upstream 2.0.6

[David A Aitcheson]

Iain,

Already being worked on; just a few nagging details that need to be
fixed in the CVS.

Also this release is actually the 2.0.7 version.

For BEST results it is strongly suggested that Xastir be installed from
CVS and then to update just run the included update-xastir script
which updates from CVS and automatically does the make and install with
very little needed  from the user save for entering a password.

73
Dave
KB3EFS

On 09/16/14 07:19, Iain R. Learmonth wrote:
 Package: xastir
 Version: 2.0.4-2
 Severity: normal

 Dear Maintainer,

 A new upstream version has been release, 2.0.6.

 Please update the xastir package to the new upstream version.

 Thanks,
 Iain.

 -- System Information:
 Debian Release: 7.6
   APT prefers stable-updates
   APT policy: (500, 'stable-updates'), (500, 'stable')
 Architecture: i386 (i686)

 Kernel: Linux 2.6.32-5-686-bigmem (SMP w/1 CPU core)
 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash



-- 
David A Aitcheson david.aitche...@gmail.com Go Green! Print this email
only when necessary.

Bug#761837: xastir: Please update to new upstream 2.0.6

[David A Aitcheson]

Iain,

I just ran the update-xastir script and the CVS is now installing
Version 2.0.7

Dave


On 09/16/14 07:31, David A Aitcheson wrote:
 Iain,

 Already being worked on; just a few nagging details that need to be
 fixed in the CVS.

 Also this release is actually the 2.0.7 version.

 For BEST results it is strongly suggested that Xastir be installed from
 CVS and then to update just run the included update-xastir script
 which updates from CVS and automatically does the make and install with
 very little needed  from the user save for entering a password.

 73
 Dave
 KB3EFS

 On 09/16/14 07:19, Iain R. Learmonth wrote:
 Package: xastir
 Version: 2.0.4-2
 Severity: normal

 Dear Maintainer,

 A new upstream version has been release, 2.0.6.

 Please update the xastir package to the new upstream version.

 Thanks,
 Iain.

 -- System Information:
 Debian Release: 7.6
   APT prefers stable-updates
   APT policy: (500, 'stable-updates'), (500, 'stable')
 Architecture: i386 (i686)

 Kernel: Linux 2.6.32-5-686-bigmem (SMP w/1 CPU core)
 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash



-- 
David A Aitcheson david.aitche...@gmail.com Go Green! Print this email
only when necessary.


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

Bug#761837: xastir: Please update to new upstream 2.0.6

[David A Aitcheson]

Iain,

The developers are not building any OS packages at all, also they only
develop for UNIX variants.

The timing is the thing with uscan and the d/watch file; the changes
just happened in the last 3 to 4 days at the most.

Dave


On 09/16/14 07:41, Iain R. Learmonth wrote:
 Hi David,

 On Tue, Sep 16, 2014 at 07:31:57AM -0400, David A Aitcheson wrote:
 Already being worked on; just a few nagging details that need to be
 fixed in the CVS.
 Brilliant news! Thanks for your work on this.

 Also this release is actually the 2.0.7 version.
 uscan gave 2.0.6 as the latest version. Possibly a problem with the d/watch
 file.

 For BEST results it is strongly suggested that Xastir be installed from
 CVS and then to update just run the included update-xastir script
 which updates from CVS and automatically does the make and install with
 very little needed  from the user save for entering a password.
 This does seem to be the case with a lot of ham radio software, but I like
 to keep local installs on my system as few as possible.

 Is there any particular reason for this with Xastir?

 Thanks,
 Iain.


-- 
David A Aitcheson david.aitche...@gmail.com Go Green! Print this email
only when necessary.


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

Bug#750819: wsjt: Homepage link broken

[David A Aitcheson]

Colin,

WSJT and WSJT-X both work FB on my system and are current in Ubuntu
12.04-LTS.

CC-ing Joe Taylor for additional input.

Perhaps the documentation is all that is out of date?

73
Dave
KB3EFS


On 06/06/2014 07:08 PM, Colin Tuckley wrote:
 Package: wsjt
 Version: 9.7.r3639+dfsg-1
 Severity: normal

 The Homepage field points to a generic berlios.de page.

 I suspect the project has moved.

 Looking at wsjtx for clues it appears the homepage for wsjt has moved to:

 http://www.physics.princeton.edu/pulsar/K1JT/wsjt.html


 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing
   APT policy: (500, 'testing')
 Architecture: amd64 (x86_64)

 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
David A Aitcheson david.aitche...@gmail.com Go Green! Print this email
only when necessary.


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

Bug#750838: tlf: Homepage field points to download file

[David A Aitcheson]

Correction

Newer program web page is at:

http://tlf.github.io/index2.html

Documentation is lagging behind development.


On 06/07/2014 08:24 AM, Colin Tuckley wrote:
 Package: tlf
 Version: 1.1.5-1
 Severity: normal

 The Homepage: field points to the downloadable archive file.

 It should point to the programs web page, in this case:

 http://tlf.wikispaces.com/

 Please also consider adding a debian/watch file to keep track of the latest 
 version

 -- System Information:
 Debian Release: jessie/sid
   APT prefers testing
   APT policy: (500, 'testing')
 Architecture: amd64 (x86_64)

 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash

-- 
David A Aitcheson david.aitche...@gmail.com Go Green! Print this email
only when necessary.


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

Bug#737060: qsstv: please add qsstv.desktop file

[David A Aitcheson]

Guys,

The desktop entry is present if one logs in as root and runs the
gnome-classic gui (that is what I do at times) BUT it is NOT present in
the normal user menu.

Nor is the entire Ham Radio folder available to the user.

I am wondering if I need to run a command to force the user menu to sync
to the root menu?

Dave ~ KB3EFS

On 01/29/2014 04:16 PM, Colin Tuckley wrote:
 On 29/01/14 21:04, Kamal Mostafa wrote:

 That spec indicates that Keywords is not required, and most .desktop
 files seem not to include it.

 But Lintian flags a warning if it's not present. See

 http://lintian.debian.org/tags/desktop-entry-lacks-keywords-entry.html

 Colin


-- 
David A Aitcheson david.aitche...@gmail.com Go Green! Print this email
only when necessary.


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

Bug#672318: chirp 0.3.0-0.1 Debian package available

[David A Aitcheson]

Chris,

Did you try the Chirp-Daily package? It is almost DAILY in its updates
and working FB for me on Ubuntu 12.04-LTS.

Please look at https://launchpad.net/ubuntu/+source/chirp before you
proceed much more.

The PPA for chirp is at
https://launchpad.net/~dansmith/+archive/chirp-snapshots

Dave - KB3EFS

PS - A fork similar to this is what caused all the problems with NODE.
Did we not learn anything from that drawn out over more than a decade mess?


On 04/04/2013 11:04 PM, Chris Knadle wrote:
 Greetings.

 I recently got a new rig, a small HT, and needed chirp to program it.  
 Unfortunately the version of the packge in Debian now doesn't work for the 
 rig, and I found the year-old wishlist bug #672318 requesting a new version.  
 I've prepared a new 0.3.0-0.1 package (currently as an NMU) and made several 
 other changes -- the debian/rules file now uses dh.

 If someone has time to take a peek and review this source package, I'd 
 appreciate it.  ;-)

http://debian-packages.coredump.us/debian/pool/main/c/chirp/

 Thanks.

   -- Chris, KB2IQN

 --
 Chris Knadle
 chris.kna...@coredump.us



-- 
David A Aitcheson david.aitche...@gmail.com Go Green! Print this email
only when necessary.


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

Bug#672318: chirp 0.3.0-0.1 Debian package available

[David A Aitcheson]

Okay Kamal, I'll wait and see what comes out, then run a cautious trial
on a sample set of the radios I work with on a daily basis.


On 04/05/2013 12:23 PM, Kamal Mostafa wrote:
 On Thu, 2013-04-04 at 23:04 -0400, Chris Knadle wrote:
 Greetings.

 I recently got a new rig, a small HT, and needed chirp to program it. 
 Unfortunately the version of the packge in Debian now doesn't work
for the
 rig, and I found the year-old wishlist bug #672318 requesting a new
version. 
 I've prepared a new 0.3.0-0.1 package (currently as an NMU) and made
several
 other changes -- the debian/rules file now uses dh.

 If someone has time to take a peek and review this source package, I'd
 appreciate it.  ;-)

http://debian-packages.coredump.us/debian/pool/main/c/chirp/

 Thanks Chris, your work is much appreciated.  I'll see that this gets
 reviewed by myself and/or Steve Conklin (the chirp Debian maintainers)
 as soon as possible.

 Thanks.

   -- Chris, KB2IQN


 On Fri, 2013-04-05 at 02:46 -0400, David A Aitcheson wrote:
 [...]
 PS - A fork similar to this is what caused all the problems with NODE.
 Did we not learn anything from that drawn out over more than a decade
mess?

 As has been pointed out, Chris's proposed package is not any sort of a
 fork -- nor is it duplicated work with respect to the chirp-daily PPA.
 Chris's package is aimed at bringing a newer official release of chirp
 to Debian (where it will then make its way into stock Ubuntu and many
 other distros), whereas the purpose of the Ubuntu PPA is to deliver the
 bleeding-edge version to more advanced Ubuntu users.  Chris's package is
 (potentially) suitable for inclusion in Debian and its derivatives, but
 the daily build package is not.

 73 de KA6MAL

  -Kamal

-- 
David A Aitcheson david.aitche...@gmail.com Go Green! Print this email
only when necessary.

Bug#661122: bug#661122: cqrlog: ftbfs with fpc in sid

[David A Aitcheson]

Kefu,

#1 primal_scream Arrrggg! /primal_scream

#2 see http://www.freepascal.org/ for information on free pascal

#3 see http://www.arrl.org/what-is-ham-radio for information about ham
radio in the USA

#4 see http://www.cqrlog.com/ for information about the program you are
messing with

#5 realise that cqrlog (1.2.2-2) has been superseded by cqrlog (1.3.1)
thus your patch may be breaking more than it is fixing

#6 goto #2, #3, #4, #5 again if not clearly understood else goto #7

On 04/23/2012 04:41 PM, Kefu Chai wrote:
 tag 661122 patch thanks hi, I am not quite familiar with free pascal
 or a ham radio. just came across this bug while looking for RC bugs.
 please find attached patch. 

#7 Where in the world are you? (just so we can point you to the ham
radio educators in your area)

Dave - KB3EFS

--
David A Aitcheson
david.aitche...@gmail.com
Go Green! Print this email only when necessary.



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

Bug#623653: xastir: is the libxp dependency necessary?

[David A Aitcheson]

  
  

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Drew,

There are no developers of Xastir on bugs.debian.org that I know
of,
thus the CC-ing to the Xastir list.

As I have said before, 1.9.4x is a very old outdated broken
version of
Xastir relatively speaking.

Please note that Xastir version 2.x is being promoted here and
elsewhere.

Information on the latest STABLE version of Xastir available at
http://www.xastir.org/wiki/Main_Page

Sincerely,
David Aitcheson - KB3EFS

On 04/21/11 21:58, Drew Parsons wrote:
 Package: xastir Version:
  1.9.4-3.1+b1 Severity: wishlist
   
   The xprint package is obsolete and scheduled for removal. A
   related library is libxp, which provides an API that
  enables client
   programs to access and use an Xprint server. Since we're
  getting
   rid of xprint, one could argue it makes sense to get rid of
  libxp
   as well.
   
   Your package depends on libxp. This situation sometimes
  arises 
   historically from the time before xprint was considered
  obsolete,
   with Build-depends: libxp-dev being set in the past and
  then
   forgotten and untouched.
   
   This bug has been filed to prompt you to check if you
  really want 
   Xprint (libxp) support in your package.
   
   We'll leave libxp in the archives for the time being until
  you and
   the other packages using it have determined whether you
  want to
   keep the dependency. But we'll be removing xprint itself
  and other
   related packages now.
   
   
   -- System Information: Debian Release: wheezy/sid APT
  prefers
   unstable APT policy: (500, 'unstable'), (1, 'experimental')
  
   Architecture: amd64 (x86_64)
   
   Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale:
   LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
  Shell:
   /bin/sh linked to /bin/dash


- -- 
David A Aitcheson
david.aitche...@gmail.com
david.aitcheson on google and skype
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iF4EAREIAAYFAk2w7kUACgkQN9kB/Il6DMDVswD7BN7gVFRqKWZjGWaBJZ/wkkBP
HJrGWv58cAaHrfqiInQA/Am/ROcoBg8MFHxAKGulO64Zg65eujHRErmyOurjyn/+
=x4kH
-END PGP SIGNATURE-

  




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

Bug#621450: Still uses libdb4.8

[David A Aitcheson]

Ondřej,

xastir version 1.9.4-3.1 is no longer a valid release. The latest
version on SourceForge is 2.0.0 and can be found at
http://sourceforge.net/projects/xastir/files/   I am not certain which
db is currently used in the current release.

Due to the non-availability of on-line Tiger maps OSM is now fully
integrated and the default.

Please kindly refer yourself to http://www.xastir.org/wiki/Main_Page for
the latest information regarding Xastir.

I would also suggest that you join/subscribe to the Xastir reflector at
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir at the least and
introduce yourself.

Others here and on the Ubuntu hams list and Ubuntu hams devel list have
done some significant advancement of the package and have very up to
date releases available on PPA's.  I am certain that they well chime in
with more definitive information.

Sincerely,
David Aitcheson - KB3EFS


On 04/06/11 16:57, Ondřej Surý wrote:
 Package: xastir
 Version: 1.9.4-3.1
 Severity: normal
 User: pkg-db-de...@lists.alioth.debian.org
 Usertags: db5.1

 Your package currently still uses Berkeley DB version 4.8 (libdb4.8).

 However, there is a newer Berkeley DB version in the archive (libdb5.1),
 with a compatible API. Berkeley DB version 4.8 will be eventually
 removed from unstable in favor of version 5.1.

 Please port your package to libdb5.1 as soon as possible. In most cases
 only change required is to update build depends from libdb4.8-dev
 to libdb-dev, or just recompile the package.

 More complicated scenarios:

 - Package does check for DB_VERSION_MAJOR == 4 - this should be updated
 to (DB_VERSION_MAJOR  4) || ((DB_VERSION_MAJOR == 4) 
 (DB_VERSION_MINOR = XX)).

 - Configure checks - sometime there is a list of db-4.8 db-4.6 db-4.2,
 etc., this
 needs to be updated to just db (or db-5.1 db-5 db), or at least list
 the 'db'
 in the front

 You can see example patch in cyrus-imapd-2.2:
 http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.2.git;a=blob;f=debian/patches/99-berkelydb-5.1.dpatch;hb=HEAD

 - The packages which use Berkeley DB transactional mode need to upgrade
 the database files before the upgrade. This is fairly straightforward
 and is well documented on the Berkeley DB website. But you probably
 already know that because it's not the first Berkeley DB transition.

 The example script can be found in the cyrus-imapd-2.4 (not yet released):
 http://git.debian.org/?p=pkg-cyrus-imapd/cyrus-imapd-2.4.git;a=blob;f=debian/cyrus-upgrade-db;hb=HEAD

 Thanks,
 --
 Ondřej Surý ond...@debian.org

 -- System Information:
 Debian Release: squeeze/sid
 APT prefers maverick-updates
 APT policy: (500, 'maverick-updates'), (500, 'maverick-security'),
 (500, 'maverick-proposed'), (500, 'maverick-backports'), (500, 'maverick')
 Architecture: amd64 (x86_64)

 Kernel: Linux 2.6.35-28-generic (SMP w/4 CPU cores)
 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
 Shell: /bin/sh linked to /bin/dash







-- 
David A Aitcheson
david.aitche...@gmail.com
david.aitcheson on google and skype



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