[Dxspider-support] DXSpider v 1.55 build 0.221

[Mike McCarthy, W1NR]

I needed to do an unset/dxgrid to see states

W1NR

On 12/10/2021 7:22 AM, Dirk Koopman via Dxspider-support wrote:
> On my test master branch machine (callsign GB7TLH-1) it appears to be 
> working. Here is an (edited) example from
> a few moments ago. It has a fresh usdb.
> 
> DX de DD0UM:     14157.0 W4RN VA 1213Z
> DX de WZ1V:      50145.0  K9DRG FN31<>EN70 IN 1213Z CT
> DX de W5EME:    144289.0  N5XO/B       EM32AI<TR>EL09UM 
> 519                                                     1214Z LA
> DX de W5EME:    144275.0  AB5N/B       EM32AI<TR>EM34LM 
> 599                                                     1215Z LA
> DX de W4HLR:     50145.0  WZ1V         EM56JB<MS>FN31RH 
> tnx                                                  CT 1215Z TN
> DX de PD5CZB:    14157.0  W4RN         great signal 73, 
> usb                                                  VA 1216Z
> DX de KC1GTK:    14270.0 MM0OPX 1217Z NH
> DX de N2OIT:     14288.0  M0XXT 55 1217Z PA
> DX de KC1GTK:    14195.0 R200NN 1218Z NH
> DX de KD2WDR:    50260.0  K1SIX        FN30GS<>FN43 -6dB 1495 Hz 
> hrd                                         NH 1218Z NY
> 
> Dirk G1TLH
> 
> On 10/12/2021 12:12, Anthony (N2KI) via Dxspider-support wrote:
>> Confirmed,  No US State appended to an announcement bld221
>>
>> Regards,
>>
>> Anthony (N2KI)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Fri, Dec 10, 2021 at 1:17 AM Steve - AA4U via Dxspider-support 
>> <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>> 
>> wrote:
>>
>>     Initially it appeared all was working properly after updating.
>>     But, I now see the 'set/usstate' command doesn't show the 2-letter
>>     state anymore. I verified the US Database is loading at cluster
>>     start-up.
>>
>>     I didn't change anything on the cluster, just did a 'git reset
>>     --hard' and 'git pull' (same process as has been done dozens of
>>     times in the past). Then, restarted the node.
>>
>>     I'm curious if anyone else has this issue after updating.
>>
>>     73, Steve - AA4U
>>
>>
>>     Sent from my Verizon, Samsung Galaxy smartphone
>>
>>
>>     -------- Original message --------
>>     From: Steve - AA4U via Dxspider-support
>>     <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>>
>>     Date: 12/9/21 22:02 (GMT-06:00)
>>     To: The DXSpider Support list <dxspider-support at tobit.co.uk
>>     <mailto:dxspider-support at tobit.co.uk>>,
>>     dxspider-support at dxcluster.org
>>     <mailto:dxspider-support at dxcluster.org>
>>     Cc: Steve - AA4U <aa4u at mchsi.com <mailto:aa4u at mchsi.com>>
>>     Subject: [Dxspider-support] DXSpider v 1.55 build 0.221
>>
>>
>>     Successfully updated from build 0.218 to 0.221 (non-MOJO)
>>
>>     Everything appears to be working properly.
>>
>>     73, Steve - AA4U
>>
>>
>>     Sent from my Verizon, Samsung Galaxy smartphone
>>
>>
>>     _______________________________________________
>>     Dxspider-support mailing list
>>     Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
>>     https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>     <https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support>
>>
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> 
> 
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>