[aprssig] xastir bug?

[Steve Dimse]

I looked, but too quickly to notice the R. When you’ve spent most of the last 20 years looking at text containing APR in a hundred different configurations you tend to focus on the unfamiliar, like the X. And then there are shrinking computer screens and aging eyes to account for. No harm, it still would need to be announced on the sig in case the author was listening, and so anyone using the software can be on alert for the problem. Since I was corrected I emailed the author but have gotten no response.

I am less worried now because I’m sure there are a lot less copies of his software floating around than xastir!

Steve K4HG

On Jan 31, 2014, at 4:03 PM, Tom Hayward <esarfl at gmail.com> wrote:

> On Fri, Jan 31, 2014 at 11:46 AM, Steve Dimse <steve at dimse.com> wrote:
>> Two separate guys running APRX28 make me worry there is a subtle bug in the code,
> 
> Are you just blindly guessing at what software this is? APRS to calls
> are assigned and documented:
> http://www.aprs.org/tocalls.txt
> 
> You can also just look at the guy's packets. He is transmitting the
> name of the software, version, and even source code commit number:
> IR0UAQ>BEACON,TCPIP*,qAC,T2LEIPZIG:APRX 2.08 SVN555
> 
> APRX 2.08, commit 555.
> 
> Tom KD7LXL
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig