[Xastir] What's this output

[Doug Alwine]

On 05/12/2012 10:44 PM, Tom Russo wrote:
> On Sat, May 12, 2012 at 08:39:30PM -0600, we recorded a bogon-computron collision of the<russo at bogodyn.org>  flavor, containing:
>> On Sat, May 12, 2012 at 08:44:26PM -0500, we recorded a bogon-computron collision of the<jjolin at itol.com>  flavor, containing:
>>
>>>>>> Do a cvs update.  These fprintfs are now commented out.
>>>>> Thanks for the info, Tom.  Unfortunately I can't find a cvs update in
>>>>> any of my xastir files.  I thought I had cvs setup right, but apparently
>>>>> not.  Will start over and see what is wrong.  If you have any ideas, let
>>>>> me know.
>>>>
>>>> simply type'cvs update' in your top-level xastir source directory.  if you had the bom debuuging output you must have cvs set
>>>> up, since that code change was only present in a very recent update.
>>
>>> Tom,
>>> Tried that and here is what I got:
>>> jolin at jjolin-Inspiron-8200 ~/src $ cd xastir
>>> jjolin at jjolin-Inspiron-8200 ~/src/xastir $ cvs update
>> [...CVS did no updating]
>>> jjolin at jjolin-Inspiron-8200 ~/src/xastir $
>>
>> Bizarre.  Please do this:
>>
>> cd ~/src/xastir/src
>> cvs status wx.c
>
> Actually, try "cvs status maps.c" --- I made a few commits recently, and you
> should have changes to configure.ac, maps.c, db.c and wx.c.  That you got
> none of them in your cvs update points to something fishy, still either
> a sticky tag or an issue at sourceforge.
>
For what is is worth, about 2 days ago I did a cvs update and it worked 
perfectly.  All the stuff about ":BOM Coastal waters warning file" is 
now gone.  Thanks for a great program!

Doug