Re: [Xastir] Format for .geo files
Thanks. I can remove that email from the list and will do so shortly. Sorry for your loss. I have lost several close ham buddies over the last 10 years or so. On Wed, Apr 20, 2022 at 11:05 AM wrote: > Don't know if you guys know it or not, but Don Russell passed away last > year, April 6th. He and I were very close friends. I don't know how many of > you knew him or talked to him much but I thought I'd reply to this list > since he was huge into HAM radio. All of his email comes to me now, but if > you want to remove his email address from the list you may do so. > > I don't know anything about HAM radio but I always remember him saying he > had a lot of gear (and I've seen it) and that "People depend on this stuff > so let Dad know if I'm ever gone."... so I don't know if when we unplugged > it all everyone who was using it was like what the heck is going on, but... > if one of you were wondering, there's your reason why... > > Big loss... I still have a hard time getting over it. He and I spoke > weekly for 25 years... > > Woody > wo...@gpgsecure.com > wo...@woodyhughes.com > > > > > --- Original Message --- > On Wednesday, April 20th, 2022 at 11:55 AM, RileyC < > rufus.rizz...@gmail.com> wrote: > > > > > > > > Thanks! Yes I've done that and converted a few. When I point Xastir to my > > Offline directory with the converted files, there are no maps. > > > > The documentation reads like I need a type of index file. I got the USGS > > csv indexes that match coordinates to the image files. I'm looking for > the > > needed formatting for that index file. That's what I'm naively calling a > > .geo file. > > > > I can convert the USGS csv to the correct format, but I want to know what > > that format is. > > > > Thanks! > > > > Riley > > > > On Wed, Apr 20, 2022, 11:10 Tom Russo ru...@bogodyn.org wrote: > > > > > ".geo" files are not for referencing geopdfs, they're for > georeferencing > > > images in PNG or JPG format (like a scanned image or something). > > > > > > Geopdfs are newer than any map type coded into Xastir, and there is no > > > native support for them at all. > > > > > > You can, however, convert geopdfs to GeoTIFF format, and they'll work > just > > > fine. > > > Since they have georeferencing information in the file already, you > need no > > > other additional files to do this. > > > > > > However, you do have to convert the file using a script called " > > > geopdf2gtiff.pl" > > > in the Xastir "scripts" directory, and this script requires that you > have > > > GDAL installed (it uses gdalinfo, gdalwarp, and the "rgb2pct.py" script > > > provided by GDAL). > > > > > > On Wed, Apr 20, 2022 at 10:40:00AM -0400, we recorded a bogon-computron > > > collision of the rufus.rizz...@gmail.com flavor, containing: > > > > > > > I'm working on getting USGS offline maps, and I'm having problems > > > > bringing > > > > them up in Xastir. Is there a format documented for the indexing of > the > > > > maps? > > > > > > > > The link in the documentation is broken: > > > > http://data.geocomm.com/quadindex/ > > > > > > > > I've got the USGS index files that point to the Geopdfs, and can > convert > > > > them so they will work like the link mentions, but I'm unsure how to > > > > format > > > > them. > > > > > > > > If I can get it working I can share my script. > > > > > > > > Thanks! > > > > > > > > Riley > > > > Kf4emz > > > > ___ > > > > Xastir mailing list > > > > Xastir@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > -- > > > Tom Russo KM5VY > > > Tijeras, NM > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] How to get CWOP weather on APRS network
Thanks! On Thu, Jan 20, 2022 at 1:34 PM Tom Russo wrote: > > On Thu, Jan 20, 2022 at 02:07:41PM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > OK, I'll modify the xastir_udp_client documentation to note that injecting > > objects or items into Xastir using the same callsign/SSID as Xastir's will > > cause Xastir to own the object and retransmit it in the same way that it > > does > > objects created via its interface. > > Done. > > Also, tested and confirmed correct --- if you actually match the callsign and > SSID, Xastir adopts, otherwise it doesn't. > > > > On Thu, Jan 20, 2022 at 01:49:09PM -0600, we recorded a bogon-computron > > collision of the flavor, containing: > > > On Thu, Jan 20, 2022 at 1:01 PM Curt Mills wrote: > > > > > > > > > > > Where it can be and advantage is if you're trying to inject > > > > objects/items into Xastir from some other interface, using > > > > xastir_udp_client to do this injection. > > > > > > > > > > That works and I have made use of it during bike events to translate SPOT > > > beacon position reports into xastir objects. (Along with a few other > > > similar uses.) > > > > > > - Jason > > > > > > -- > > > "The problem with quotes on the Internet is that it is often difficult to > > > verify their authenticity." - *Abraham Lincoln* > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > -- > > Tom RussoKM5VY > > Tijeras, NM > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > [n-z][a-m] > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] How to get CWOP weather on APRS network
Yes, that description of how they get adopted fits my fuzzy recollection of same. Perhaps others who have used that side-effect feature can comment. It'd be good to add a blurb to the man-page about the possibility, so people don't get confused when things work differently than they expect. On Thu, Jan 20, 2022 at 11:29 AM km5vy Tom Russo wrote: > > On Thu, Jan 20, 2022 at 11:13:52AM -0800, we recorded a bogon-computron > collision of the flavor, containing: > > Commented-out lines: Seems to be a common complaint of yours these > > days. > > As someone who's day job involves maintaining an enormous legacy software > package written by some dozen different authors over 20+ years, code > readability and code rot is a major concern, and I'll bring it up often until > I retire from that job *and* start using a pencil instead of a computer in > day to day operation. > > Commented out code in version-controlled software, especially commented out > code that was inserted once 18 years ago and then promptly commented out, > has been the bane of my existence because of its impact on readability. > Worse, code inside those comments is often rotted out so that uncommenting it > would be disastrous. > > My position is that if it was commented out in 2005, the code in there is > no longer helping anyone and just serves to make it that much harder to > read and maintain. > > "git log -p" on a file will show all the changes made to that file since > it was created, and one can always just use the pager's search function to > look for specific old code that was removed. > > > > > Anyway... I was just mentioning the Xastir adoption of packets as a > > side-effect in case you wanted to add a blurb about that to the > > man-page as well. > > I don't have the opportunity to scope out when and how Xastir adopts packets > inserted this way right now, though I believe I have made use of the fact in > my old (no longer functional) DFing code --- inserting OBJECTS via TCP or UDP > into Xastir's ports does seem to let Xastir adopt them if you use the same > call. But it's been so long since I've done that I'm uncomfortable adding it > to the documentation without actually testing it out first. > > I think that's because objects created by xastir get handled by looping them > through the input processing, and then inserted into Xastir's own-object list > when they're recognized, at which point they get transmitted and added to > the "retransmit this periodically" process. Both objects created by Xastir > and those that come in through an interface get treated the same way. But I'd > actually have to revisit all the code to make sure this is true. > > And I'm pretty sure that non-object/item packets don't get the same treatment. > > > On Thu, Jan 20, 2022 at 11:07 AM km5vy Tom Russo wrote: > > > > > > The code is pretty hard to read and is peppered with blocks of > > > commented-out > > > code that have been that way since 2005. There used to be some attempt to > > > treat the injected stuff as third-party only if its callsign was different > > > from Xastir's, but all that is commented out and stuff injected by > > > xastir_udp_client is *always* treated as third-party. > > > > > > Whether it gets inserted into xastir's "own" packets and adopted for > > > retransmission is another question, but I don't think it does. > > > > > > When I tested this all out by hand, I didn't use the same SSID for the > > > injected packet, so I could tell the difference when I looked at aprs.fi > > > for whether it had been gated properly. Xastir retransmitted it fine, but > > > did not adopt it. > > > > > > Since it's not an object or item, I don't think Xastir would have > > > retransmitted > > > it anyway --- WeeWx's aprs extension creates a "weather station" packet > > > payload, > > > not a "weather object" payload. > > > > > > On Thu, Jan 20, 2022 at 11:00:57AM -0800, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > It's fuzzy in my memory now, but I believe there may be a side-effect > > > > in Xastir as well (which can be taken advantage of in some cases) > > > > where if the call and SSID are the same as the Xastir instance when > > > > injecting packets in via xastir_udp_client, Xastir can take up > > > > re-transmitting those packets at intervals. Like I said it's a bit > > > > fuzzy now as I haven't messed with that piece for some time. > > > > > > > > Where it can be and advantage is if you're trying to inject > > > > objects/items into Xastir from some other interface, using > > > > xastir_udp_client to do this injection. > > > > > > > > Of course the side-effect is if you don't desire Xastir to pick up the > > > > transmission as it's own and retransmit it. I believe this can be > > > > solved by using a different SSID and/or callsign for the injection. > > > > > > > > On Thu, Jan 20, 2022 at 10:50 AM Tom Russo wrote: > > > > > > > > > > Resurrecting an ancient thread, because Dj opened
Re: [Xastir] How to get CWOP weather on APRS network
Thinking about that another few seconds, the "Those of us who aren't as accomplished with Git" bit probably means just myself, as we have only three developers at present. On Thu, Jan 20, 2022 at 11:13 AM Curt Mills wrote: > > Commented-out lines: Seems to be a common complaint of yours these > days. Those of us who aren't as accomplished with Git, not using it > everyday, tend to keep possibly-useful code around in this form. Feel > free to get rid of such lines, at the expense of making it harder for > some of us to look up later in Git if we want to re-add or learn from > the unused bits of code. > > Anyway... I was just mentioning the Xastir adoption of packets as a > side-effect in case you wanted to add a blurb about that to the > man-page as well. > > On Thu, Jan 20, 2022 at 11:07 AM km5vy Tom Russo wrote: > > > > The code is pretty hard to read and is peppered with blocks of commented-out > > code that have been that way since 2005. There used to be some attempt to > > treat the injected stuff as third-party only if its callsign was different > > from Xastir's, but all that is commented out and stuff injected by > > xastir_udp_client is *always* treated as third-party. > > > > Whether it gets inserted into xastir's "own" packets and adopted for > > retransmission is another question, but I don't think it does. > > > > When I tested this all out by hand, I didn't use the same SSID for the > > injected packet, so I could tell the difference when I looked at aprs.fi > > for whether it had been gated properly. Xastir retransmitted it fine, but > > did not adopt it. > > > > Since it's not an object or item, I don't think Xastir would have > > retransmitted > > it anyway --- WeeWx's aprs extension creates a "weather station" packet > > payload, > > not a "weather object" payload. > > > > On Thu, Jan 20, 2022 at 11:00:57AM -0800, we recorded a bogon-computron > > collision of the flavor, containing: > > > It's fuzzy in my memory now, but I believe there may be a side-effect > > > in Xastir as well (which can be taken advantage of in some cases) > > > where if the call and SSID are the same as the Xastir instance when > > > injecting packets in via xastir_udp_client, Xastir can take up > > > re-transmitting those packets at intervals. Like I said it's a bit > > > fuzzy now as I haven't messed with that piece for some time. > > > > > > Where it can be and advantage is if you're trying to inject > > > objects/items into Xastir from some other interface, using > > > xastir_udp_client to do this injection. > > > > > > Of course the side-effect is if you don't desire Xastir to pick up the > > > transmission as it's own and retransmit it. I believe this can be > > > solved by using a different SSID and/or callsign for the injection. > > > > > > On Thu, Jan 20, 2022 at 10:50 AM Tom Russo wrote: > > > > > > > > Resurrecting an ancient thread, because Dj opened an issue on GitHub > > > > about it > > > > this week, and I tracked down what is happening here. I'm following up > > > > to > > > > the original thread to clear up the misunderstanding and get the answer > > > > into > > > > the mailing list archive where it could presumably be found in web > > > > searches. > > > > > > > > Dj had Xastir and WeeWx's APRS extension working, but only by modifying > > > > main.c. > > > > > > > > The reason for the suggested mods of main.c in the message I'm replying > > > > to > > > > is to work around some mistaken usage of xastir_udp_client, which I > > > > think > > > > may have been the result of some incomplete (or perhaps overly vague) > > > > documentation. > > > > > > > > xastir_udp_client does NOT insert the packet header "FROMCALL>TOCALL:" > > > > into > > > > the data passed to it on the command line, it does a straight insersion > > > > of > > > > the data passed to it directly into Xastir's incoming packet stream. > > > > And so > > > > one MUST include "FROMCALL>TOCALL:" at the beginning of the packet > > > > oneself. > > > > Some other APRS tools for injecting packets do this for you, but > > > > xastir_udp_client does not. > > > > > > > > Once injected, Xastir creates a third-party packet out of the data. > > > &g
Re: [Xastir] How to get CWOP weather on APRS network
Commented-out lines: Seems to be a common complaint of yours these days. Those of us who aren't as accomplished with Git, not using it everyday, tend to keep possibly-useful code around in this form. Feel free to get rid of such lines, at the expense of making it harder for some of us to look up later in Git if we want to re-add or learn from the unused bits of code. Anyway... I was just mentioning the Xastir adoption of packets as a side-effect in case you wanted to add a blurb about that to the man-page as well. On Thu, Jan 20, 2022 at 11:07 AM km5vy Tom Russo wrote: > > The code is pretty hard to read and is peppered with blocks of commented-out > code that have been that way since 2005. There used to be some attempt to > treat the injected stuff as third-party only if its callsign was different > from Xastir's, but all that is commented out and stuff injected by > xastir_udp_client is *always* treated as third-party. > > Whether it gets inserted into xastir's "own" packets and adopted for > retransmission is another question, but I don't think it does. > > When I tested this all out by hand, I didn't use the same SSID for the > injected packet, so I could tell the difference when I looked at aprs.fi > for whether it had been gated properly. Xastir retransmitted it fine, but > did not adopt it. > > Since it's not an object or item, I don't think Xastir would have > retransmitted > it anyway --- WeeWx's aprs extension creates a "weather station" packet > payload, > not a "weather object" payload. > > On Thu, Jan 20, 2022 at 11:00:57AM -0800, we recorded a bogon-computron > collision of the flavor, containing: > > It's fuzzy in my memory now, but I believe there may be a side-effect > > in Xastir as well (which can be taken advantage of in some cases) > > where if the call and SSID are the same as the Xastir instance when > > injecting packets in via xastir_udp_client, Xastir can take up > > re-transmitting those packets at intervals. Like I said it's a bit > > fuzzy now as I haven't messed with that piece for some time. > > > > Where it can be and advantage is if you're trying to inject > > objects/items into Xastir from some other interface, using > > xastir_udp_client to do this injection. > > > > Of course the side-effect is if you don't desire Xastir to pick up the > > transmission as it's own and retransmit it. I believe this can be > > solved by using a different SSID and/or callsign for the injection. > > > > On Thu, Jan 20, 2022 at 10:50 AM Tom Russo wrote: > > > > > > Resurrecting an ancient thread, because Dj opened an issue on GitHub > > > about it > > > this week, and I tracked down what is happening here. I'm following up to > > > the original thread to clear up the misunderstanding and get the answer > > > into > > > the mailing list archive where it could presumably be found in web > > > searches. > > > > > > Dj had Xastir and WeeWx's APRS extension working, but only by modifying > > > main.c. > > > > > > The reason for the suggested mods of main.c in the message I'm replying to > > > is to work around some mistaken usage of xastir_udp_client, which I think > > > may have been the result of some incomplete (or perhaps overly vague) > > > documentation. > > > > > > xastir_udp_client does NOT insert the packet header "FROMCALL>TOCALL:" > > > into > > > the data passed to it on the command line, it does a straight insersion of > > > the data passed to it directly into Xastir's incoming packet stream. And > > > so > > > one MUST include "FROMCALL>TOCALL:" at the beginning of the packet > > > oneself. > > > Some other APRS tools for injecting packets do this for you, but > > > xastir_udp_client does not. > > > > > > Once injected, Xastir creates a third-party packet out of the data. Third > > > party packets look like > > > "xastircall>APX219,PATH1,PATH2...:}tpcall>tocall:..." > > > where "xastircall" is the call sign of the Xastir instance and "tpcall" > > > is the > > > call sign of the third party station (which may be the same as Xastir's). > > > When properly formatted, these packets show up in APRS clients (including > > > web > > > based ones like aprs.fi) as being from tpcall. > > > > > > The main.c changes Dj mentions here basically break the third-party > > > insertion > > > and mask the fact that he's left out the packet header in what he's > > > passed to > > > xastir_udp_client. The fact that he was leaving out "tpcall>tocall:" was > > > why his packets were being flagged as invalid without those > > > modifications (the stuff after the "}" was incomplete). > > > > > > Once that usage error is corrected, Xastir should be able to take WeeWx's > > > data > > > just fine. So the script to do the insertion would be: > > > > > > #!/bin/bash > > > # > > > weatherpacket=`cat /dev/shm/aprs.pkt` > > > /usr/local/xastir/bin/xastir_udp_client localhost 2023 YOURCALL > > > -to_rf > > > "YOURCALL>APX219:$weatherpacket" > > > > > > > > > with the obvious
Re: [Xastir] How to get CWOP weather on APRS network
It's fuzzy in my memory now, but I believe there may be a side-effect in Xastir as well (which can be taken advantage of in some cases) where if the call and SSID are the same as the Xastir instance when injecting packets in via xastir_udp_client, Xastir can take up re-transmitting those packets at intervals. Like I said it's a bit fuzzy now as I haven't messed with that piece for some time. Where it can be and advantage is if you're trying to inject objects/items into Xastir from some other interface, using xastir_udp_client to do this injection. Of course the side-effect is if you don't desire Xastir to pick up the transmission as it's own and retransmit it. I believe this can be solved by using a different SSID and/or callsign for the injection. On Thu, Jan 20, 2022 at 10:50 AM Tom Russo wrote: > > Resurrecting an ancient thread, because Dj opened an issue on GitHub about it > this week, and I tracked down what is happening here. I'm following up to > the original thread to clear up the misunderstanding and get the answer into > the mailing list archive where it could presumably be found in web searches. > > Dj had Xastir and WeeWx's APRS extension working, but only by modifying > main.c. > > The reason for the suggested mods of main.c in the message I'm replying to > is to work around some mistaken usage of xastir_udp_client, which I think > may have been the result of some incomplete (or perhaps overly vague) > documentation. > > xastir_udp_client does NOT insert the packet header "FROMCALL>TOCALL:" into > the data passed to it on the command line, it does a straight insersion of > the data passed to it directly into Xastir's incoming packet stream. And so > one MUST include "FROMCALL>TOCALL:" at the beginning of the packet oneself. > Some other APRS tools for injecting packets do this for you, but > xastir_udp_client does not. > > Once injected, Xastir creates a third-party packet out of the data. Third > party packets look like "xastircall>APX219,PATH1,PATH2...:}tpcall>tocall:..." > where "xastircall" is the call sign of the Xastir instance and "tpcall" is the > call sign of the third party station (which may be the same as Xastir's). > When properly formatted, these packets show up in APRS clients (including web > based ones like aprs.fi) as being from tpcall. > > The main.c changes Dj mentions here basically break the third-party insertion > and mask the fact that he's left out the packet header in what he's passed to > xastir_udp_client. The fact that he was leaving out "tpcall>tocall:" was > why his packets were being flagged as invalid without those > modifications (the stuff after the "}" was incomplete). > > Once that usage error is corrected, Xastir should be able to take WeeWx's data > just fine. So the script to do the insertion would be: > > #!/bin/bash > # > weatherpacket=`cat /dev/shm/aprs.pkt` > /usr/local/xastir/bin/xastir_udp_client localhost 2023 YOURCALL -to_rf > "YOURCALL>APX219:$weatherpacket" > > > with the obvious modification to make it correct for your call sign. This > will work with Xastir unmodified, and is as xastir_udp_client was meant > to be invoked. > > I have examined the xastir_udp_client man page and found it to leave too much > to interpretation. I edited it and added more notes about how it really works > so that perhaps it will be easier for others to grok in the future. If anyone > still finds it confusing, I can modify it further. > > On Sat, Oct 31, 2020 at 08:30:18PM -0400, we recorded a bogon-computron > collision of the flavor, containing: > > On 10/30/2020 1:07 AM, Steven Morrison wrote: > > > I can configure the WeeWx program to generate a report and send it to the > > xastir Pi, but how can i receive that report and transmit it in xastir? > > > > > > I'm doing it as follows in Linux (Raspberry Pi) with both WeeWx and Xastir > > running on the same RPi, but you could easily rsync the /dev/shm/aprs.kpt > > file to a different computer if needed. > > > > I have the APRS extension loaded into WeeWx > > (https://github.com/cavedon/weewx-aprs). > > > > In /etc/weewx/weewx.conf I have: > > > > # Options for extension 'aprs' > > [APRS] > > comment = "RaspberryPi-Xastir-Wx-Topsham,ME" > > include_position = 1 > > symbol_code = _ > > symbol_table = / > > output_filename = /dev/shm/aprs.pkt > > > > > > Then I have a crontab entry that does: > > > > 01,11,21,31,41,51 * * * * /home/xastir/scripts/send-weather-rf.sh > > > /dev/null > > > > > > and the send-weather-rf.sh script looks like ( is my 4 digit APRS code): > > > > #!/bin/bash > > # > > weatherpacket=`cat /dev/shm/aprs.pkt` > > /usr/local/xastir/bin/xastir_udp_client localhost 2023 N1JOV -to_rf > > $weatherpacket > > > > > > I am using an older version of Xastar (2.1.1) compiled from source code, and > > had to make the following change in main.c to make the xastir_udp_client > > command work for the above. I do not know if this still needs to be done in
Re: [Xastir-dev] Switching string length discussion to here
Rgr. It's worth asking the question every few years to see if anything new has come along that can help portability as well as reliability. Sounds like nothing's come along yet. On Sun, Dec 19, 2021 at 2:48 PM km5vy Tom Russo wrote: > > On Sun, Dec 19, 2021 at 02:37:24PM -0800, we recorded a bogon-computron > collision of the flavor, containing: > > Ah, should have read everything more thoroughly... So by adding > > another library to Linux we might be able to use something better. > > I disagree: by adding another library, we're adding dependencies that could > just as easily be solved by using strncat correctly without any depedencies. > > The operative comment is: > > > > > strlcpy() and strlcat() are not standard, neither ISO C nor POSIX. So, > > > > their use in portable programs is impossible. > > > The fact that one can expect it to work in SOME places just fine and on linux > with extra libraries doesn't make it portable. > > Further on in that discussion are descriptions of multiple packages that > provide their own implementation of strlcat (just as we provide > xastir_snprintf > to provide the non-standard snprintf function), all different, just to > assure portability. > > That's a mess, and with as little developer energy as we have I do not > advocate adding an additional maintenance headache (either by tracking down > dependencies or providing our own implementation) if it can be avoided with > a little extra typing. > > > On Sun, Dec 19, 2021 at 2:36 PM Curt Mills wrote: > > > > > > Nope. I remember considering those before after a bunch of research. I > > > think they're on some BSD-derived systems but they're not on Linux. > > > > > > On Sun, Dec 19, 2021 at 2:33 PM Tom Russo wrote: > > > > > > > > On Sun, Dec 19, 2021 at 03:27:07PM -0700, we recorded a bogon-computron > > > > collision of the flavor, containing: > > > > > On Sun, Dec 19, 2021 at 03:25:28PM -0700, we recorded a > > > > > bogon-computron collision of the flavor, > > > > > containing: > > > > > > On Sun, Dec 19, 2021 at 03:12:50PM -0600, we recorded a > > > > > > bogon-computron collision of the flavor, > > > > > > containing: > > > > > > > There is also strlcat. > > > > > > > > > > > > Are these in the C standard, snprintf? > > > > > > > > > > "unlike snprintf" > > > > > > > > It appears that they are not standard in either ISO or POSIX standards. > > > > > > > > From > > > > https://stackoverflow.com/questions/2114896/why-are-strlcpy-and-strlcat-considered-insecure > > > > > > > > strlcpy() and strlcat() are not standard, neither ISO C nor POSIX. So, > > > > their use in portable programs is impossible. In fact, strlcat() has > > > > two different variants: the Solaris implementation is different from > > > > the others for edge cases involving length 0. This makes it even less > > > > useful > > > > than otherwise. > > > > > > > > From the same discussion: > > > > > > > > This API has been adopted by most modern operating systems and many > > > > standalone software packages, including OpenBSD (where it originated), > > > > Sun Solaris, FreeBSD, NetBSD, the Linux kernel, rsync and the GNOME > > > > project. > > > > The notable exception is the GNU standard C library, glibc [12], whose > > > > maintainer steadfastly refuses to include these improved APIs, > > > > labelling > > > > them "horribly inefficient BSD crap" [4], despite prior evidence that > > > > they > > > > are faster is most cases than the APIs they replace [13]. > > > > > > > > That is why they are not available in glibc, but it is not true that > > > > they > > > > are not available on Linux. They are available on Linux in libbsd: > > > > > > > > https://libbsd.freedesktop.org/ > > > > > > > > > > > > -- > > > > Tom RussoKM5VY > > > > Tijeras, NM > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > > [n-z][a-m] > > > > > > > > ___ > > > > Xastir-dev mailing list > > > > Xastir-dev@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir-dev > > > > > > > > > > > > -- > > > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com > > > > > > > > -- > > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
Re: [Xastir-dev] Switching string length discussion to here
Ah, should have read everything more thoroughly... So by adding another library to Linux we might be able to use something better. On Sun, Dec 19, 2021 at 2:36 PM Curt Mills wrote: > > Nope. I remember considering those before after a bunch of research. I > think they're on some BSD-derived systems but they're not on Linux. > > On Sun, Dec 19, 2021 at 2:33 PM Tom Russo wrote: > > > > On Sun, Dec 19, 2021 at 03:27:07PM -0700, we recorded a bogon-computron > > collision of the flavor, containing: > > > On Sun, Dec 19, 2021 at 03:25:28PM -0700, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > On Sun, Dec 19, 2021 at 03:12:50PM -0600, we recorded a bogon-computron > > > > collision of the flavor, containing: > > > > > There is also strlcat. > > > > > > > > Are these in the C standard, snprintf? > > > > > > "unlike snprintf" > > > > It appears that they are not standard in either ISO or POSIX standards. > > > > From > > https://stackoverflow.com/questions/2114896/why-are-strlcpy-and-strlcat-considered-insecure > > > > strlcpy() and strlcat() are not standard, neither ISO C nor POSIX. So, > > their use in portable programs is impossible. In fact, strlcat() has > > two different variants: the Solaris implementation is different from > > the others for edge cases involving length 0. This makes it even less > > useful > > than otherwise. > > > > From the same discussion: > > > > This API has been adopted by most modern operating systems and many > > standalone software packages, including OpenBSD (where it originated), > > Sun Solaris, FreeBSD, NetBSD, the Linux kernel, rsync and the GNOME > > project. > > The notable exception is the GNU standard C library, glibc [12], whose > > maintainer steadfastly refuses to include these improved APIs, labelling > > them "horribly inefficient BSD crap" [4], despite prior evidence that they > > are faster is most cases than the APIs they replace [13]. > > > > That is why they are not available in glibc, but it is not true that they > > are not available on Linux. They are available on Linux in libbsd: > > > > https://libbsd.freedesktop.org/ > > > > > > -- > > Tom RussoKM5VY > > Tijeras, NM > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > [n-z][a-m] > > > > ___ > > Xastir-dev mailing list > > Xastir-dev@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir-dev > > > > -- > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
Re: [Xastir-dev] Switching string length discussion to here
Nope. I remember considering those before after a bunch of research. I think they're on some BSD-derived systems but they're not on Linux. On Sun, Dec 19, 2021 at 2:33 PM Tom Russo wrote: > > On Sun, Dec 19, 2021 at 03:27:07PM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > On Sun, Dec 19, 2021 at 03:25:28PM -0700, we recorded a bogon-computron > > collision of the flavor, containing: > > > On Sun, Dec 19, 2021 at 03:12:50PM -0600, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > There is also strlcat. > > > > > > Are these in the C standard, snprintf? > > > > "unlike snprintf" > > It appears that they are not standard in either ISO or POSIX standards. > > From > https://stackoverflow.com/questions/2114896/why-are-strlcpy-and-strlcat-considered-insecure > > strlcpy() and strlcat() are not standard, neither ISO C nor POSIX. So, > their use in portable programs is impossible. In fact, strlcat() has > two different variants: the Solaris implementation is different from > the others for edge cases involving length 0. This makes it even less useful > than otherwise. > > From the same discussion: > > This API has been adopted by most modern operating systems and many > standalone software packages, including OpenBSD (where it originated), > Sun Solaris, FreeBSD, NetBSD, the Linux kernel, rsync and the GNOME project. > The notable exception is the GNU standard C library, glibc [12], whose > maintainer steadfastly refuses to include these improved APIs, labelling > them "horribly inefficient BSD crap" [4], despite prior evidence that they > are faster is most cases than the APIs they replace [13]. > > That is why they are not available in glibc, but it is not true that they > are not available on Linux. They are available on Linux in libbsd: > > https://libbsd.freedesktop.org/ > > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir-dev mailing list > Xastir-dev@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir-dev -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
[Xastir-dev] Switching string length discussion to here
Tom, Thanks for your recent explanation in the issue discussion (Issue #188). This is good general "string" talk and applicable to a wide range of code. For that reason I'm moving the discussion here so it's more easily found later, instead of hidden in Github issue comments. Pardon me while I summarize my limited knowledge of "strings" at this point: There aren't actually strings in C, only null-terminated character buffers. We can't run past the end or else we read/write from other stuff in memory. In Xastir we often use character buffers of size MAX_DEVICE_BUFFER, which is the case for the Opentrac code. At one point we got rid of almost all of the strnXX() type of calls, switching to xastir_snprintf() instead... Perhaps the Opentrac routines were coded up later or weren't converted at the time. >From Tom: - "There was a lot if incorrect use of strncat in Xastir, mostly using incorrect values of "n" --- it's supposed to be the maximum number of characters that can fit into the destination string, and in many cases the code had been written to specify that number as the number of characters to copy out of the source string instead. We fixed a lot of that, but the opentrac code had a lot of it. The "right" fix is to fix the strncat calls so that one keeps track of how much room is left in the destination string, and use that as the"n" in strncat." - I can certainly do that last but it seems like a lot of busy work in C. Other languages have string functions which handle all of this. Are there any C libraries that make it easier these days? I know I couldn't find a good one before and that's why xastir_snprintf() came about. -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
Re: [Xastir] [notificati...@github.com: [Xastir/Xastir] SSL cert expired (#177)]
Yea. Done. On Tue, May 25, 2021 at 7:58 AM Tom Russo wrote: > > Yeah, the SSL certificate for xastir.org looks like it expired on March 25th. > > Curt, that's owned by you these days, right? > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > > > > -- Forwarded message -- > From: Dennis Boone > To: "Xastir/Xastir" > Cc: Subscribed > Bcc: > Date: Mon, 24 May 2021 20:10:53 -0700 > Subject: [Xastir/Xastir] SSL cert expired (#177) > I notice the SSL cert on xastir.org is expired. > > -- > You are receiving this because you are subscribed to this thread. > Reply to this email directly or view it on GitHub: > https://github.com/Xastir/Xastir/issues/177___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Xastir down after upgrade to OSX 11.3 " Big Sur"
Add a tag to the repo which indicates non-C-compatible systems aren't supported from here on out and document that tag in the HOWTO's or README's. Good 'nuf. On Tue, May 11, 2021 at 9:12 AM Tom Russo wrote: > > So, here's a thing to ask the community at large: > > Is there anyone left trying to run Xastir on really, really ancient operating > systems? > > A lot of the things that the most recent autocof is flagging as "obsolete" > like "AC_HEADER_STDC" and "AC_HEADER_TIME" is obsolete ONLY because most > modern > systems are so compatible with each other that these things are almost never > needed anymore. They were the norm back when people were running all sorts > of proprietary Unix systems like Slowlaris, AIX, etc., and these systems had > compilers that predated most POSIX standards. > > These days there are very clear standards that all modern systems abide by, > and this sort of clumsy portability hackage is obsolescent. The GNU folks > are increasingly deprecating things that harken back to such old systems. > > I am fixing the actually obsolete autoconf stuff that *isn't* specifically > targeted at backward portability to ancient systems, which will fix most of > the warnings shown in this email (like the AC_LANG, AC_TRY, etc. warnings), > as these all have straightforward equivalents in modern autoconf that have > been present in all versions of autoconf since 2006. > > BUt removing things like AC_HEADER_STDC and AC_HEADER_TIME and friends also > means removing all the clumsy portability code in Xastir source that NEEDS > those probes, along with a number of completely unnecessary probes for > standard > POSIX functions and the ifdefs that work around their absence. That is more > than I can do in a quick hacking run in between longer hacking runs as part of > my day job. > > It would be a good idea at some point to declare that newer versions of Xastir > will only run on systems that support the C standard, and not on > retrocomputing > platforms that use proprietary, pre-standard compilers. Then we can actually > remove a lot of unnecessary portability kludges from the late 90s. > > In the meantime, however, new users of Xastir will start seeing more of these > confusing warnings from "boostrap" that imply something is wrong and telling > them to run "autoupdate" when they really should just ignore the warnings. > > On Tue, May 11, 2021 at 09:37:12AM -0600, we recorded a bogon-computron > collision of the flavor, containing: > > The things that autoconf is complaining about are "obsolete" as of autoconf > > 2.60, and Xastir's autoconf is meant to be compatible with much older > > versions. > > > > It looks like 2.60 is old enough (2006) that it should be no problem at all > > to update our configure process to require it instead of 2.53, and fix > > these antiquated uses. I'm testing that now. > > > > I second Jason's suggestion that you should clean your build directory > > before > > trying to rebuild Xastir on a newly upgraded system. > > > > I do not recommend that you run autoupdate, just let autoconf complain about > > the obsolete uses for now. > > > > On Tue, May 11, 2021 at 09:19:02AM -0500, we recorded a bogon-computron > > collision of the flavor, containing: > > > Hello. > > > > > > I was able to build xastir on 11.3.1, so this may be local issue. My first > > > suggestion is doing a "make clean" and then rebuilding. From your output > > > it > > > looks like you may have old .o files left over from a previous build. > > > > > > If that doesn't work, my next suggestion would be to see if you have up to > > > date X 11 libraries installed (sounds like you get them from macports.) > > > > > > 73 > > > - Jason > > > > > > On Tue, May 11, 2021 at 8:38 AM f1mhv wrote: > > > > > > > Dear Group, > > > > > > > > I have updated the laptop to ?? Big Sur ?? OSX 10.3.1 including Xcode > > > > tools > > > > and Macports. I tried du rebuild from source following git pull and > > > > here is > > > > what i got: > > > > > > > > " Xastir % bash bootstrap.sh > > > > 6) Removing autom4te.cache directory... > > > > 5) Running aclocal... > > > > 4) Running autoheader... > > > > 3) Running autoconf... > > > > configure.ac:50: warning: The macro `AC_GNU_SOURCE' is obsolete. > > > > configure.ac:50: You should run autoupdate. > > > > ./lib/autoconf/specific.m4:312: AC_GNU_SOURCE is expanded from... > > > > configure.ac:50: the top level > > > > configure.ac:71: warning: The macro `AC_LANG_C' is obsolete. > > > > configure.ac:71: You should run autoupdate. > > > > ./lib/autoconf/c.m4:72: AC_LANG_C is expanded from... > > > > acinclude.m4:568: ACX_PTHREAD is expanded from... > > > > configure.ac:71: the top level > > > > configure.ac:71: warning: The macro `AC_TRY_LINK' is obsolete. > > > > configure.ac:71: You should run autoupdate. > > > > ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from... > > > > acinclude.m4:568: ACX_PTHREAD is expanded from... > > > >
Re: [Xastir] WX-Radar
Interesting. Xastir supports WMS, so it's do-able. Might not take a tremendous amount of effort either. On Tue, Apr 27, 2021 at 2:46 PM David Flood wrote: > > Hello Udo, > > The NWS stopped producing easily processable/usable data and instead switched > to complicated data files. If someone has some ATUs and wants to figure out > how to parse the data it might be loadable into Xastir. But since the data > is changing/updated on a regular basis you'd have to write an entirely > separate program that fetches the new data on a schedule and then "serves" it > up to Xastir. > > Here's the current data collection: > > https://opengeo.ncep.noaa.gov/geoserver/www/index.html > > I suppose, if someone had the programming skills and a spare server or two > they could light up a Weather Server that does the processing but you still > would then need to figure out how to modify Xastir to work with that server. > And as soon as it all was working the NWS would change everything once again. > > Dave > KD7MYC > > > -Original Message- > From: Xastir On Behalf Of Udo Visintini > Sent: Tuesday, April 27, 2021 1:48 PM > To: Xastir@lists.xastir.org > Subject: [Xastir] WX-Radar > > Hi, > > I used for years the RIDGE Radar files created by K1KWD > > I know the weather service has changed the layout and the URL > > I there anybody who know a new URL, or a way to get those radar overlay > files, so it can be used by xastir's mapping system. > > Thanks and 73 de kf4kul > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Object file location?
~/.xastir/config/object.log ~/.xastir/config/tactical_calls.log ~/.xastir/config/CAD_object.log These are all in your home directory. On Wed, Feb 10, 2021 at 12:47 AM f1mhv wrote: > > Good morning Group, > > On Debian based where can i find the file containing the objects i created in > order to export-it? > > 73 de Cyril - DF1CHB - F1MHV > > > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
No. Once that has been applied (assuming the executable is in that spot anyway, change the path to match yours) and the binary is owned by root, Xastir will change the effective user ID to "root" at the point it needs to open a port, then will go back to the user you started Xastir from immediately after, so it's reasonably safe security-wise. What it will do is tell you whether there's a permission issue or user/group ownership issue with that port. Xastir should be able to open the port in that instance. On Mon, Feb 8, 2021 at 1:06 PM Eric Chamberlain wrote: > > Curt, are you asking if I'm able to execute the /usr/local/bin/xastir when > 4755 has been applied? > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
As a check about the ownership/permissions on the port, you might do a "chmod 4755 /usr/local/bin/xastir" as root to set the SUID bit in the executable. If Xastir works for you then, it's an ownership/group/permissions issue with that port. We need to set that bit on Linux in order to open an AX.25 networking port. That's its main use. On Mon, Feb 8, 2021 at 12:36 PM Eric Chamberlain wrote: > > It's sending NMEA because I accidentally set that on the transmitter, I > vaguely remember that being set on the list of things. So that's my bad. > But yeah it still hangs on the open(). I added NOBLOCK to the flags to force > it to come back, it returns with an errno 2, no such file or directory. It > appears to open the port for reading, ie it doesn't send a fail when it > attempts to read, but instead throws an errno 35, resource temporarily > unavailable, when attempting to write to the port. I did a chown root:wheel > to the xastir executable so that it would match the /dev/tty.usbserial-1430, > but that didn't work either. > > I'll go grab the transmitter and fix that in the meanwhile. > > From: "Curt Mills" > > Since it's not KISS you can _try_ the Serial TNC interface with it, > but I don't know what the command-set for the TNC4 looks like so don't > know whether Xastir would be able to talk to it. If it's TAPR TNC-2 > compatible to some degree, then it might work. > > On Mon, Feb 8, 2021 at 11:21 AM Curt Mills wrote: > > > > If putty sees that, then it's not KISS. That looks like normal TNC > > ASCII output, not KISS. > > > > On Mon, Feb 8, 2021 at 11:16 AM Eric Chamberlain > > wrote: > > > > > > The code hangs at this line, so the mutex is opened. > > > port_data[port].channel = open(port_data[port].device_name, > > > O_RDWR|O_NOCTTY); > > > > > > Jason, I think its in KISS. Regarding the readable payload with binary > > > garbage, I'm getting it. Here's some of what putty sees, so I think the > > > baud rate is good too. > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:>MT-Omega v1.47 > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190857,A,4015.8900,N,07946.0796,W,000,057,080221,,*03/TT3 > > > ROCKET|!"#c'6|!w!x! > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190958,A,4015.8927,N,07946.0753,W,000,169,080221,,*0D|!##c':|!w:Q! > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191059,A,4015.8942,N,07946.0762,W,000,169,080221,,*05|!$#c'<|!wGY! > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191159,A,4015.8922,N,07946.0766,W,000,169,080221,,*06|!%#c'>|!w5]! > > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191300,A,4015.8922,N,07946.0776,W,000,169,080221,,*09/TT3 > > > ROCKET|!
Re: [Xastir] Tinytrak TNC not opening interface
Since it's not KISS you can _try_ the Serial TNC interface with it, but I don't know what the command-set for the TNC4 looks like so don't know whether Xastir would be able to talk to it. If it's TAPR TNC-2 compatible to some degree, then it might work. On Mon, Feb 8, 2021 at 11:21 AM Curt Mills wrote: > > If putty sees that, then it's not KISS. That looks like normal TNC > ASCII output, not KISS. > > On Mon, Feb 8, 2021 at 11:16 AM Eric Chamberlain > wrote: > > > > The code hangs at this line, so the mutex is opened. > > port_data[port].channel = open(port_data[port].device_name, > > O_RDWR|O_NOCTTY); > > > > Jason, I think its in KISS. Regarding the readable payload with binary > > garbage, I'm getting it. Here's some of what putty sees, so I think the > > baud rate is good too. > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:>MT-Omega v1.47 > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190857,A,4015.8900,N,07946.0796,W,000,057,080221,,*03/TT3 > > ROCKET|!"#c'6|!w!x! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190958,A,4015.8927,N,07946.0753,W,000,169,080221,,*0D|!##c':|!w:Q! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191059,A,4015.8942,N,07946.0762,W,000,169,080221,,*05|!$#c'<|!wGY! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191159,A,4015.8922,N,07946.0766,W,000,169,080221,,*06|!%#c'>|!w5]! > > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191300,A,4015.8922,N,07946.0776,W,000,169,080221,,*09/TT3 > > ROCKET|!
Re: [Xastir] Tinytrak TNC not opening interface
If putty sees that, then it's not KISS. That looks like normal TNC ASCII output, not KISS. On Mon, Feb 8, 2021 at 11:16 AM Eric Chamberlain wrote: > > The code hangs at this line, so the mutex is opened. > port_data[port].channel = open(port_data[port].device_name, O_RDWR|O_NOCTTY); > > Jason, I think its in KISS. Regarding the readable payload with binary > garbage, I'm getting it. Here's some of what putty sees, so I think the baud > rate is good too. > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:>MT-Omega v1.47 > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190857,A,4015.8900,N,07946.0796,W,000,057,080221,,*03/TT3 > ROCKET|!"#c'6|!w!x! > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,190958,A,4015.8927,N,07946.0753,W,000,169,080221,,*0D|!##c':|!w:Q! > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191059,A,4015.8942,N,07946.0762,W,000,169,080221,,*05|!$#c'<|!wGY! > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191159,A,4015.8922,N,07946.0766,W,000,169,080221,,*06|!%#c'>|!w5]! > KC3OBB-1>APT314,WIDE1-1,WIDE2-1:$GPRMC,191300,A,4015.8922,N,07946.0776,W,000,169,080221,,*09/TT3 >
Re: [Xastir] Tinytrak TNC not opening interface
That code looks familiar for some reason... Look at xastir/src/util.c On Mon, Feb 8, 2021 at 8:28 AM Eric Chamberlain wrote: > > Tracing the hang further, it gets to the begin_critical_section mutex call, > so it's blocking on that, but it's an extern reference in util.h. Do you > happen to know what library that is sourced from? > > > > > From: "Eric Chamberlain" > > I went ahead and added my userid to the wheel group but no effect. Also I ran > debug level 3. It gave me the Opening a Serial KISS device output before > hanging. I added some output to the source and remade the file to output the > other serial variables, here's what came out. > > Port Available 1 > Opening a Serial KISS TNC device > Dev Type 10 > Dev baud rate 19200 > Dev style 0 > > I'm going to look at what comes next after this add_device call. > > > From: "Curt Mills" > > The permissions are R/W for user/group/other, so I don't think you > need to add yourself to the wheel group for this. Perhaps one of the > OSX guys can comment on that though. I don't run OSX. > > On Mon, Feb 8, 2021 at 7:30 AM Eric Chamberlain > wrote: > > > > I haven't set debug yet, but I wanted to respond with the ls -l output > > first. > > crw-rw-rw- 1 root wheel 18, 4 Feb 8 10:26 /dev/tty.usbserial-1430 > > > > I'm logged in as user ericchamberlain and groups looks like: > > staff access_bpf everyone localaccounts _appserverusr admin _appserveradm > > _lpadmin _appstore _lpoperator _developer _analyticsusers > > com.apple.access_ftp com.apple.access_screensharing com.apple.access_ssh > > com.apple.access_remote_ae com.apple.sharepoint.group.1 > > > > So yeah, I'm not a member of wheel group. > > > > > > > > > > From: "Curt Mills" > > > > File -> Configure -> Change Debug Level can change it while it's > > running. You need to start Xastir from a console/xterm/etc in order to > > see them. > > > > See the file DEBUG_LEVELS for info on which ones to try. > > > > The sources are the result of a LOT of people over the years, starting > > with Frank Gianandrea who initially wrote it. Thank them. ;-) > > > > The port to use if you're using a TNC4 in KISS mode is the "Serial > > KISS TNC" interface. I've used that with H/W full-blown TNC's and with > > my TNC-X. > > > > More than likely it's a group/permissions problem with the interface. > > Do an "ls -l" against the port you're using and report back with the > > string for it including owner/group/permissions. > > > > Also report back what "groups" shows when logged-in as the user you're > > starting Xastir as. BTW: Don't run Xastir as root. > > > > > > On Mon, Feb 8, 2021 at 6:58 AM Eric Chamberlain > > wrote: > > > > > > Hey Curt. I've seen your comments in the source code, thanks for your > > > work. I've used both serial TNC interface and serial KISS TNC interface. > > > Based on the /dev/cu comment, I guess it hangs because of blocking(?). I > > > don't believe there is a permission on that port. I can apply a generic > > > username (guest) in putty with the autologin username without problem. > > > > > > Is there a debugging #define in the source I can build against to get > > > more information while the interface is opening? > > > > > > > > > > > > > > > From: "Curt Mills" > > > > > > Which type of interface are you using in Xastir? > > > > > > Did you add your username to the dialout group? > > > > > > What are the permissions on the port you're trying to use? > > > > > > On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain > > > wrote: > > > > > > > > That certainly prevents the port from blocking. The interface in xastir > > > > returns as 'up' but it doesn't appear to be reading packets off the TNC > > > > in the view-incoming data window. Looking in putty it still shows the > > > > incoming packets. So its not quite fixed yet. > > > > > > > > > > > > > > > > > > > > From: "Jason KG4WSV" > > > > > > > > Try the /dev/cu.whatever device special file. > > > > > > > > It’s been a few years but when I hit the same problem (well, Kermit not > > > > putty) switching to cu did the trick. > > > > > > > > -Jason > > > > > > > > > On Feb
Re: [Xastir] Tinytrak TNC not opening interface
The permissions are R/W for user/group/other, so I don't think you need to add yourself to the wheel group for this. Perhaps one of the OSX guys can comment on that though. I don't run OSX. On Mon, Feb 8, 2021 at 7:30 AM Eric Chamberlain wrote: > > I haven't set debug yet, but I wanted to respond with the ls -l output first. > crw-rw-rw- 1 root wheel 18, 4 Feb 8 10:26 /dev/tty.usbserial-1430 > > I'm logged in as user ericchamberlain and groups looks like: > staff access_bpf everyone localaccounts _appserverusr admin _appserveradm > _lpadmin _appstore _lpoperator _developer _analyticsusers > com.apple.access_ftp com.apple.access_screensharing com.apple.access_ssh > com.apple.access_remote_ae com.apple.sharepoint.group.1 > > So yeah, I'm not a member of wheel group. > > > > > From: "Curt Mills" > > File -> Configure -> Change Debug Level can change it while it's > running. You need to start Xastir from a console/xterm/etc in order to > see them. > > See the file DEBUG_LEVELS for info on which ones to try. > > The sources are the result of a LOT of people over the years, starting > with Frank Gianandrea who initially wrote it. Thank them. ;-) > > The port to use if you're using a TNC4 in KISS mode is the "Serial > KISS TNC" interface. I've used that with H/W full-blown TNC's and with > my TNC-X. > > More than likely it's a group/permissions problem with the interface. > Do an "ls -l" against the port you're using and report back with the > string for it including owner/group/permissions. > > Also report back what "groups" shows when logged-in as the user you're > starting Xastir as. BTW: Don't run Xastir as root. > > > On Mon, Feb 8, 2021 at 6:58 AM Eric Chamberlain > wrote: > > > > Hey Curt. I've seen your comments in the source code, thanks for your work. > > I've used both serial TNC interface and serial KISS TNC interface. Based on > > the /dev/cu comment, I guess it hangs because of blocking(?). I don't > > believe there is a permission on that port. I can apply a generic username > > (guest) in putty with the autologin username without problem. > > > > Is there a debugging #define in the source I can build against to get more > > information while the interface is opening? > > > > > > > > > > From: "Curt Mills" > > > > Which type of interface are you using in Xastir? > > > > Did you add your username to the dialout group? > > > > What are the permissions on the port you're trying to use? > > > > On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain > > wrote: > > > > > > That certainly prevents the port from blocking. The interface in xastir > > > returns as 'up' but it doesn't appear to be reading packets off the TNC > > > in the view-incoming data window. Looking in putty it still shows the > > > incoming packets. So its not quite fixed yet. > > > > > > > > > > > > > > > From: "Jason KG4WSV" > > > > > > Try the /dev/cu.whatever device special file. > > > > > > It’s been a few years but when I hit the same problem (well, Kermit not > > > putty) switching to cu did the trick. > > > > > > -Jason > > > > > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > > > wrote: > > > > > > > > I've been trying to configure an interface to read the tinytrak4 TNC, > > > > which is supposed to operate as KISS according to their docs. When I > > > > run PuTTY on the /dev/tty.usbserial-1430 port I can see packets coming > > > > in from a test transmitter. I close putty and open xastir so the port > > > > isn't blocking. When I go to start the TNC interface, in mac it hangs > > > > without messages in the terminal window. On the putty it doesn't hang > > > > but there's nothing. There are never incoming packets from the view > > > > data window. Unfortunately, Byonics say they don't know much about > > > > xastir. I've tried this both on my mac and my raspberry. The cable > > > > setup works for programming and PuTTY, so I don't think its that or > > > > drivers. I think it comes down to settings. Is there anything I can try? > > > > ___ > > > > Xastir mailing list > > > > Xastir@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > ___ > > > Xastir mailing list > &g
Re: [Xastir] Tinytrak TNC not opening interface
File -> Configure -> Change Debug Level can change it while it's running. You need to start Xastir from a console/xterm/etc in order to see them. See the file DEBUG_LEVELS for info on which ones to try. The sources are the result of a LOT of people over the years, starting with Frank Gianandrea who initially wrote it. Thank them. ;-) The port to use if you're using a TNC4 in KISS mode is the "Serial KISS TNC" interface. I've used that with H/W full-blown TNC's and with my TNC-X. More than likely it's a group/permissions problem with the interface. Do an "ls -l" against the port you're using and report back with the string for it including owner/group/permissions. Also report back what "groups" shows when logged-in as the user you're starting Xastir as. BTW: Don't run Xastir as root. On Mon, Feb 8, 2021 at 6:58 AM Eric Chamberlain wrote: > > Hey Curt. I've seen your comments in the source code, thanks for your work. > I've used both serial TNC interface and serial KISS TNC interface. Based on > the /dev/cu comment, I guess it hangs because of blocking(?). I don't > believe there is a permission on that port. I can apply a generic username > (guest) in putty with the autologin username without problem. > > Is there a debugging #define in the source I can build against to get more > information while the interface is opening? > > > > > From: "Curt Mills" > > Which type of interface are you using in Xastir? > > Did you add your username to the dialout group? > > What are the permissions on the port you're trying to use? > > On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain > wrote: > > > > That certainly prevents the port from blocking. The interface in xastir > > returns as 'up' but it doesn't appear to be reading packets off the TNC in > > the view-incoming data window. Looking in putty it still shows the incoming > > packets. So its not quite fixed yet. > > > > > > > > > > From: "Jason KG4WSV" > > > > Try the /dev/cu.whatever device special file. > > > > It’s been a few years but when I hit the same problem (well, Kermit not > > putty) switching to cu did the trick. > > > > -Jason > > > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > > wrote: > > > > > > I've been trying to configure an interface to read the tinytrak4 TNC, > > > which is supposed to operate as KISS according to their docs. When I run > > > PuTTY on the /dev/tty.usbserial-1430 port I can see packets coming in > > > from a test transmitter. I close putty and open xastir so the port isn't > > > blocking. When I go to start the TNC interface, in mac it hangs without > > > messages in the terminal window. On the putty it doesn't hang but there's > > > nothing. There are never incoming packets from the view data window. > > > Unfortunately, Byonics say they don't know much about xastir. I've tried > > > this both on my mac and my raspberry. The cable setup works for > > > programming and PuTTY, so I don't think its that or drivers. I think it > > > comes down to settings. Is there anything I can try? > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir][http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir]] > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir] > > > > -- > Curt, WE7U http://xastir.org[http://xastir.org] http://www.sarguydigital.com > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir] > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Tinytrak TNC not opening interface
Which type of interface are you using in Xastir? Did you add your username to the dialout group? What are the permissions on the port you're trying to use? On Mon, Feb 8, 2021 at 4:31 AM Eric Chamberlain wrote: > > That certainly prevents the port from blocking. The interface in xastir > returns as 'up' but it doesn't appear to be reading packets off the TNC in > the view-incoming data window. Looking in putty it still shows the incoming > packets. So its not quite fixed yet. > > > > > From: "Jason KG4WSV" > > Try the /dev/cu.whatever device special file. > > It’s been a few years but when I hit the same problem (well, Kermit not > putty) switching to cu did the trick. > > -Jason > > > On Feb 7, 2021, at 8:44 PM, Eric Chamberlain > > wrote: > > > > I've been trying to configure an interface to read the tinytrak4 TNC, > > which is supposed to operate as KISS according to their docs. When I run > > PuTTY on the /dev/tty.usbserial-1430 port I can see packets coming in from > > a test transmitter. I close putty and open xastir so the port isn't > > blocking. When I go to start the TNC interface, in mac it hangs without > > messages in the terminal window. On the putty it doesn't hang but there's > > nothing. There are never incoming packets from the view data window. > > Unfortunately, Byonics say they don't know much about xastir. I've tried > > this both on my mac and my raspberry. The cable setup works for programming > > and PuTTY, so I don't think its that or drivers. I think it comes down to > > settings. Is there anything I can try? > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir[http://xastir.org/mailman/listinfo/xastir] > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
[Xastir] Fwd: OSX 10.15.7 Macports: configure: error: **** MOTIF LIBRARIES NOT FOUND ****
Forwarding to the list as well.
-- Forwarded message -
From: Curt Mills
Date: Mon, Feb 1, 2021 at 6:06 AM
Subject: Re: [Xastir] OSX 10.15.7 Macports: configure: error:
MOTIF LIBRARIES NOT FOUND
To: f1mhv
It's this section that's relevant:
configure:8614: result: no
configure:8675: checking for Motif headers
configure:8681: gcc -E -I/sw/include -I/opt/local/include
-I/usr/local/include -I/opt/local/include conftest.c
configure:8681: $? = 0
configure:8685: result: in default path
configure:8745: checking for Motif libraries
configure:8765: gcc -o conftest -g -O2 -pipe -W -Wall -Wpointer-arith
-Wstrict-prototypes -Wno-unused-parameter -I/sw/include
-I/opt/local/include -I/usr/local/include -I/opt/local/include
-L/sw/lib -L/opt/local/lib -L/usr/local/lib -L/opt/local/lib
conftest.c -lXm -lXm -lXt -lXext -lSM -lICE -lX11 -lcurl >&5
conftest.c:52:1: error: implicit declaration of function
'XmGetDestination' is invalid in C99
[-Werror,-Wimplicit-function-declaration]
XmGetDestination()
^
1 error generated.
The way this works: Xastir tries to do little example compiles with
each set of headers and libraries needed to add in various functions.
Some of those tests are for required pieces to compile Xastir, some
are for optional add-on libraries. Motif is required for Xastir.
In this case it's trying to compile a test program to use the library
function XmGetDestination() from the Motif library and failing.
Which method did you use to install Motif: Fink, Homebrew, or from sources?
I'll assume you're trying to use one of the HOWTO's from the
www.xastir.org project. If so, which one?
On Sun, Jan 31, 2021 at 8:52 PM f1mhv wrote:
>
> Good morning Tom & Curt,
>
> I encroached a bit more, i hope it’s enough?
>
> configure:8400: result: no
> configure:8408: checking whether byte ordering is bigendian
> configure:8423: gcc -c -g -O2 -pipe -W -Wall -Wpointer-arith
> -Wstrict-prototypes -Wno-unused-parameter -I/sw/include -I/opt/local/include
> -I/usr/local/include -I/opt/local/include conftest.c >&5
> configure:8423: $? = 0
> configure:8468: gcc -c -g -O2 -pipe -W -Wall -Wpointer-arith
> -Wstrict-prototypes -Wno-unused-parameter -I/sw/include -I/opt/local/include
> -I/usr/local/include -I/opt/local/include conftest.c >&5
> configure:8468: $? = 0
> configure:8486: gcc -c -g -O2 -pipe -W -Wall -Wpointer-arith
> -Wstrict-prototypes -Wno-unused-parameter -I/sw/include -I/opt/local/include
> -I/usr/local/include -I/opt/local/include conftest.c >&5
> conftest.c:55:4: error: use of undeclared identifier 'not'
> not big endian
> ^
> 1 error generated.
> configure:8486: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> | #define PACKAGE_NAME "xastir"
> | #define PACKAGE_TARNAME "xastir"
> | #define PACKAGE_VERSION "2.1.7"
> | #define PACKAGE_STRING "xastir 2.1.7"
> | #define PACKAGE_BUGREPORT "xas...@xastir.org"
> | #define PACKAGE_URL ""
> | #define PACKAGE "xastir"
> | #define VERSION "2.1.7"
> | #define PACKAGE "xastir"
> | #define VERSION "2.1.7"
> | #define XASTIR_TOCALL "APX217"
> | #define STDC_HEADERS 1
> | #define HAVE_SYS_TYPES_H 1
> | #define HAVE_SYS_STAT_H 1
> | #define HAVE_STDLIB_H 1
> | #define HAVE_STRING_H 1
> | #define HAVE_MEMORY_H 1
> | #define HAVE_STRINGS_H 1
> | #define HAVE_INTTYPES_H 1
> | #define HAVE_STDINT_H 1
> | #define HAVE_UNISTD_H 1
> | #define __EXTENSIONS__ 1
> | #define _ALL_SOURCE 1
> | #define _GNU_SOURCE 1
> | #define _POSIX_PTHREAD_SEMANTICS 1
> | #define _TANDEM_SOURCE 1
> | #define TNC_PORT "none"
> | #define GPS_PORT "none"
> | #define HAVE_PTHREAD 1
> | #define XASTIR_SYSTEM "Darwin"
> | #define HAVE_CONVERT 1
> | #define CONVERT_PATH "/opt/local/bin/gm convert"
> | #define HAVE_LPR 1
> | #define LPR_PATH "/usr/bin/lpr"
> | #define STIPPLE 1
> | #define HAVE_LIBXEXT 1
> | #define HAVE_LIBXT 1
> | #define HAVE_LIBXM 1
> | #define HAVE_SED 1
> | #define SED_PATH "/usr/bin/sed"
> | #define HAVE_MV 1
> | #define MV_PATH "/bin/mv"
> | #define HAVE_XFONTSEL 1
> | #define XFONTSEL_PATH "/opt/X11/bin/xfontsel"
> | #define HAVE_LIBCURL 1
> | /* end confdefs.h. */
> | #include
> | #include
> |
> | int
> | main ()
> | {
> | #if BYTE_ORDER != BIG_ENDIAN
> | not big endian
> | #endif
> |
> | ;
> | return 0;
> | }
> configure:8614: result: no
> configure:8675: checking for Motif headers
> configure:8681: gcc -E -I/sw/include -I/opt/local/include
> -I/usr/local/include -I/opt/local/include conftest.c
> co
Re: [Xastir] OSX 10.15.7 Macports: configure: error: **** MOTIF LIBRARIES NOT FOUND ****
On Sun, Jan 31, 2021 at 10:07 AM Tom Russo wrote: > > Look in config.log and see what the actual failure is. ... > Look in config.log and try to find the spot where it actually claims it can't > find libXm.a, and the error message from the linker should help to explain > why it doesn't work. But the solution to whatever that problem may be might > not be obvious at first. That last sentence is a major understatement, but give it a shot. If you can't figure it out: Find the snippet from "config.log" around where it can't find the Motif libraries (including above and below that part) and send it to this list. We should be able to help. -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
[Xastir] Fwd: Ridge radar
This came in to the mailman-owner address. Forwarding to the list. -- Forwarded message - From: Udo VISINTINI Date: Fri, Jan 1, 2021 at 7:04 PM Subject: Ridge radar To: Is there any updates, or information to get radar maps, again after the ridge radar URL doesn't work anymore Uwf Vis -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
[Xastir] Fwd: [Special] [aprsfirenet] [Announcement] Firenet Server Uptime Issues
-- Forwarded message - From: Eric H. Christensen via groups.io Date: Sat, Nov 7, 2020 at 4:55 PM Subject: [Special] [aprsfirenet] [Announcement] Firenet Server Uptime Issues To: Greetings fellow APRSers, There have been several questions around the recent (and not so recent) uptime issues with the Firenet APRS servers. Here is what I know right now: Firenet has four servers: N5JXS-F1 has been down for a while. The systems administrator for this box is extremely busy with a bunch of other tasks at the moment so... WG3K-CA is almost behaving itself but goes down on occasion for memory issues. WG3K-NJ just won't stay up and I'm planning to move it back to its own box soon. WE7U-IE just works. Each of these servers can handle ~50 connections. With three servers we usually don't have a problem. When one decides to go on vacation, we usually have a problem. This can affect the dissemination of our objects and data as well. So, I say all this to say... I'm working on it. Curt's box just works. Mine, for some reason, likes to fall over more than it should. Stay tuned for more information. 73, Eric WG3K -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#41): https://groups.io/g/aprsfirenet/message/41 Mute This Topic: https://groups.io/mt/78106468/145615 Group Owner: aprsfirenet+ow...@groups.io Unsubscribe: https://groups.io/g/aprsfirenet/leave/2516005/1904980795/xyzzy [curt.w...@gmail.com] -=-=-=-=-=-=-=-=-=-=-=- -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] APRS position not showing on map
Nope, not "Compressed" format, but Mic-E. On Thu, Sep 3, 2020 at 10:23 AM Curt Mills wrote: > > For packet: > > SV1GE-9>SWPU25,J48VAE*,WIDE1,WIDE2-2,:`5a)l 4Y/ > > There's a comma prior to the colon in the header. Could that be a > digipeater field with non-ASCII characters or non-printable > characters? > > There shouldn't be a comma right before the colon character. > > I haven't compared the rest of the characters (the payload) against > the APRS spec yet. I might get time to do that later today. The type > of packet would be '`' while the position would be "5a)l 4Y/" (there's > a space in there making it 8 chars). Probably a "Compressed" packet > per the spec? > > On Sat, Aug 29, 2020 at 9:27 AM Apostolos Kefalas wrote: > > > > Hi all, > > > > can anyone help? Why the beacon below is not showing on XASTIR map? > > > > > > SV1GE-9>SWPU25,J48VAE*,WIDE1,WIDE2-2,:`5a)l 4Y/ > > > > > > I think there might be a parsing error. > > > > > > Thanks > > > > 73 de SV1LJJ > > > > > > > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > > -- > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] APRS position not showing on map
For packet: SV1GE-9>SWPU25,J48VAE*,WIDE1,WIDE2-2,:`5a)l 4Y/ There's a comma prior to the colon in the header. Could that be a digipeater field with non-ASCII characters or non-printable characters? There shouldn't be a comma right before the colon character. I haven't compared the rest of the characters (the payload) against the APRS spec yet. I might get time to do that later today. The type of packet would be '`' while the position would be "5a)l 4Y/" (there's a space in there making it 8 chars). Probably a "Compressed" packet per the spec? On Sat, Aug 29, 2020 at 9:27 AM Apostolos Kefalas wrote: > > Hi all, > > can anyone help? Why the beacon below is not showing on XASTIR map? > > > SV1GE-9>SWPU25,J48VAE*,WIDE1,WIDE2-2,:`5a)l 4Y/ > > > I think there might be a parsing error. > > > Thanks > > 73 de SV1LJJ > > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] script to update FCC database
Roger. Thanks Tom. To the other Tom: Try deleting that file from the scripts directory and checking the file out again from Git, then a make clean;make;make install to see if that fixes it on the errant system. On Thu, Sep 3, 2020 at 9:48 AM Tom Russo wrote: > > There is nothing int he configure script that would add a line to output > the base directory and exit this way. All that configure does is scribble > the prefix into the script. > > On Thu, Sep 03, 2020 at 09:47:14AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > The final script is generated using an input of the > > scripts/getfcc-rac.pl.in file using the autoconf files. There must be > > a difference in how the file is processed on the two systems to come > > up with the final script. Tom Russo probably has more insight into > > this. > > > > On Thu, Sep 3, 2020 at 9:40 AM Tom Henderson wrote: > > > > > > I have two xastir installs, one on unbuntu, the other on raspian. > > > > > > Both were updated today using the update.xastir script. > > > > > > Both are running 2.1.7 > > > > > > On Ubuntu, the FCC script runs. It gets an error, but I think that's > > > probably an FCC problem. > > > > > > On Raspian, it prints the base directory and exits. > > > > > > As it turn out, the script on the Raspian install has an exit statement > > > added right after the base directory is printed, and the Ubuntu install > > > does not have that line added. > > > > > > Any idea how this could be? > > > > > > -- > > > Tom Henderson > > > > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] script to update FCC database
The final script is generated using an input of the scripts/getfcc-rac.pl.in file using the autoconf files. There must be a difference in how the file is processed on the two systems to come up with the final script. Tom Russo probably has more insight into this. On Thu, Sep 3, 2020 at 9:40 AM Tom Henderson wrote: > > I have two xastir installs, one on unbuntu, the other on raspian. > > Both were updated today using the update.xastir script. > > Both are running 2.1.7 > > On Ubuntu, the FCC script runs. It gets an error, but I think that's > probably an FCC problem. > > On Raspian, it prints the base directory and exits. > > As it turn out, the script on the Raspian install has an exit statement > added right after the base directory is printed, and the Ubuntu install > does not have that line added. > > Any idea how this could be? > > -- > Tom Henderson > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] re the problem that I asked about earlier
I'd also recommend setting aside the current ~/.xastir directory and letting the latest Xastir recreate a new one from scratch. Something like: Xastir: File->Exit cd mv .xastir .xastir.old Start up Xastir If there are things you want to snag out of the old Xastir config files you'll have the old version there to refer to. Any time you switch between a pre-packaged version of Xastir and a compiled version of Xastir, in either direction, you should perform the above steps. The programs and files get installed in different places, and the above assures the config files point to the correct files. On Tue, Jun 2, 2020 at 10:04 AM Tom Russo wrote: > > On Tue, Jun 02, 2020 at 02:55:11PM +0930, we recorded a bogon-computron > collision of the flavor, containing: > > On 2/6/20 10:02 am, Tom Russo wrote: > > > > I forgot to mention that I had removed every instance of "local" from my > > .xastir.cnf file. Doing so allowed xastir to start but on reboot xastir > > rebuilt the .xastir.cnf file to again include /usr/local/share/xastir. > > > > So, as I said in my first posting, I think that I have remnants of the > > build-from-source code on my system but I cannot locate them. > > This is definitely a sign of a messed up install. > > The package installed version should be creating an xastir.cnf with the > appropriate paths for its install, that is, /usr/share. This is a sign > that you're not in fact running that build. > > Please type the following in a shell window: >type -a xastir > > There should only be one, and it should be in /usr/bin, where the Ubuntu > package would install it. If there are more than one, then type: > which xastir > > to figure out which of the two is actually first in your path. > > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] re the problem that I asked about earlier
Also: How are you shutting down Xastir? Are you doing it through the menus or just killing it with the window controls? Somehow Xastir appears to be dying in a poor manner, which leaves processes running since it's a multi-threaded -and- multiprocessing application. On Mon, Jun 1, 2020 at 8:35 AM Jason Godfrey wrote: > > Can you run "lsof -i :2023" as root and see if anything is using those > ports? This will look at the spider side of things. > > I'm not familiar with the festival side of things, so I won't be much > help there. > - Jason > > On Mon, Jun 1, 2020 at 1:08 AM Phil wrote: > > > > telnet localhost 1314 results in "connection refused" > > > > /etc/hosts had a line that read "127.0.0.1 localhost" I added > > "localhost.localdomain" to that line. > > > > Running xastir after the addition results in the error messages: > > > > x_spider: Can't bind local address for AF 2: 98 - Address already in use > > Either this OS maps IPv4 addresses to IPv6 and this may be expected or > > could some processes still be running from a previous run of Xastir? > > x_spider: Can't bind local address for AF 10: 98 - Address already in use > > Either this OS maps IPv4 addresses to IPv6 and this may be expected or > > could some processes still be running from a previous run of Xastir? > > x_spider: Couldn't open any sockets > > Unable to setup any x_spider server sockets. > > festival_client: connect to server failed > > x_spider: Can't bind local address for AF 2: 98 - Address already in use > > Either this OS maps IPv4 addresses to IPv6 and this may be expected or > > could some processes still be running from a previous run of Xastir? > > x_spider: Can't bind local address for AF 10: 98 - Address already in use > > Either this OS maps IPv4 addresses to IPv6 and this may be expected or > > could some processes still be running from a previous run of Xastir? > > x_spider: Couldn't open any sockets > > Unable to setup any x_spider UDP server sockets. > > Could some processes still be running from a previous run of Xastir? > > UDP_Server process died. > > SayText: Couldn't open socket to Festival > > XReadBitmapFile() failed: Bitmap not found? > > /usr/local/share/xastir/symbols/2x2.xbm > > > > Which is where I was a day or two ago. The suggestion to kill running > > processes now has no effect. I have now removed the addition that I > > added to /etc/hosts. > > > > Any ideas? Surely I can't be the only one to have installed Xastir from > > the 20.04 Ubuntu repository and run into problems. > > > > -- > > > > Regards, > > Phil > > > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > > -- > "The problem with quotes on the Internet is that it is often difficult > to verify their authenticity." - Abraham Lincoln > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] No more problems
If you're talking about stations coming in from the internet, the internet servers are going to wait until you transmit your location so they know what stations around you to send. At least that's what my connection does because I have a range filter set up on the internet feed. You can speed that up by doing the "transmit now" bit from the menus. On Sat, May 30, 2020 at 1:34 AM Phil wrote: > > I thought I had a problem but all of a sudden stations are now displayed > on the map. Perhaps I didn't wait long enough. Anyway, I have made notes > so I shouldn't have to ask any more basic questions. > > -- > > Regards, > Phil > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Using Xastir online
I went hunting just now and found his callsign in a March 4th message. I don't run my email in threaded mode (on purpose) so takes me a bit longer to look back... Have to do searches instead. On Fri, May 29, 2020 at 10:21 AM Kirby wrote: > > On 29/05/2020 17:20, Curt Mills wrote: > > BTW: The usual protocol is to ask to see their callsign first before > > explaining how to go about it: A minor effort to help prevent non-hams > > from using the APRS-IS system. There were a couple of requests for the > > callsign but I hadn't seen one produced yet. > > Excellent point taken! > > -- > > > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Using Xastir online
BTW: The usual protocol is to ask to see their callsign first before explaining how to go about it: A minor effort to help prevent non-hams from using the APRS-IS system. There were a couple of requests for the callsign but I hadn't seen one produced yet. On Fri, May 29, 2020 at 10:16 AM Kirby wrote: > > On 29/05/2020 16:54, Brett Friermood wrote: > > I'm not sure of the exact algorithm at the moment, but the callpass length > > is some function of the callsign length and not always 5 digits. For > > instance my callpass is only 3 digits based off my 2x1 callsign. > > It breaks your call up into 16-bit and XORs them with a seed. Depending > on your call, I guess it could have any number from 0 to 32767. > > -- > > > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Using Xastir online
What's your callsign? I didn't see it in your email and didn't hunt down the rest of the thread. I can help. On Fri, May 29, 2020 at 4:55 AM Phil wrote: > > On 4/3/20 6:53 pm, Liz wrote: > > You haven't given a callsign, and you need a callsign to get data out > > of aunz.aprs2.net. > > Thank you Liz, > > I had this working the day you answered but due to a fresh installation > of Kubuntu I've had to start afresh. Now stations aren't being displayed > on the map. I cannot remember if I needed a pass-code or not, you > mentioned that I need a call sign to get data from aunz.aprs2.net. I > tried my call sign in the pass-code box but that's not the answer. Only > my call sign is listed under "all stations" and nothing else. > > This is frustrating me beyond belief, do I need a pass-code or is > whatever I'm missing less obvious? > > -- > > Regards, > Phil > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Xastir's iGate log?
All logging functions are in the "File" menu. On Wed, May 13, 2020 at 12:12 PM F1MHV wrote: > > Hi Tom, > > Does there is log of what is specifically igated RF->INET et INET->RF by > Xastir? > > 73 de Cyril - DF1CHB/AM - F1MHV/M > > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] locally stored OSM map file
Just a minor point: The list of map types supported is only displayed if you start Xastir from an xterm or similar. If you start it from the GUI you won't see that list. On Tue, Apr 21, 2020 at 9:41 AM Tom Russo wrote: > > You'll have to convert it to a file format that Xastir understands. We can't > read XML map files. The list of vector formats we actually support is > displayed at the time you start up Xastir. > > It is possible you could convert it to shapefile format using the "ogr2ogr" > tool of the GDAL suite, if the XML file describes a vector map. > > Once you've converted to shapefile format, you will almost certainly need to > create a dbfawk file to go with it. dbfawk files tell Xastir how to render > the lines it finds in the shapefile --- without one, they all show up as > unlabeled black lines, which is fairly useless. > > You may be better off trying to locate OSM maps that have already been > converted to shapefile. There may even be a dbfawk file in Xastir's > config directory that is suitable for rendering those. > > Sorry there is no quick and dirty answer to your question. Using off-line > maps is a great thing, and Xastir is quite capable in that regard, but > setting them up can be a chore. > > On Tue, Apr 21, 2020 at 05:41:58PM +0200, we recorded a bogon-computron > collision of the flavor, containing: > > Hi ! > > > > I have a locally stored map file. Using "file -k this-local-file" gives me > > "OpenStreetMap XML data\012- XML 1.0 document text\012- XML document, UTF-8 > > Unicode text\012-". According to osmium, it was generated by CGImap 0.1.0. > > > > How can I use this file with Xastir ? > > > > Thanks ! > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Update frequency for FCC and NWS?
I update the FCC/RAC databases maybe once or twice a year. I probably update the NWS Shapefiles more often than most 'cuz I need to make sure they haven't changed at NWS, but if so, update the Xastir script. So 4 to 6 times a year for that. Nobody probably needs to actually update them that often. Probably once or twice a year for that script would be fine too. On Sat, Apr 18, 2020 at 2:43 PM Tom Henderson wrote: > > Just curious how often most of you update the FCC database and NWS shape > files? > > -- > Tom Henderson > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] FCC database download
I updated scripts/get-NWSdata.in in my Github/Xastir repo. Don't recall whether I need to go update my repo first before I do a pull request. Might be easier / faster if you snag that one-line change out of that repo and apply it directly. I tested the resulting script and it works fine. On Fri, Apr 17, 2020 at 3:00 PM km5vy Tom Russo wrote: > > On Fri, Apr 17, 2020 at 02:58:47PM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > I should run through the wx alert files real quick too. > > Please do. I was in the middle of doing the point release right now, so > I'll stop and start over if you find an update is needed. > > > On Fri, Apr 17, 2020 at 2:58 PM Tom Russo wrote: > > > > > > FWIW, I went to "fix" the script today so that the fixed version would be > > > in the 2.1.6 point release, only to find that the URL we have been using > > > all along is working again. So no fix needed. Problem was on their end. > > > > > > On Sun, Mar 29, 2020 at 11:32:27AM -0400, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > Tom and Hal, thanks for the info. I'll wait a few days/weeks and try > > > > again. THANKS! > > > > > > > > Glenn WB4UGH > > > > ___ > > > > Xastir mailing list > > > > Xastir@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > -- > > > Tom RussoKM5VY > > > Tijeras, NM > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir-dev] [Xastir] Fwd: Bug#957970: xastir: ftbfs with GCC-10
Yes please. On Fri, Apr 17, 2020 at 9:16 AM km5vy Tom Russo wrote: > > On Fri, Apr 17, 2020 at 08:54:30AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > Sure. > > I can do that tonight if we're all in accord. It's a fairly lightweight > process anymore to push out a release on github. > > > On Fri, Apr 17, 2020 at 8:33 AM Tom Russo wrote: > > > > > > On Fri, Apr 17, 2020 at 08:31:34AM -0700, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > > > > > Ah.. ok. Seems like a good first step would be to tag a new Xastir > > > > release > > > > and tell the Debian maintainer to start with that. > > > > > > Yes, a point release seems in order. > > > > > > > On 04/17/2020 08:27 AM, Tom Russo wrote: > > > > > On Fri, Apr 17, 2020 at 07:14:19AM -0700, we recorded a > > > > > bogon-computron collision of the flavor, > > > > > containing: > > > > > > Just saw this notification on the Xastir list. Seems like GCC-10 is > > > > > > going to > > > > > > require a lot of different Linux programs to do some clean ups. > > > > > It apppears they are trying to build release code, not the git head. > > > > > Some > > > > > of this stuff is already fixed as a result of a github issue that was > > > > > opened > > > > > back in Feb: https://github.com/Xastir/Xastir/issues/164. > > > > > > > > > > See commit 9d0d1d9, which fixed those multiply defined variables > > > > > (which > > > > > are all the result of "-fno-common" being made the default in gcc10. > > > > > > > > > > The snprintf stuff is a perenial issue, and we've been picking away > > > > > at it. > > > > > There's a lot of messy use of snprintf. But I believe this is just a > > > > > warning. > > > > > > > > > > > Forwarded Message > > > > > > Subject: Bug#957970: xastir: ftbfs with GCC-10 > > > > > > Resent-Date: Fri, 17 Apr 2020 11:38:07 + > > > > > > Resent-From: Matthias Klose > > > > > > Resent-To:Debian Hamradio Maintainers > > > > > > > > > > > > Date: Fri, 17 Apr 2020 11:13:49 + > > > > > > From: Matthias Klose > > > > > > Reply-To: Matthias Klose , > > > > > > 957970-mainto...@bugs.debian.org > > > > > > To: mainto...@bugs.debian.org > > > > > > > > > > > > > > > > > > > > > > > > Package: src:xastir > > > > > > Version: 2.1.4+git20191127.bb66a77-3 > > > > > > Severity: normal > > > > > > Tags: sid bullseye > > > > > > User: debian-...@lists.debian.org > > > > > > Usertags: ftbfs-gcc-10 > > > > > > > > > > > > Please keep this issue open in the bug tracker for the package it > > > > > > was filed for. If a fix in another package is required, please > > > > > > file a bug for the other package (or clone), and add a block in this > > > > > > package. Please keep the issue open until the package can be built > > > > > > in > > > > > > a follow-up test rebuild. > > > > > > > > > > > > The package fails to build in a test rebuild on at least amd64 with > > > > > > gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The > > > > > > severity of this report will be raised before the bullseye release, > > > > > > so nothing has to be done for the buster release. > > > > > > > > > > > > The full build log can be found at: > > > > > > http://people.debian.org/~doko/logs/gcc10-20200225/xastir_2.1.4+git20191127.bb66a77-3_unstable_gcc10.log > > > > > > The last lines of the build log are at the end of this report. > > > > > > > > > > > > To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, > > > > > > or install the gcc, g++, gfortran, ... packages from experimental. > > > > > > > > > > > >apt-get -t=experimental install g++ > > > > > > > > > > > > Common build failures are new warnings resulting in build failures > > > > > > with > > > > > > -Werror turned on, or new/dropped symbols in Debian symbols files. > > > > > > For other C/C++ related build failures see the porting guide at > > > > > > http://gcc.gnu.org/gcc-10/porting_to.html > > > > > > > > > > > > [...] > > > > > > 3379 | "%s", > > > > > >|^~ > > > > > > In file included from /usr/include/stdio.h:867, > > > > > > from snprintf.h:27, > > > > > > from objects.c:29: > > > > > > /usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: > > > > > > ???__builtin_snprintf??? output between 1 and 1993 bytes into a > > > > > > destination of size 40 > > > > > > 67 | return __builtin___snprintf_chk (__s, __n, > > > > > > __USE_FORTIFY_LEVEL - 1, > > > > > >| > > > > > > ^~~~ > > > > > > 68 |__bos (__s), __fmt, __va_arg_pack ()); > > > > > >|~ > > > > > > gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/GraphicsMagick > > > > > > -I/usr/local/include -I/usr/include/geotiff -Wdate-time > > > > > >
Re: [Xastir] Fwd: Bug#957970: xastir: ftbfs with GCC-10
GCC: Forcing coders to write better code since 1987. On Fri, Apr 17, 2020 at 7:14 AM David Ranch wrote: > > > Just saw this notification on the Xastir list. Seems like GCC-10 is > going to require a lot of different Linux programs to do some clean ups. > > --David > KI6ZHD > > > Forwarded Message > Subject:Bug#957970: xastir: ftbfs with GCC-10 > Resent-Date:Fri, 17 Apr 2020 11:38:07 + > Resent-From:Matthias Klose > Resent-To: Debian Hamradio Maintainers > Date: Fri, 17 Apr 2020 11:13:49 + > From: Matthias Klose > Reply-To: Matthias Klose , > 957970-mainto...@bugs.debian.org > To: mainto...@bugs.debian.org > > > > Package: src:xastir > Version: 2.1.4+git20191127.bb66a77-3 > Severity: normal > Tags: sid bullseye > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-10 > > Please keep this issue open in the bug tracker for the package it > was filed for. If a fix in another package is required, please > file a bug for the other package (or clone), and add a block in this > package. Please keep the issue open until the package can be built in > a follow-up test rebuild. > > The package fails to build in a test rebuild on at least amd64 with > gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The > severity of this report will be raised before the bullseye release, > so nothing has to be done for the buster release. > > The full build log can be found at: > http://people.debian.org/~doko/logs/gcc10-20200225/xastir_2.1.4+git20191127.bb66a77-3_unstable_gcc10.log > The last lines of the build log are at the end of this report. > > To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, > or install the gcc, g++, gfortran, ... packages from experimental. > >apt-get -t=experimental install g++ > > Common build failures are new warnings resulting in build failures with > -Werror turned on, or new/dropped symbols in Debian symbols files. > For other C/C++ related build failures see the porting guide at > http://gcc.gnu.org/gcc-10/porting_to.html > > [...] > 3379 | "%s", >|^~ > In file included from /usr/include/stdio.h:867, > from snprintf.h:27, > from objects.c:29: > /usr/include/x86_64-linux-gnu/bits/stdio2.h:67:10: note: ‘__builtin_snprintf’ > output between 1 and 1993 bytes into a destination of size 40 > 67 | return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1, >| ^~~~ > 68 |__bos (__s), __fmt, __va_arg_pack ()); >|~ > gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/GraphicsMagick > -I/usr/local/include -I/usr/include/geotiff -Wdate-time -D_FORTIFY_SOURCE=2 > -DXASTIR_DATA_BASE=\"/usr/share/xastir\" -fopenmp -g -O2 > -fdebug-prefix-map=/build/graphicsmagick-wInnp7/graphicsmagick-1.4+really1.3.35=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread > -fdebug-prefix-map=/<>=. -pipe -Wpointer-arith > -Wstrict-prototypes -Wno-unused-parameter -c -o sound.o sound.c > gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/GraphicsMagick > -I/usr/local/include -I/usr/include/geotiff -Wdate-time -D_FORTIFY_SOURCE=2 > -DXASTIR_DATA_BASE=\"/usr/share/xastir\" -fopenmp -g -O2 > -fdebug-prefix-map=/build/graphicsmagick-wInnp7/graphicsmagick-1.4+really1.3.35=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread > -fdebug-prefix-map=/<>=. -pipe -Wpointer-arith > -Wstrict-prototypes -Wno-unused-parameter -c -o tile_mgmnt.o tile_mgmnt.c > gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/GraphicsMagick > -I/usr/local/include -I/usr/include/geotiff -Wdate-time -D_FORTIFY_SOURCE=2 > -DXASTIR_DATA_BASE=\"/usr/share/xastir\" -fopenmp -g -O2 > -fdebug-prefix-map=/build/graphicsmagick-wInnp7/graphicsmagick-1.4+really1.3.35=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread > -fdebug-prefix-map=/<>=. -pipe -Wpointer-arith > -Wstrict-prototypes -Wno-unused-parameter -c -o track_gui.o track_gui.c > gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/GraphicsMagick > -I/usr/local/include -I/usr/include/geotiff -Wdate-time -D_FORTIFY_SOURCE=2 > -DXASTIR_DATA_BASE=\"/usr/share/xastir\" -fopenmp -g -O2 > -fdebug-prefix-map=/build/graphicsmagick-wInnp7/graphicsmagick-1.4+really1.3.35=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread > -fdebug-prefix-map=/<>=. -pipe -Wpointer-arith > -Wstrict-prototypes -Wno-unused-parameter -c -o util.o util.c > gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/GraphicsMagick > -I/usr/local/include -I/usr/include/geotiff -Wdate-time -D_FORTIFY_SOURCE=2 > -DXASTIR_DATA_BASE=\"/usr/share/xastir\" -fopenmp -g -O2 > -fdebug-prefix-map=/build/graphicsmagick-wInnp7/graphicsmagick-1.4+really1.3.35=. > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pthread
Re: [Xastir] My question related to MAPS_AUTO_MAPS in xastir.cnf
I should have said "if the first map is raster and that's the only raster map loaded". Can load vector maps after that on top of raster with good effect. For those with email that stacks new messages on top of old so you miss things, read my previous message. On Wed, Apr 15, 2020 at 7:35 AM Curt Mills wrote: > > Actually a better way of describing it is that it works quite well, > but is very simplistic. You have to be a bit of a map expert to know > how to use it properly. For most people it's not useful and only > causes problems. Maybe 1 or 2% of users do use it and don't want the > feature to disappear so we haven't removed it (yet). I'd entertain the > idea of removing it or making it more difficult to select. Maybe > having it default to "OFF" on every startup would be a reasonable > compromise. > > If you have it on and don't know how to use it, turn it off now. More > than likely it's causing long map-load times as Xastir looks through > every one of your possible maps and loads every one that fits your > current map screen one-by-one, stacking each one on top of the last. > Works great for all vector maps or if the first map loaded is raster, > otherwise it is one big mess. > > On Wed, Apr 15, 2020 at 6:07 AM Tom Russo wrote: > > > > > > "Auto maps" is a thing in Xastir that few people use anymore. It was a way > > of "automatically" choosing when to display them that was ultimately > > superceded by the layer and min/max zoom levels options in the map chooser > > properties. It still exists and can still be used, and is turned on using > > the > > "Enable auto maps" option in the Map menu. > > > > As I recall, "Auto Maps" never worked very well, which is why most people > > went to the more configurable method. I do recall that someone on the > > list had some trick where he used both auto maps and the manually configured > > layer and min/max zoom to acheive some specific use case but I can't for > > the life of me remember what that was. > > > > I haven't turned auto maps on in at least 16 years. > > > > On Wed, Apr 15, 2020 at 01:48:51PM +0200, we recorded a bogon-computron > > collision of the flavor, containing: > > > Hi all, > > > > > > What is the meaning of the MAPS_AUTO_MAPS line in the config/xastir.cnf > > > file > > > ? Which are the possibles values ? How is this field set ? > > > > > > Many thanks ! > > > > > > Best wishes, > > > Claude (DJ0OT) > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > -- > > Tom RussoKM5VY > > Tijeras, NM > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > [n-z][a-m] > > > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > > -- > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] My question related to MAPS_AUTO_MAPS in xastir.cnf
Actually a better way of describing it is that it works quite well, but is very simplistic. You have to be a bit of a map expert to know how to use it properly. For most people it's not useful and only causes problems. Maybe 1 or 2% of users do use it and don't want the feature to disappear so we haven't removed it (yet). I'd entertain the idea of removing it or making it more difficult to select. Maybe having it default to "OFF" on every startup would be a reasonable compromise. If you have it on and don't know how to use it, turn it off now. More than likely it's causing long map-load times as Xastir looks through every one of your possible maps and loads every one that fits your current map screen one-by-one, stacking each one on top of the last. Works great for all vector maps or if the first map loaded is raster, otherwise it is one big mess. On Wed, Apr 15, 2020 at 6:07 AM Tom Russo wrote: > > > "Auto maps" is a thing in Xastir that few people use anymore. It was a way > of "automatically" choosing when to display them that was ultimately > superceded by the layer and min/max zoom levels options in the map chooser > properties. It still exists and can still be used, and is turned on using the > "Enable auto maps" option in the Map menu. > > As I recall, "Auto Maps" never worked very well, which is why most people > went to the more configurable method. I do recall that someone on the > list had some trick where he used both auto maps and the manually configured > layer and min/max zoom to acheive some specific use case but I can't for > the life of me remember what that was. > > I haven't turned auto maps on in at least 16 years. > > On Wed, Apr 15, 2020 at 01:48:51PM +0200, we recorded a bogon-computron > collision of the flavor, containing: > > Hi all, > > > > What is the meaning of the MAPS_AUTO_MAPS line in the config/xastir.cnf file > > ? Which are the possibles values ? How is this field set ? > > > > Many thanks ! > > > > Best wishes, > > Claude (DJ0OT) > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Data Logging
Is it possible you have an INET interface configured and they're coming in to Xastir that way? On Mon, Apr 13, 2020 at 6:52 PM Tom Russo wrote: > > On Mon, Apr 13, 2020 at 06:49:37PM -0600, we recorded a bogon-computron > collision of the flavor, containing: > > On Mon, Apr 13, 2020 at 07:45:01PM -0500, we recorded a bogon-computron > > collision of the flavor, containing: > > > I am using a DRAWS on a Pi. > > > > > > I am seeing mobile stations move but I am not seeing the data in the > > > View > Incoming Data > TNC Data Only screen. > > > > Is your DRAWS board configured as an AX.25 kernel interface or a serial > > TNC? > > > > If the former, you need to enable the "Net" data view, as the TNC is > > considered a network interface. > > Sorry, this is not correct. You should be getting the data in Incoming Data > no matter how the TNC is configured with "TNC Data only" checked. > > Sorry for the misleading statement. > > If your Xastir station is showing stations and the TNC is your only input, > I have no idea why the data should not be showing up under the incoming > data window. > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] DBFAWK - Doin' it wrong?
Start Xastir from a terminal window. It'll show up in that window. On Sun, Mar 29, 2020 at 7:55 AM Chip Griffin wrote: > > What would this do for me? Where would I go to read the extra info? I’m > assuming this would go in a logfile somewhere. > > > On Mar 24, 2020, at 12:13, Curt Mills wrote: > > > > One could also turn on debug level 16. Might be of use in this case. > > > > -- > > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > > -- > Chip > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] DBFAWK - Doin' it wrong?
Agreed on the more complexity of adding filenames into the testdbfawk.c code. I looked at that too and decided not to look any further. It could be done though. Sounds like we have a reasonable debugging path for the problem as-is. On Tue, Mar 24, 2020 at 9:53 AM km5vy Tom Russo wrote: > > On Tue, Mar 24, 2020 at 09:48:27AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > Ah, cool. > > > > One might also have to search through the map directories if you have > > per-file dbfawks for some maps (I do). > > Yes, of course. But that's just a matter of adding additional directory > names to the same grep command. > > But if you have a per-file dbfawk for the specified file, you already know > what file is being used --- you specified it. The question before the > committee is "what file other than the one I intended might be getting used > instead?" > > > On Tue, Mar 24, 2020 at 9:45 AM km5vy Tom Russo wrote: > > > > > > On Tue, Mar 24, 2020 at 09:41:49AM -0700, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > Yea, try it... I didn't see any filenames listed in the output. > > > > > > I didn't say there would be. But there will be a dbf signature shown, and > > > you use grep to find all the files in the config directory that have that > > > signature. For example: > > > > > > 8 Columns, 3334 Records in file > > > sig: STATE:CWA:COUNTYNAME:FIPS:TIME_ZONE:FE_AREA:LON:LAT > > > DBF Signatures match! > > > > > > > > > One then does: > > > > > > grep -l 'dbfinfo="STATE:CWA:COUNTYNAME:FIPS:TIME_ZONE:FE_AREA:LON:LAT"' > > > /usr/local/share/xastir/config/* > > > > > > to get the list of file names that contain that signature. > > > > > > > On Tue, Mar 24, 2020 at 9:34 AM km5vy Tom Russo > > > > wrote: > > > > > > > > > > On Tue, Mar 24, 2020 at 09:32:02AM -0700, we recorded a > > > > > bogon-computron collision of the flavor, > > > > > containing: > > > > > > On Tue, Mar 24, 2020 at 9:13 AM Curt Mills > > > > > > wrote: > > > > > > > > > > > > > > One could also turn on debug level 16. Might be of use in this > > > > > > > case. > > > > > > > > > > > > Could also mess around with testdbfawk, although now that I think > > > > > > about it we should think about modifying testdbfawk.c to print out > > > > > > the > > > > > > name of the dbfawk file that matched the dbf file. Could be quite > > > > > > useful in this case. > > > > > > > > > > > > cd /usr/local/share/xastir; testdbfawk -D config -d > > > > > > Counties/mz02ap19.dbf 2>&1 | head -10 > > > > > > > > > > One could. Or one could just run the command above and use "grep" to > > > > > find > > > > > all the files that have the same dbfinfo line. > > > > > > > > > > -- > > > > > Tom RussoKM5VY > > > > > Tijeras, NM > > > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > > > [n-z][a-m] > > > > > > > > > > > > > > > > > -- > > > > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com > > > > > > -- > > > Tom RussoKM5VY > > > Tijeras, NM > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > > > > > > -- > > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] DBFAWK - Doin' it wrong?
Ah, cool. One might also have to search through the map directories if you have per-file dbfawks for some maps (I do). On Tue, Mar 24, 2020 at 9:45 AM km5vy Tom Russo wrote: > > On Tue, Mar 24, 2020 at 09:41:49AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > Yea, try it... I didn't see any filenames listed in the output. > > I didn't say there would be. But there will be a dbf signature shown, and > you use grep to find all the files in the config directory that have that > signature. For example: > > 8 Columns, 3334 Records in file > sig: STATE:CWA:COUNTYNAME:FIPS:TIME_ZONE:FE_AREA:LON:LAT > DBF Signatures match! > > > One then does: > > grep -l 'dbfinfo="STATE:CWA:COUNTYNAME:FIPS:TIME_ZONE:FE_AREA:LON:LAT"' > /usr/local/share/xastir/config/* > > to get the list of file names that contain that signature. > > > On Tue, Mar 24, 2020 at 9:34 AM km5vy Tom Russo wrote: > > > > > > On Tue, Mar 24, 2020 at 09:32:02AM -0700, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > On Tue, Mar 24, 2020 at 9:13 AM Curt Mills wrote: > > > > > > > > > > One could also turn on debug level 16. Might be of use in this case. > > > > > > > > Could also mess around with testdbfawk, although now that I think > > > > about it we should think about modifying testdbfawk.c to print out the > > > > name of the dbfawk file that matched the dbf file. Could be quite > > > > useful in this case. > > > > > > > > cd /usr/local/share/xastir; testdbfawk -D config -d > > > > Counties/mz02ap19.dbf 2>&1 | head -10 > > > > > > One could. Or one could just run the command above and use "grep" to find > > > all the files that have the same dbfinfo line. > > > > > > -- > > > Tom RussoKM5VY > > > Tijeras, NM > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > > > > > > -- > > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] DBFAWK - Doin' it wrong?
Yea, try it... I didn't see any filenames listed in the output. On Tue, Mar 24, 2020 at 9:34 AM km5vy Tom Russo wrote: > > On Tue, Mar 24, 2020 at 09:32:02AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > On Tue, Mar 24, 2020 at 9:13 AM Curt Mills wrote: > > > > > > One could also turn on debug level 16. Might be of use in this case. > > > > Could also mess around with testdbfawk, although now that I think > > about it we should think about modifying testdbfawk.c to print out the > > name of the dbfawk file that matched the dbf file. Could be quite > > useful in this case. > > > > cd /usr/local/share/xastir; testdbfawk -D config -d > > Counties/mz02ap19.dbf 2>&1 | head -10 > > One could. Or one could just run the command above and use "grep" to find > all the files that have the same dbfinfo line. > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] DBFAWK - Doin' it wrong?
On Tue, Mar 24, 2020 at 9:13 AM Curt Mills wrote: > > One could also turn on debug level 16. Might be of use in this case. Could also mess around with testdbfawk, although now that I think about it we should think about modifying testdbfawk.c to print out the name of the dbfawk file that matched the dbf file. Could be quite useful in this case. cd /usr/local/share/xastir; testdbfawk -D config -d Counties/mz02ap19.dbf 2>&1 | head -10 -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] DBFAWK - Doin' it wrong?
One could also turn on debug level 16. Might be of use in this case. On Tue, Mar 24, 2020 at 8:37 AM Tom Russo wrote: > > On Tue, Mar 24, 2020 at 08:28:08AM -0500, we recorded a bogon-computron > collision of the flavor, containing: > > On Mon, Mar 23, 2020 at 7:28 PM Chip Griffin wrote: > > > > > the results of the DBFAWK are not equal. > > > > > > > Could there be an additional dbfawk on the system that is not behaving as > > expected? > > > > It's possible to hove more than one dbfawk that matches a particular file. > > I beat my head against the wall for a short time trying to figure out why > > my dbfawk wasn't working as expected when the reason was that another > > dbfawk (in my case one that came with xastir) was kicking in first. > > Oooh. Yeah, that's another way it could happen. > > > I do not recall the logic of how a dbfawk is selected when there are > > multiple files that match the dbf signature. > > If there is a per-file dbfawk that matches the file's name (e.g. if > you've got foo.dbf and foo.dbfawk exists, it is used). Otherwise, the first > one that matches the signature is used. > > However, the "first one that matches" is the first one in a linked list of > pre-scanned dbf signatures, which is constructed by repeatedly making > "readdir" calls on the config directory and scanning the files it finds. > That probably means that the file that comes first lexicographically. > > The surest way to check whether this is happening is to copy your dbfawk > to have the same name as the dbf file you want it to match, and put it in > the same directory as the dbf file. If the rendering changes, this is the > problem and then you have to find the other file in the config directory > that has the same dbfinfo line. > > Alternatively, rename your dbfawk file with "" as a prefix so it comes > first in the readdir loop. Either way, if the rendering changes, Jason's > issue is the one that's your problem. > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
[Xastir-dev] Travis OSX build broken
I'm scratching my head trying to figure out how my last checkin broke the Travis CI OSX build... I only touched stuff having to do with NWS shapefiles as far as I can tell. -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
Re: [Xastir] What is very large rectangle with X in center on station?
> I didn't see the original message come across the list, only Tom's response. Ah, two messages from Bill went into my spam folder. Turn off display of such rectangles here: Station -> Filter Display -> Display Position Ambiguity -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] What is very large rectangle with X in center on station?
I didn't see the original message come across the list, only Tom's response. You can turn off display of such rectangles here: Station -> Filter Display -> Display Position Ambiguity On Fri, Feb 21, 2020 at 8:08 AM Tom Russo wrote: > > It's a station transmitting with position ambiguity (truncated precision > position). The box represents the range of positions that the station could > be in given the limited amount of data it transmitted. > > > http://blog.aprs.fi/2011/01/position-ambiguity-support.html > > http://www.aprs.org/symbols.html > (APRSdos used circles for ambiguity) > > > On Fri, Feb 21, 2020 at 10:05:16AM -0600, we recorded a bogon-computron > collision of the flavor, containing: > > Hi, > > > > In the St. Louis, MO area I see from time to time on my Xastir map (rf only) > > a very large rectangle (more than 50 miles in North/South direction) with an > > X on the station AC0MW-7.?? The X goes from corner to corner of the > > rectangle.?? The X and the rectangle are made of dashes.?? I have been using > > APRS since APRSdos and continue to enjoy it.?? The current Xastir map is > > shown on my website, www.billbird.com.?? I've tried to discover the answer > > on my own but have not been able to. > > > > Thanks and 73, > > > > Bill Bird > > KG0YJ > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] USNG Support
Unfortunately you can't input coordinates directly in USNG. Alternatives: Place an object or item on the map where you want it, then read it out in USNG via the calculator or via the coordinate system at the bottom. In fact you can do the first method without finishing the actual placement of an object/item. On Thu, Jan 30, 2020 at 7:30 AM Brett Friermood wrote: > > Thanks, Curt. That jogs my memory now. > > I didn't look at the output of the calculator for it since I was focused on > inputting USNG. > > > On Thu, Jan 30, 2020 at 9:17 AM Curt Mills wrote: > > > There are two areas in Xastir that have USNG: > > > > One is under File->Configure->Coordinate System. > > > > The other is the Map->Coordinate Calculator. This can also be brought > > up from the Object/Item Create menu from right-clicking on the map. If > > you put a coordinate into the calculator in UTM or lat/long it will > > spit out 6 different coordinates including MGRS/USNG when you hit the > > "Calculate" button. If you originally brought it up from the "Create > > Object/Item" menu then the "OK" button will paste the coordinate into > > your object/item you're creating. > > > > I created an Android app that is similar to the Coordinate Calculator > > as well. Not open-source though. We use it in the local SAR. > > > > On Thu, Jan 30, 2020 at 6:45 AM Brett Friermood > > wrote: > > > > > > To what extent does Xastir support USNG coordinates? I am investigating a > > > relatively simple use case of marking a location on the map using a > > > object when given coordinates in USNG format. > > > > > > I recall seeing something more in depth before, however I'm currently > > > unable to find any mention of it on the internet, in the list archives, > > or > > > even in the little bit I've browsed the code. The only thing I am able to > > > find is a couple mentions of it being supported, however no additional > > > information. > > > > > > I have a work around by using an external converter and inputting via UTM > > > or Lat/Long, just curious if I am able to directly input via USNG. > > > > > > Thanks, > > > > > > Brett KQ9N > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] USNG Support
There are two areas in Xastir that have USNG: One is under File->Configure->Coordinate System. The other is the Map->Coordinate Calculator. This can also be brought up from the Object/Item Create menu from right-clicking on the map. If you put a coordinate into the calculator in UTM or lat/long it will spit out 6 different coordinates including MGRS/USNG when you hit the "Calculate" button. If you originally brought it up from the "Create Object/Item" menu then the "OK" button will paste the coordinate into your object/item you're creating. I created an Android app that is similar to the Coordinate Calculator as well. Not open-source though. We use it in the local SAR. On Thu, Jan 30, 2020 at 6:45 AM Brett Friermood wrote: > > To what extent does Xastir support USNG coordinates? I am investigating a > relatively simple use case of marking a location on the map using a > object when given coordinates in USNG format. > > I recall seeing something more in depth before, however I'm currently > unable to find any mention of it on the internet, in the list archives, or > even in the little bit I've browsed the code. The only thing I am able to > find is a couple mentions of it being supported, however no additional > information. > > I have a work around by using an external converter and inputting via UTM > or Lat/Long, just curious if I am able to directly input via USNG. > > Thanks, > > Brett KQ9N > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Xastir Digest, Vol 689, Issue 2
On Tue, Jan 7, 2020 at 12:04 PM Tom Russo wrote: > > There are way too many system-specific install notes for outdated systems on > the wiki, and it makes them impossible to keep up to date. Some of the > systems > are years old and some are many years past their end of life. > > We need to clear out the wiki of outdated cruft. Any help in that regard > would be appreciated. It great that folks contribute new build instructions > there, but we really need to clean them out when the systems they refer to > become obsolete. Most of these pages are just minor deltas off of each other, > with huge chunks of duplicated text that is a maintenance nightmare. I opened all of the Windows & Linux install pages last night and tweaked them. I didn't look at the OSX pages at all. GDAL should be gone from all, minus one or two pages that talked about installed GDAL separate from Xastir: I left those notes. I didn't clear out pages for obsolete OS'es. Maybe would be good to make an "archive" area and move old ones under that? -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Xastir Digest, Vol 690, Issue 1
Yea. Order of the packages for install shouldn't matter. On Wed, Jan 8, 2020 at 9:07 AM Jason KG4WSV wrote: > > On Wed, Jan 8, 2020 at 10:27 AM Dominick Spina wrote: > > > > I found if I tried to install multiple packages at the same time, as part > > of the same command, not all packages actually were installed, or failed to > > install. > > > > When I installed packages one at a time, running separate commands, they > > installed successfully. > > > The only reasons I have encountered / can think of for this would be: > > - bad package dependencies in the repo. This is _not_ the case for the > xastir dependencies. > > - low disk space, which means not enough room for all packages to download > before installing. I have experienced this on Pis and other SBCs. > > - interrupted network connection. > > > -Jason > kg4wsv > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Xastir Digest, Vol 689, Issue 2
Note that you don't need GDAL anymore. That support has been deprecated and was hardly used prior to that anyway. Timing: You can always do: time to time things easily. For instance "time ls" gives me: -- $ time ls blah blah blah real0m0.117s user0m0.008s sys 0m0.007s -- On Tue, Jan 7, 2020 at 8:53 AM Fred Erickson wrote: > > > I'm replying after Tom's message since it is the last in the thread but > this is just to let Dominick know that the instructions here: > http://xastir.org/index.php/HowTo:Ubuntu_14.04-17.04 work just fine > when followed exactly, step by step. > > Yesterday, after reading this thread, I followed the instructions on my > Acer Aspire 5734Z, which is several years old and was the cheapest > laptop Best Buy had at the time. Installed os is Linux Mint 19.3 > Tricia. No problems were encountered except building gdal took a very > long time. Wish I had started a timer or even tee'd it to a file. > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Xastir weather alerts
Thanks Tom!
On Sun, Dec 29, 2019, 11:35 AM Tom Russo wrote:
> On Sun, Dec 29, 2019 at 11:15:33AM -0700, we recorded a bogon-computron
> collision of the flavor, containing:
> > It looks like some of the work cleaning up compiler warnings resulted in
> > broken code to concatenate strings.
> >
> > I'm looking into it. It may take a while.
>
> Or not. Found the spot where things were being done wrong, and it was
> indeed
> the result of a broken cleanup of compiler warnings in the alerts code.
> The
> fix should be on github as of now.
>
> > On Sun, Dec 29, 2019 at 11:08:32AM -0700, we recorded a bogon-computron
> collision of the flavor, containing:
> > > In a recent message, Apostolos Kefalas asked:
> > >
> > > Hello all,
> > >
> > >
> > > I am on Xastir v2.1.3 (6884c6f9) and now I have noticed that the
> > > weather alert list (View -> Weather Alerts) is not showing all the
> > > data.
> > >
> > > I remember in older versions of Xastir we could see the type of alert,
> > > expiration time and area codes.
> > >
> > > Happy New Year to All
> > >
> > > Apostolos, SV1LJJ
> > >
> > >
> > >
> > > It looks suspiciously like something has changed in the data coming in
> related
> > > to weather alerts, and xastir is improperly parsing it.
> > >
> > > For example, a quick view of my net feed shows this packet coming in:
> > >
> > > UNRWSW>APRS,TCPIP,qAO,WE7U-WX::NWS-WARN
> :300100z,WINTER_WEATHER,SDZ14-31-32-41>44 {THj1D
> > >
> > > But all that shows up in the weather alerts box is:
> > >
> > > UNRWSW THj1D NWS-WARN z
> > >
> > > Somehow that incoming data is not properly being parsed anymore. Most
> of the
> > > alerts I find in my wx alerts dialog look like this, with a few extra
> > > adornments, like:
> > >
> > > ABRWSW T3Y4B NWS-WARN 03 @z
> > >
> > > Very, very few have full data, but some do:
> > > SGFFLS 10020 NWS_ADVIS 01 @z ==> 03 @0224z NI MO_C185 FLOOD
> > >
> > > Whether this is a change in the incoming data formatting or something
> broken
> > > in Xastir's code is another question. Looks like we need a deep dive
> into
> > > the alert parsing code to see if there are changes necessary. The
> alert code
> > > has not had meaningful changes in a very long time. There was some
> effort
> > > to eliminate compiler warnings in 2017 and again earlier this year,
> but those
> > > should not have changed functionality.
> > >
> > > However, Xastir does have an NWS-TEST.log file that we're supposed to
> be
> > > able to read in and get alerts, and when I read it in it shows up as
> garbled
> > > alerts just like the new ones have.
> > >
> > > Interestingly enough, though, when I read in NWS-TEST.log the alerts
> do show
> > > up on the map. The data is just missing in the alert dialog box.
> > >
> > > So it looks like something got mangled in the code where data is
> parsed out
> > > for display in the dialog, but there is enough information getting
> decoded to
> > > display it on the map.
> > >
> > >
> > > --
> > > Tom RussoKM5VY
> > > Tijeras, NM
> > >
> > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
> [n-z][a-m]
> > >
> > > ___
> > > Xastir mailing list
> > > Xastir@lists.xastir.org
> > > http://xastir.org/mailman/listinfo/xastir
> >
> > --
> > Tom RussoKM5VY
> > Tijeras, NM
> >
> > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
> [n-z][a-m]
> >
> > ___
> > Xastir mailing list
> > Xastir@lists.xastir.org
> > http://xastir.org/mailman/listinfo/xastir
>
> --
> Tom RussoKM5VY
> Tijeras, NM
>
> echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
> [n-z][a-m]
>
> ___
> Xastir mailing list
> Xastir@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir
>
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Did the NWS pull a fast one - Shapefile data
Done. On Sat, Dec 21, 2019 at 4:28 PM Curt Mills wrote: > > Checked in the first fix. > > Looks like the FZ files matched some of the other dbfawk files > earlier, so we never had to create specific dbfawks for them. That's > now changed and I'm adding yet another dbfawk file to match the > current FZ maps. Will check in shortly after testing. > > On Sat, Dec 21, 2019 at 4:15 PM Curt Mills wrote: > > > > Working on it. I have the 'z' files working now, but the "fz" files > > have the same problem. I don't see any dbfawk files for the "fz" files > > at all. > > > > I'll check in the first fix shortly. > > > > On Sat, Dec 21, 2019 at 4:10 PM Tom Russo wrote: > > > > > > On Sat, Dec 21, 2019 at 03:45:04PM -0800, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > I think that despite the filename being the same, the NWS pulled a fast > > > > one > > > > and silently updated the z_10oc19.dbf file. > > > > > > They have done that time and again, which is why there is a proliferation > > > of dbfawks in the config directory (so that people who don't want to > > > update > > > their NWS files constantly don't have their old files made useless when > > > we change the dbfawk to make them work with the new files --- so instead, > > > each time there's a change we just create a new dbfawk and leave the old > > > in > > > place). > > > > > > > I did a git pull today and it pulled in a new get-NWSDATA script so I > > > > went > > > > ahead and ran it after a full compile. It's reporting that there isn't > > > > a > > > > dbfawk signature match for that NWS file. > > > > > > > > I took a look at the Wiki but I can't tell which file(s) in the dbfwak > > > > database are used for the z_ files so I'm having trouble rolling my own. > > > > > > The dbfawks associated with the NWS zone shapefiles are "nwsz_*.dbfawk) > > > in the config directory. > > > > > > Copy the latest one, which would be nwsz_ddmmyy13.dbfawk (appears > > > that the zone signature hasn't changed in 6 years --- it used to change > > > more often). Call it "nwsz_ddmmyy19.dbfawk" and change the "dbfinfo" line > > > to match the signature in the new files (which you can get by using the > > > "testdbfawk" program: > > > testdbfawk -D /usr/local/share/xastir/config -d [your new shapefile name] > > > whose second line of output is the signature, which could be cut and > > > pasted > > > into the "dbfinfo" value. > > > > > > If they haven't changed the actual names of columns, just the ordering, > > > you > > > should be good to go. If they changed the names, you'll have to change > > > the > > > "dbffields" variable, too, to pick out the two important columns, the zone > > > number and the name. > > > > > > If that fixes things, then let us know and we can add the new dbfawk to > > > the > > > repo. Curt just updated get-NWS a couple of weeks ago, and perhaps > > > overlooked > > > this step (since it's been a few years since dbfawks needed updating). > > > > > > -- > > > Tom RussoKM5VY > > > Tijeras, NM > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com > > > > -- > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Did the NWS pull a fast one - Shapefile data
Checked in the first fix. Looks like the FZ files matched some of the other dbfawk files earlier, so we never had to create specific dbfawks for them. That's now changed and I'm adding yet another dbfawk file to match the current FZ maps. Will check in shortly after testing. On Sat, Dec 21, 2019 at 4:15 PM Curt Mills wrote: > > Working on it. I have the 'z' files working now, but the "fz" files > have the same problem. I don't see any dbfawk files for the "fz" files > at all. > > I'll check in the first fix shortly. > > On Sat, Dec 21, 2019 at 4:10 PM Tom Russo wrote: > > > > On Sat, Dec 21, 2019 at 03:45:04PM -0800, we recorded a bogon-computron > > collision of the flavor, containing: > > > I think that despite the filename being the same, the NWS pulled a fast > > > one > > > and silently updated the z_10oc19.dbf file. > > > > They have done that time and again, which is why there is a proliferation > > of dbfawks in the config directory (so that people who don't want to update > > their NWS files constantly don't have their old files made useless when > > we change the dbfawk to make them work with the new files --- so instead, > > each time there's a change we just create a new dbfawk and leave the old in > > place). > > > > > I did a git pull today and it pulled in a new get-NWSDATA script so I went > > > ahead and ran it after a full compile. It's reporting that there isn't a > > > dbfawk signature match for that NWS file. > > > > > > I took a look at the Wiki but I can't tell which file(s) in the dbfwak > > > database are used for the z_ files so I'm having trouble rolling my own. > > > > The dbfawks associated with the NWS zone shapefiles are "nwsz_*.dbfawk) > > in the config directory. > > > > Copy the latest one, which would be nwsz_ddmmyy13.dbfawk (appears > > that the zone signature hasn't changed in 6 years --- it used to change > > more often). Call it "nwsz_ddmmyy19.dbfawk" and change the "dbfinfo" line > > to match the signature in the new files (which you can get by using the > > "testdbfawk" program: > > testdbfawk -D /usr/local/share/xastir/config -d [your new shapefile name] > > whose second line of output is the signature, which could be cut and pasted > > into the "dbfinfo" value. > > > > If they haven't changed the actual names of columns, just the ordering, you > > should be good to go. If they changed the names, you'll have to change the > > "dbffields" variable, too, to pick out the two important columns, the zone > > number and the name. > > > > If that fixes things, then let us know and we can add the new dbfawk to the > > repo. Curt just updated get-NWS a couple of weeks ago, and perhaps > > overlooked > > this step (since it's been a few years since dbfawks needed updating). > > > > -- > > Tom RussoKM5VY > > Tijeras, NM > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > [n-z][a-m] > > > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > > -- > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Did the NWS pull a fast one - Shapefile data
Working on it. I have the 'z' files working now, but the "fz" files have the same problem. I don't see any dbfawk files for the "fz" files at all. I'll check in the first fix shortly. On Sat, Dec 21, 2019 at 4:10 PM Tom Russo wrote: > > On Sat, Dec 21, 2019 at 03:45:04PM -0800, we recorded a bogon-computron > collision of the flavor, containing: > > I think that despite the filename being the same, the NWS pulled a fast one > > and silently updated the z_10oc19.dbf file. > > They have done that time and again, which is why there is a proliferation > of dbfawks in the config directory (so that people who don't want to update > their NWS files constantly don't have their old files made useless when > we change the dbfawk to make them work with the new files --- so instead, > each time there's a change we just create a new dbfawk and leave the old in > place). > > > I did a git pull today and it pulled in a new get-NWSDATA script so I went > > ahead and ran it after a full compile. It's reporting that there isn't a > > dbfawk signature match for that NWS file. > > > > I took a look at the Wiki but I can't tell which file(s) in the dbfwak > > database are used for the z_ files so I'm having trouble rolling my own. > > The dbfawks associated with the NWS zone shapefiles are "nwsz_*.dbfawk) > in the config directory. > > Copy the latest one, which would be nwsz_ddmmyy13.dbfawk (appears > that the zone signature hasn't changed in 6 years --- it used to change > more often). Call it "nwsz_ddmmyy19.dbfawk" and change the "dbfinfo" line > to match the signature in the new files (which you can get by using the > "testdbfawk" program: > testdbfawk -D /usr/local/share/xastir/config -d [your new shapefile name] > whose second line of output is the signature, which could be cut and pasted > into the "dbfinfo" value. > > If they haven't changed the actual names of columns, just the ordering, you > should be good to go. If they changed the names, you'll have to change the > "dbffields" variable, too, to pick out the two important columns, the zone > number and the name. > > If that fixes things, then let us know and we can add the new dbfawk to the > repo. Curt just updated get-NWS a couple of weeks ago, and perhaps overlooked > this step (since it's been a few years since dbfawks needed updating). > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] u-blox 8
Oh yea, also disconnect Minicom from that port, and set the GPS to send out NMEA format strings at 4800 baud. Typically on Linux it would be something like port /dev/ttyS0 or /dev/ttyS1, but could be other ports if using a USB to Serial Port adapter cable. On Tue, Dec 17, 2019 at 1:14 PM Curt Mills wrote: > > The use of Minicom tells me he's using a serial GPS. The Xastir > interface to use is "Serial GPS". He may be running into trouble with > permissions on the serial port he is using. Typically he'd add his own > account to /etc/group for the "dialout" group, log out and in again to > gain the new permissions. Depending on the particular Linux that last > may be slightly different. > > On Tue, Dec 17, 2019 at 1:10 PM MJ Inabnit wrote: > > > > hi all, > > > > this is a RELAY from km6liq > > > > how do I tell xastir which protocol to use for this device? > > I load minicom and see data flowing constantly. Any help > > greatly desired! > > Carl km6liq via 2m phone net > > > > tnx guys, I don't know the gps stuff for xastir and unable to help him! > > > > 73 > > j > > > > -- > > Wishing you well > > Jaye Inabnit, ke6sls > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > > -- > Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] u-blox 8
The use of Minicom tells me he's using a serial GPS. The Xastir interface to use is "Serial GPS". He may be running into trouble with permissions on the serial port he is using. Typically he'd add his own account to /etc/group for the "dialout" group, log out and in again to gain the new permissions. Depending on the particular Linux that last may be slightly different. On Tue, Dec 17, 2019 at 1:10 PM MJ Inabnit wrote: > > hi all, > > this is a RELAY from km6liq > > how do I tell xastir which protocol to use for this device? > I load minicom and see data flowing constantly. Any help > greatly desired! > Carl km6liq via 2m phone net > > tnx guys, I don't know the gps stuff for xastir and unable to help him! > > 73 > j > > -- > Wishing you well > Jaye Inabnit, ke6sls > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://xastir.orghttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] [aprssig] PocketAPRS Maps and MacDLG Map Generator Program
FYI: Here's the search I did to find all of the PocketAPRS maps I had
on my system. I did this once in my home directory (found some old
backups from my PalmOS device that had PocketAPRS maps) and once from
my /usr/local/share/xastir/maps/ directory.
find . 2>/dev/null -name \*.pdb -exec grep -l map1pAPR {} \;
On Mon, Dec 9, 2019 at 2:04 PM Curt Mills wrote:
>
> Xastir's latest code doesn't handle PocketAPRS maps anymore.
>
> Before you delete the files, consider getting copies of what you have to
> Jason.
>
> -- Forwarded message -
> From: Jason Rausch
> Date: Mon, Dec 9, 2019 at 1:18 PM
> Subject: [aprssig] PocketAPRS Maps and MacDLG Map Generator Program
> To: aprs...@lists.tapr.org
>
>
> I'm looking for anyone who might have an archive of any or all of the
> PocketAPRS maps that were generated years ago. I'm also looking for a
> copy of the MacDLG program for generating those maps. It was a
> strictly Mac program and I know it was at one time available for
> download from the TAPR FTP site. Those links are all dead now.
>
> Thanks!
>
> Jason Rausch
> www.ke4nyv.com
> ___
> aprssig mailing list
> aprs...@lists.tapr.org
> http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
>
>
> --
> Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com
--
Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com
___
Xastir mailing list
Xastir@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir
[Xastir] Fwd: [aprssig] PocketAPRS Maps and MacDLG Map Generator Program
Xastir's latest code doesn't handle PocketAPRS maps anymore. Before you delete the files, consider getting copies of what you have to Jason. -- Forwarded message - From: Jason Rausch Date: Mon, Dec 9, 2019 at 1:18 PM Subject: [aprssig] PocketAPRS Maps and MacDLG Map Generator Program To: aprs...@lists.tapr.org I'm looking for anyone who might have an archive of any or all of the PocketAPRS maps that were generated years ago. I'm also looking for a copy of the MacDLG program for generating those maps. It was a strictly Mac program and I know it was at one time available for download from the TAPR FTP site. Those links are all dead now. Thanks! Jason Rausch www.ke4nyv.com ___ aprssig mailing list aprs...@lists.tapr.org http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Ambient Weather Station
Does it use its own protocol? If so it's unlikely to be supported by Xastir. Unless... There was some universal file format that Xastir doesn't support but somebody may have written a script to parse it and feed to Xastir (nagging feeling in the back of my mind that I may have heard about that): If so you might have a chance. WXNOW format maybe? Somebody else pipe in that knows more please. On Mon, Nov 25, 2019 at 6:28 PM Chip Griffin wrote: > > Has anyone connected (or attempted to connect) an Ambient Weather Station to > Xastir? I don’t have one, but I am looking at one. > > > -- > Chip > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Now that I have it, What do I do with it?
On Mon, Oct 28, 2019 at 12:10 PM wa7skg wrote: > > I finally have Xastir running, decoding and displaying data. Now what? > Various questions abound. This would be a very good subject for a new Wiki page... > 1. Maps. Map > Map Chooser gives me a list that I have no idea which to > choose. Is there a description some place about these? I've tried > several, some take many minutes to load, some look like a child drew > them with a broken crayon, others simply make no sense. One of Xastir's strong points is that it can use so many different types of maps. I'm using the Online/OSM_tiled* maps. One key thing to know: If you're using raster maps you generally want to select only one. If you're using vector maps, especially ones that don't fill in areas, you can use multiple at the same time. You can also do your own map stackups with certain maps (like vector) on top of others (perhaps a bottom-of-the-stack raster map). Play around with one map at a time until you figure out the useful / favorite ones. Read README.MAPS file. Check out the xastir.org Wiki pages. > 2. What am I looking at on the screen? I see a bunch of icons. I can't > seem to find any kind of legend that tells me what they are. Some of the > icons have associated text that is completely unreadable. They are > bright yellow, small, and in a weird font. I am also seeing various > lines on the screen. Some are associated with icons, some not. Some are > straight, some have specific bends, others just seem to randomly meander > around the screen. Some are solid, some are dotted, some are dashed. > They are in all colors, red, black, green, violet, white, blue, etc. > These lines seemingly come and go at random. Some of the icons have red > flags on them that look like wind symbols on weather charts. Zooming in > only shows a smaller area, it does not affect the text at all. If you compiled Xastir with fontconfig support you can change several of the fonts to your liking. Some of the stuff you describe above sounds like you are trying the oldest style of maps: APRSdos maps. Try other maps. You can enable/disable various types of stations on the Station->Filter Data menu, and decide which parameters of the stations to display on the Station->Filter Display menu. > 3. The navigation buttons at the top are very awkward to use. They move > in such large jumps it is hard to center on any particular segment of > the screen. Then don't use them. Use the PageUp/Dwn keys to zoom in/out, and use the mouse to zoom into the exact area you wish. You can also use the arrow keys. There's a way to remember a map zoom and center as well and call it up again from the mouse menus. > 4. Should I be beaconing or something to show others I am there? I have > yet to see my radio transmit. I look at on-line resources like aprs.fi > and I see everybody on my screen except me. Set up an Interface on the Interfaces menu to connect to an internet feed or a local TNC. Allow transmitting on that interface. Allow global transmitting on the main Interface manu. Set up your callsign and location on the File->Configure->Station menu. Run through the File->Configure->Defaults menu and set what you'd like there. > 5. I guess the biggest question right now is, so what? What purpose does > this serve me right now? How can I utilize this information? I > understand I can send messages, but is everybody looking for messages? Depends on what you want to do with it. I use it for SAR and watching my friends on APRS, as well as watching ADS-B (planes) and AIS (ships). Everyone seems to have a different purpose for running it. I'm typing mostly with one hand these days. The above took a lot of effort. Yell out if you need more and I'm sure others will jump in. -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir-dev] Travis CI has Ubuntu-18.04LTS
Regarding the OSX build, I see this list on Travis CI for OSX versions. We're using "xcode10.2" right now: osx_image value Xcode version Xcode build version macOS version JDK osx_image: xcode11 Xcode 11.0 11A420a macOS 10.14 12.0.2 osx_image: xcode10.3 Xcode 10.3 18E226 macOS 10.14.4 osx_image: xcode10.2 Xcode 10.2.1 10E1001 macOS 10.14 12+33 Which means we could now use 10.3 or 11.0 for Travis CI builds. I'm not an OSX user so I'll defer to others as to whether it's worth the effort to switch. On Fri, Sep 27, 2019 at 1:42 PM Curt Mills wrote: > > Swapped the Travis builds around. We now have: > > Current Travis CI builds: > Ubuntu-18.04LTS light w/ImageMagick > Ubuntu-18.04LTS gcc-9 full-featured w/GraphicsMagick > OSX semi-light w/GraphicsMagick > Ubuntu-16.04LTS Exercise Configure Options > > So I upgraded two from 16.04 to 18.04 and swapped in the gcc-9 > compiler on one. There are plenty of compiler warnings to read on that > one. > > On Fri, Sep 27, 2019 at 9:08 AM Curt Mills wrote: > > > > Looks like Travis CI has Ubuntu-18.04LTS now. We should add builds for > > for it. Once working we could remove the Ubuntu-16.04LTS builds. Any > > reason not to? > > > > Current Travis CI builds: > > Ubuntu-16.04 light w/ImageMagick > > Ubuntu-16.04 gcc8 full-featured w/GraphicsMagick > > OSX semi-light w/GraphicsMagick > > Ubuntu-16.04 Exercise Configure Options > > > > -- > > Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com > > > > -- > Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
Re: [Xastir-dev] Travis CI has Ubuntu-18.04LTS
Swapped the Travis builds around. We now have: Current Travis CI builds: Ubuntu-18.04LTS light w/ImageMagick Ubuntu-18.04LTS gcc-9 full-featured w/GraphicsMagick OSX semi-light w/GraphicsMagick Ubuntu-16.04LTS Exercise Configure Options So I upgraded two from 16.04 to 18.04 and swapped in the gcc-9 compiler on one. There are plenty of compiler warnings to read on that one. On Fri, Sep 27, 2019 at 9:08 AM Curt Mills wrote: > > Looks like Travis CI has Ubuntu-18.04LTS now. We should add builds for > for it. Once working we could remove the Ubuntu-16.04LTS builds. Any > reason not to? > > Current Travis CI builds: > Ubuntu-16.04 light w/ImageMagick > Ubuntu-16.04 gcc8 full-featured w/GraphicsMagick > OSX semi-light w/GraphicsMagick > Ubuntu-16.04 Exercise Configure Options > > -- > Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
[Xastir-dev] Travis CI has Ubuntu-18.04LTS
Looks like Travis CI has Ubuntu-18.04LTS now. We should add builds for for it. Once working we could remove the Ubuntu-16.04LTS builds. Any reason not to? Current Travis CI builds: Ubuntu-16.04 light w/ImageMagick Ubuntu-16.04 gcc8 full-featured w/GraphicsMagick OSX semi-light w/GraphicsMagick Ubuntu-16.04 Exercise Configure Options -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
Re: [Xastir] Archaic default map
I'd lean toward more detailed maps at the cost of file size rather than less detailed maps these days. Even for an Rpi the file size is much less important. Perhaps someone can come up with some use-cases where the filesize is still critical, but it's getting to be less of a problem over time. On Mon, Jul 29, 2019 at 11:00 AM Tom Russo wrote: > > On Mon, Jul 29, 2019 at 12:51:56PM -0500, we recorded a bogon-computron > collision of the flavor, containing: > > Tiles require either Imagemagick or GraphicsMagick, and as Tom already > > stated that's not desirable for a minimum install of Xastir. > > Yeah, but his follow-up appears to be volunteering to try to find a shapefile > representation of the OSM data from which the Stamen tiles are generated. > So long as the license is consistent (it may not be) that is helpful. > > We're also looking at naturalearth's shapefiles, which include a relatively > small (750k or so), fairly rough map that could be suitable. > > We're not looking to have a default map that's high quality and beautiful, > just one that isn't 30 years out of date. We already have a low quality > and ugly map, it's just also wrong. It's about 250k. > > If a user wants a GOOD map, they're still going to have to do some work, > either by building Xastir with support for on-line maps, or by finding > more detailed local maps that suit their specific needs. The naturalearth > maps include much more detailed shapefiles that could be such a choice, but > they're way too large to be part of the Xastir distribution. > > > On Mon, Jul 29, 2019, 3:05 AM Hal Mueller wrote: > > > > > Roughly what file size are we targeting? The Stamen stuff is based on Open > > > Street Map. I think the country level data will be fairly easy to extract > > > from OSM, or (more likely) already exists. If I see a way through I???ll > > > hop > > > over to github and self assign. > > > > > > Hal > > > N3YX > > > > > > > On Jul 28, 2019, at 11:27 PM, Tom Russo wrote: > > > > > > > > Only vector maps need apply, specifically shapefile. Anything else > > > requires > > > > too many TPLs, and that would be too big a "minimum" install. > > > > > > > > On Sun, Jul 28, 2019 at 11:25:59PM -0700, we recorded a bogon-computron > > > collision of the flavor, containing: > > > >> Perhaps a joined together version of tiles at > > > http://maps.stamen.com/toner/#5/38.221/17.402? What pixel size is > > > preferred? How much space can it consume? > > > >> > > > >> Hal > > > >> N3YX > > > > > > > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Archaic default map
On Sun, Jul 28, 2019 at 6:15 PM Tom Russo wrote: > > - If Xastir stopped letting you turn off shapefile support, and required > it just like we require Motif and X11, would you be beside yourself with > rage? No. A reasonable change and I'm fine with it. > - If, as is called for in bug #128, > https://github.com/Xastir/Xastir/issues/128, we also made PCRE > a mandatory third party library and made DBFAWK support (which > is the only thing that uses PCRE in Xastir) unconditional, > would you revolt? No. If we're doing Shapelib as a requirement I think we should do this too. It's tiny. > - Do you have any favorite world shapefile maps that might be suitable > as a world-wide default map No unfortunately. -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Raspian Builds
How's this? > SELECT Cast(user_name AS CHAR), Cast(User_Email AS CHAR) FROM user where > user_name = 'Kg4wsv'; +-+--+ | Cast(user_name AS CHAR) | Cast(User_Email AS CHAR) | +-+--+ | Kg4wsv | | +-+--+ 1 row in set (0.00 sec) > UPDATE user SET user_email='CHANGED TO PROTECT FROM SPAM' WHERE user_name = > 'Kg4wsv'; Query OK, 1 row affected (0.00 sec) Rows matched: 1 Changed: 1 Warnings: 0 > SELECT Cast(user_name AS CHAR), Cast(User_Email AS CHAR) FROM user where > user_name = 'Kg4wsv'; +-+--+ | Cast(user_name AS CHAR) | Cast(User_Email AS CHAR) | +-+--+ | Kg4wsv | CHANGED TO PROTECT FROM SPAM | +-+--+ 1 row in set (0.00 sec) Try it now Jason! On Mon, Jul 15, 2019 at 9:03 AM km5vy Tom Russo wrote: > > On Mon, Jul 15, 2019 at 08:37:14AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > Or delete the user and create a fresh account? > > There is apparently no longer a way to delete a user from the web interface > anymore, either: > https://www.mediawiki.org/wiki/Topic:Uufq7bc2yldm78jq > > The recommended method of faking it, "merging a user to an anonymous account", > can only be done with an extension that does not appear to be installed > on this instance of the wiki. > > > On Mon, Jul 15, 2019 at 8:30 AM Tom Russo wrote: > > > > > > It appears that there is no way to change a users' email address from the > > > MediaWiki web interface (at least in the version that's installed on > > > xastir.org). It has to be done externally to the web, on the command > > > line. > > > That means Curt will have to take care of it. > > > > > > https://www.mediawiki.org/wiki/Manual:ResetUserEmail.php > > > > > > > > > On Mon, Jul 15, 2019 at 09:19:35AM -0600, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > On Mon, Jul 15, 2019 at 10:18:01AM -0500, we recorded a bogon-computron > > > > collision of the flavor, containing: > > > > > On Mon, Jul 15, 2019 at 9:02 AM Tom Russo wrote: > > > > > > > > > > > > > > > > According to the user list page on the wiki, you not only have an > > > > > > account > > > > > > on the wiki, but also edit permissions. > > > > > > > > > > > > > > > > In my (failed) search for my password, I stumbled across this gem > > > > > (from me, > > > > > circa 2009): > > > > > > > > > > I have a login (Kg4wsv), but apparently did not supply an email > > > > > > address (needed for the software to reset the password) and I don't > > > > > > remember the password. > > > > > > Is there a wiki admin who can reset my password, or stick my email > > > > > > address on the wiki account? > > > > > > > > > > > > > > > Is there a wiki admin that can help me out? > > > > > > > > Heh. I'll see what I can do. It is so infrequent that I use my mad > > > > admin > > > > skilz that I don't remember if there's an admin feature to edit a user > > > > account. If there is, I'll add the email address you're posting from > > > > now. > > > > > > > > -- > > > > Tom RussoKM5VY > > > > Tijeras, NM > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > > [n-z][a-m] > > > > > > -- > > > Tom RussoKM5VY > > > Tijeras, NM > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Raspian Builds
Nope, this version of Mediawiki (1.23.0) doesn't have that script. I might be able to change it in the database but since I'm not a DBA that may take more time. On Mon, Jul 15, 2019 at 8:45 AM Curt Mills wrote: > > I'll try to change it with the script first. > > On Mon, Jul 15, 2019 at 8:37 AM Curt Mills wrote: > > > > Or delete the user and create a fresh account? > > > > On Mon, Jul 15, 2019 at 8:30 AM Tom Russo wrote: > > > > > > It appears that there is no way to change a users' email address from the > > > MediaWiki web interface (at least in the version that's installed on > > > xastir.org). It has to be done externally to the web, on the command > > > line. > > > That means Curt will have to take care of it. > > > > > > https://www.mediawiki.org/wiki/Manual:ResetUserEmail.php > > > > > > > > > On Mon, Jul 15, 2019 at 09:19:35AM -0600, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > On Mon, Jul 15, 2019 at 10:18:01AM -0500, we recorded a bogon-computron > > > > collision of the flavor, containing: > > > > > On Mon, Jul 15, 2019 at 9:02 AM Tom Russo wrote: > > > > > > > > > > > > > > > > According to the user list page on the wiki, you not only have an > > > > > > account > > > > > > on the wiki, but also edit permissions. > > > > > > > > > > > > > > > > In my (failed) search for my password, I stumbled across this gem > > > > > (from me, > > > > > circa 2009): > > > > > > > > > > I have a login (Kg4wsv), but apparently did not supply an email > > > > > > address (needed for the software to reset the password) and I don't > > > > > > remember the password. > > > > > > Is there a wiki admin who can reset my password, or stick my email > > > > > > address on the wiki account? > > > > > > > > > > > > > > > Is there a wiki admin that can help me out? > > > > > > > > Heh. I'll see what I can do. It is so infrequent that I use my mad > > > > admin > > > > skilz that I don't remember if there's an admin feature to edit a user > > > > account. If there is, I'll add the email address you're posting from > > > > now. > > > > > > > > -- > > > > Tom RussoKM5VY > > > > Tijeras, NM > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > > [n-z][a-m] > > > > > > -- > > > Tom RussoKM5VY > > > Tijeras, NM > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com > > > > -- > Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Raspian Builds
I'll try to change it with the script first. On Mon, Jul 15, 2019 at 8:37 AM Curt Mills wrote: > > Or delete the user and create a fresh account? > > On Mon, Jul 15, 2019 at 8:30 AM Tom Russo wrote: > > > > It appears that there is no way to change a users' email address from the > > MediaWiki web interface (at least in the version that's installed on > > xastir.org). It has to be done externally to the web, on the command line. > > That means Curt will have to take care of it. > > > > https://www.mediawiki.org/wiki/Manual:ResetUserEmail.php > > > > > > On Mon, Jul 15, 2019 at 09:19:35AM -0600, we recorded a bogon-computron > > collision of the flavor, containing: > > > On Mon, Jul 15, 2019 at 10:18:01AM -0500, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > On Mon, Jul 15, 2019 at 9:02 AM Tom Russo wrote: > > > > > > > > > > > > > According to the user list page on the wiki, you not only have an > > > > > account > > > > > on the wiki, but also edit permissions. > > > > > > > > > > > > > In my (failed) search for my password, I stumbled across this gem (from > > > > me, > > > > circa 2009): > > > > > > > > I have a login (Kg4wsv), but apparently did not supply an email > > > > > address (needed for the software to reset the password) and I don't > > > > > remember the password. > > > > > Is there a wiki admin who can reset my password, or stick my email > > > > > address on the wiki account? > > > > > > > > > > > > Is there a wiki admin that can help me out? > > > > > > Heh. I'll see what I can do. It is so infrequent that I use my mad admin > > > skilz that I don't remember if there's an admin feature to edit a user > > > account. If there is, I'll add the email address you're posting from now. > > > > > > -- > > > Tom RussoKM5VY > > > Tijeras, NM > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > [n-z][a-m] > > > > -- > > Tom RussoKM5VY > > Tijeras, NM > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > [n-z][a-m] > > > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > > -- > Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Raspian Builds
Or delete the user and create a fresh account? On Mon, Jul 15, 2019 at 8:30 AM Tom Russo wrote: > > It appears that there is no way to change a users' email address from the > MediaWiki web interface (at least in the version that's installed on > xastir.org). It has to be done externally to the web, on the command line. > That means Curt will have to take care of it. > > https://www.mediawiki.org/wiki/Manual:ResetUserEmail.php > > > On Mon, Jul 15, 2019 at 09:19:35AM -0600, we recorded a bogon-computron > collision of the flavor, containing: > > On Mon, Jul 15, 2019 at 10:18:01AM -0500, we recorded a bogon-computron > > collision of the flavor, containing: > > > On Mon, Jul 15, 2019 at 9:02 AM Tom Russo wrote: > > > > > > > > > > According to the user list page on the wiki, you not only have an > > > > account > > > > on the wiki, but also edit permissions. > > > > > > > > > > In my (failed) search for my password, I stumbled across this gem (from > > > me, > > > circa 2009): > > > > > > I have a login (Kg4wsv), but apparently did not supply an email > > > > address (needed for the software to reset the password) and I don't > > > > remember the password. > > > > Is there a wiki admin who can reset my password, or stick my email > > > > address on the wiki account? > > > > > > > > > Is there a wiki admin that can help me out? > > > > Heh. I'll see what I can do. It is so infrequent that I use my mad admin > > skilz that I don't remember if there's an admin feature to edit a user > > account. If there is, I'll add the email address you're posting from now. > > > > -- > > Tom RussoKM5VY > > Tijeras, NM > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > [n-z][a-m] > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] GraphicsMagick include issue on Gentoo
+1 On Sun, Jul 14, 2019 at 1:26 PM Tom Russo wrote: > > On Sun, Jul 14, 2019 at 07:23:00AM -0600, we recorded a bogon-computron > collision of the flavor, containing: > > On Sun, Jul 14, 2019 at 08:24:21PM +1000, we recorded a bogon-computron > > collision of the flavor, containing: > > > > > > > > > > On 14 Jul 2019, at 7:26 pm, Carl Makin wrote: > > > > Would it be worthwhile pushing this as a point release? > > > > > > Actually, don???t worry about it. I???ll add the patch manually. > > > > I was going to suggest just adding the single patch based on commit > > fb6ecce5. > > > Correction: commit 7b6ecce5 > > On the other hand, a point release to fix this wouldn't be unreasonable, given > how many OSen are affected by this mistaken use of GraphicsMagick. Might > be better to get it out there as a release instead of having many independent > patches. > > What to the rest of you all think? The code is relatively stable at the > moment. > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
[Xastir] Steam train script
Had to rewrite my script AGAIN, but the "STEAM" object is again being generated and sent to Firenet servers. Currently headed toward Lincoln, NE. -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Blank Bulletins window keeps popping up?
May be something I broke during reformatting then. On Sat, Jun 22, 2019, 1:25 PM Tom Henderson wrote: > It looks like I got a blank window popup at about the same time as this > log entry: > > # 1561224182 Sat Jun 22 12:23:02 CDT 2019 > AL2C-FD>APWW10,TCPIP*,qAC,T2EISBERG::BLN0 :Field Day June 22-23 @ > the Smith Center 298 Jay Street, Prattville, AL 36066. 9 AM Sat - 1 PM > Sun. VE Testing @ 10 AM. > > Tom Henderson > > On 6/21/19 11:12 AM, Curt Mills wrote: > > I haven't personally seen that odd operation. Have you checked the > > incoming data to see if perhaps someone is sending something odd? It's > > definitely possible that a bug crept into the Xastir code as well. > > > > On Fri, Jun 21, 2019 at 9:04 AM Tom Henderson wrote: > >> After receiving a bulletin earlier today, and closing the window, xastir > >> is now popping up a blank bulletins window every few minutes. is this a > >> setting I have screwed up somewhere? > >> > >> -- > >> Tom Henderson > >> > >> ___ > >> Xastir mailing list > >> Xastir@lists.xastir.org > >> http://xastir.org/mailman/listinfo/xastir > > > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Blank Bulletins window keeps popping up?
I haven't personally seen that odd operation. Have you checked the incoming data to see if perhaps someone is sending something odd? It's definitely possible that a bug crept into the Xastir code as well. On Fri, Jun 21, 2019 at 9:04 AM Tom Henderson wrote: > > After receiving a bulletin earlier today, and closing the window, xastir > is now popping up a blank bulletins window every few minutes. is this a > setting I have screwed up somewhere? > > -- > Tom Henderson > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Turn-by-turn directions?
That object format can only hold so many segments, so probably not a great fit for this. One could create a Shapefile map overlay out of it though. Not sure how turn-by-turn could work with that, but some limited functionality might be had. Heaven help you if you got off-course though, it wouldn't auto-recalculate. I use Google Maps on my cellphone for this. Or my designed-for-the-purpose Garmin Nuvi-350. On Fri, Jun 14, 2019 at 10:34 AM Jason KG4WSV wrote: > > On Fri, Jun 14, 2019 at 12:07 PM William McKeehan wrote: > > > > Would it be possible to integrate something like the Open Source > > Routing Machine > > (https://wiki.openstreetmap.org/wiki/Open_Source_Routing_Machine) into > > Xastir? > > > > > Maybe you could use an external program to generate an APRS multiline > object from the output of OSRM? > > -Jason > kg4wsv > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Turn-by-turn directions?
Even for our OSM maps we are only using tiles generated from a server elsewhere. We don't have the underlying data that would make routing possible. To do that you'd have to have a database engine running on the machine and a complete set of OSM data for the area of interest. That's beyond our project at the moment. On Fri, Jun 14, 2019 at 10:07 AM William McKeehan wrote: > > A lot of times, when working an event, that I need to get directions. > I currently accomplish this with multiple devices - one showing APRS, > the other for routing. > > Would it be possible to integrate something like the Open Source > Routing Machine > (https://wiki.openstreetmap.org/wiki/Open_Source_Routing_Machine) into > Xastir? possibly providing the directions as a layer on top of the > other maps being used? > > On Fri, Jun 14, 2019 at 12:55 PM Curt Mills wrote: > > > > Nope. The only address-like thing we have is a quite-old feature for > > finding a location by street address. > > > > To get into routing and turn-by-turn directions we'd need the proper > > up-to-date maps with speed limits and lanes, put that into a directed > > graph, then walk the graph to look for the 2 or 3 best routes through > > the graph from point A to point B. We have none of that. > > > > On Fri, Jun 14, 2019 at 9:36 AM William McKeehan wrote: > > > > > > Is there any way to get directions in Xastir? Is such a feature on the > > > list of desired things? > > > > > > -- > > > William > > > KI4HDU > > > ___ > > > Xastir mailing list > > > Xastir@lists.xastir.org > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > > -- > William > KI4HDU > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Turn-by-turn directions?
Nope. The only address-like thing we have is a quite-old feature for finding a location by street address. To get into routing and turn-by-turn directions we'd need the proper up-to-date maps with speed limits and lanes, put that into a directed graph, then walk the graph to look for the 2 or 3 best routes through the graph from point A to point B. We have none of that. On Fri, Jun 14, 2019 at 9:36 AM William McKeehan wrote: > > Is there any way to get directions in Xastir? Is such a feature on the > list of desired things? > > -- > William > KI4HDU > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Code reformatted to new coding standard
Then something about llamas. On Mon, Jun 10, 2019, 7:24 PM David Flood wrote: > First thing I thought when I read the subject: "The directors of the firm > hired to continue the credits after the other people had been sacked, wish > it to be known that they have just been sacked. The credits have been > completed in an entirely different style at great expense and at the last > minute." > > Dave > KD7MYC > > -Original Message- > From: Xastir [mailto:xastir-boun...@lists.xastir.org] On Behalf Of Curt > Mills > Sent: Monday, June 10, 2019 09:42 > > The Xastir code has been completely reformatted to the new coding > standard we voted on. > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
[Xastir] Code reformatted to new coding standard
The Xastir code has been completely reformatted to the new coding standard we voted on. The pull request was merged this morning. That's of course the "master" Git branch. The code looks cleaner now and is easier to read. The top of this HOWTO states the command used to reformat the code, which we can use again later if code starts deviating from our standard: http://xastir.org/index.php/HowTo:Developer_Guidelines_and_Notes We only reformatted the C code. We didn't touch Perl/Python/Shell scripts. Along the way, tabs were removed from the C sources also. By hand in that case so formatting didn't get messed up. Enjoy! -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir-dev] Possible to get rid of Xastir/m4/ directory?
I got Xastir to compile w/o it now. Files changed: modified: Makefile.am modified: configure.ac deleted:m4/Makefile.am deleted:m4/xmhtml.m4 Anyone know if we actually need the m4 directory and contents? On Wed, Jun 5, 2019 at 11:13 AM Curt Mills wrote: > I only see one file of consequence in the Xastir/m4/ directory: xmhtml.m4 > > Anyone know what it's used for? I've discovered that I can't just delete > it and get Xastir to compile, so we're dependent on it in some manner. > > -- > Curt, WE7Uhttp://we7u.wetnet.net > http://www.sarguydigital.com > -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
[Xastir-dev] Possible to get rid of Xastir/m4/ directory?
I only see one file of consequence in the Xastir/m4/ directory: xmhtml.m4 Anyone know what it's used for? I've discovered that I can't just delete it and get Xastir to compile, so we're dependent on it in some manner. -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
Re: [Xastir] 126,858 stations/objects in Xastir
Sounds like the same, yes. At some point Xastir can't keep up with an unfiltered full stream and the incoming queue gets bigger and bigger until you get a disconnection from the server. Xastir will process packets for a while out of the queue, then reconnect to the server if that option is checked. On Tue, Jun 4, 2019 at 1:29 PM MLHPUB wrote: > Hi Xastir list, > > Could it be Xastir behaviour I have noticed before as a "TCP/IP > connexion lost" ? > Were big latencies after more than H24 uptime without any filter. > > Never tried again. > > 73 de F4ACU > Matthieu > > > Le 03/06/2019 à 23:37, Curt Mills a écrit : > > A point of reference: I put Xastir on a full feed last week and got up to > > 120k+ stations. I then switched to a range-filtered Firenet feed for the > > next 24 hours and the number kept increasing. The max it hit was 126,858 > > stations, then the number declined as some of the earlier stations > started > > timing out. > > > > That's by far the highest number of stations I've personally seen in > > Xastir. To get there I had to zoom way in and turn off display of > > stations/objects/weather alerts. Even then Xastir kept disconnecting from > > the remote server periodically because it would get too far behind in > > processing packets. After I switched to the filtered feed the processing > > time was no longer an issue and it stayed connected to the server. > > > > Xastir's in-memory "database" and packet decoding are not optimized for > > those kinds of numbers. > > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] Xastir Release 2.1.2
Because you jumped right past the release version to the new development version. On Tue, Jun 4, 2019 at 7:03 AM Tom Henderson wrote: > I ran update-xastir and it worked smoothly. However, when I open the > "About Xastir" window, it says I am running 2.1.3. > > Tom Henderson > > On 6/2/19 9:03 PM, Curt Mills wrote: > > This release of Xastir implements the following changes: > > > > - National Weather Service shapefile script updated, dbfawk files added. > > > > - Compilation errors in OS X earlier than 10.6 fixed. > > > > - Tiger WMS server maps added. > > > > - A new set of National Map .geo files replaces those that referenced WMS > > products that have gone off-line since the last release. > > > > - GDAL and OGR support removed. > > > > - Xastir builds are now reproducible (builds no longer contain the build > > date and time). > > > > - Deprecated GraphicsMagick and ImageMagick function calls replaced with > > new API. > > > > - Download of tiled maps is now handled by a download manager running in > a > > separate thread, dramatically improving map update speed. > > > > - Obsolete interface to old Tiger/Line map server removed (the server > went > > down years ago). > > > > - OpenTrac decoding support removed. > > > > - Support for the old PocketAPRS (PalmOS based APRS) map format has been > > removed. Users of these old map types should transition to a more modern > > format. > > > > - Xastir sources no longer contains a copy of an old version of shapelib > > source. Shapelib support must now always be provided by an external > > library. > > > > - The embryonic "Xastir-qt" project has been moved to a separate > repository. > > > > - "Xastir -V" will now cause Xastir to report its version number (with > git > > sha-1 hash appended if built from a git clone) and exit. > > > > - Support for many additional satellite navigation (GNSS) receivers has > > been added to the existing GPS support. Prior to this release, only NMEA > > sentences starting with $GP were recognized. > > > > - Many compilation warnings from recent GCC and Clang compilers have been > > eliminated, resulting in a cleaner build. > > > > - Our Makefiles now default to "silent rules" to reduce uninteresting > > output during compliation. The old, noisier behavior may be invoked by > > adding "V=1" to the "make" line at build time. > > > > - The configure summary now shows the status of its probe for Xpm > libraries > > under "Xpm / Snapshots". > > > > Xastir web pages: http://xastir.org > > Xastir Code: https://github.com/Xastir/Xastir > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
[Xastir] 126,858 stations/objects in Xastir
A point of reference: I put Xastir on a full feed last week and got up to 120k+ stations. I then switched to a range-filtered Firenet feed for the next 24 hours and the number kept increasing. The max it hit was 126,858 stations, then the number declined as some of the earlier stations started timing out. That's by far the highest number of stations I've personally seen in Xastir. To get there I had to zoom way in and turn off display of stations/objects/weather alerts. Even then Xastir kept disconnecting from the remote server periodically because it would get too far behind in processing packets. After I switched to the filtered feed the processing time was no longer an issue and it stayed connected to the server. Xastir's in-memory "database" and packet decoding are not optimized for those kinds of numbers. -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
[Xastir] Xastir Release 2.1.2
This release of Xastir implements the following changes: - National Weather Service shapefile script updated, dbfawk files added. - Compilation errors in OS X earlier than 10.6 fixed. - Tiger WMS server maps added. - A new set of National Map .geo files replaces those that referenced WMS products that have gone off-line since the last release. - GDAL and OGR support removed. - Xastir builds are now reproducible (builds no longer contain the build date and time). - Deprecated GraphicsMagick and ImageMagick function calls replaced with new API. - Download of tiled maps is now handled by a download manager running in a separate thread, dramatically improving map update speed. - Obsolete interface to old Tiger/Line map server removed (the server went down years ago). - OpenTrac decoding support removed. - Support for the old PocketAPRS (PalmOS based APRS) map format has been removed. Users of these old map types should transition to a more modern format. - Xastir sources no longer contains a copy of an old version of shapelib source. Shapelib support must now always be provided by an external library. - The embryonic "Xastir-qt" project has been moved to a separate repository. - "Xastir -V" will now cause Xastir to report its version number (with git sha-1 hash appended if built from a git clone) and exit. - Support for many additional satellite navigation (GNSS) receivers has been added to the existing GPS support. Prior to this release, only NMEA sentences starting with $GP were recognized. - Many compilation warnings from recent GCC and Clang compilers have been eliminated, resulting in a cleaner build. - Our Makefiles now default to "silent rules" to reduce uninteresting output during compliation. The old, noisier behavior may be invoked by adding "V=1" to the "make" line at build time. - The configure summary now shows the status of its probe for Xpm libraries under "Xpm / Snapshots". Xastir web pages: http://xastir.org Xastir Code: https://github.com/Xastir/Xastir ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir-dev] [Xastir] ATTENTION: Preparing for next release: Please thrash on the code
. Is > > > > > > > whether or not that is supported in our platform based on what > > > > version of > > > > > > > curl is installed? > > > > > > > > > > > > > > - now that dlm.c handles downloading tiles, is there anything > left in > > > > > > > tile_mgmnt.c that is still needed or could tile_mgmnt.h and > > > > tile_mgmnt.c be > > > > > > > removed? It seems at a minimum the "getOneTile" portion of > > > > tile_mgmnt.c is > > > > > > > no longer needed. > > > > > > > > > > > > > > Looks like you guys are doing a lot of cleanup in this > release, so > > > > brought > > > > > > > that up just in case there's some stuff there that could be > > > > streamlined a > > > > > > > bit. > > > > > > > > > > > > > > Fyi, my Odroid XU4 (arm based) beats the pants off my Intel > Celeron > > > > based > > > > > > > laptop in terms of map download speed. Both are on Ubuntu > 18.04 > > > > with the > > > > > > > MATE desktop. Am wondering if the fact that the XU4 has an > octa-core > > > > cpu > > > > > > > makes a difference with respect to curl-multi. > > > > > > > > > > > > > > The cleaner compiling is very noticeable, and the earlier note > about > > > > newer > > > > > > > compilers spitting out more warnings matches what I saw. > Compiling > > > > is > > > > > > > cleaner in Debian Stretch and Ubuntu 16.04 than it is in Ubuntu > > > > 18.04, but > > > > > > > it still builds fine. (And even in Ubuntu 18.04 the new code > still > > > > > > > compiles a lot cleaner that the older code did) > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > Lee > > > > > > > K5DAT > > > > > > > > > > > > > > > > > > > > > On Thu, May 9, 2019 at 9:57 AM Curt Mills > > > > > wrote: > > > > > > > > > > > > > > > We're planning to do a release within a few weeks. It might > be as > > > > few as > > > > > > > 2 > > > > > > > > weeks. > > > > > > > > > > > > > > > > Please check out / compile / thrash on the latest Github > Xastir > > > > code. > > > > > > > Find > > > > > > > > anything that broke with our latest code fixes. Exercise all > types > > > > of > > > > > > > > interfaces, messaging, bulletins, weather stations, tracking, > > > > following > > > > > > > > stations, maps, etc. Anything you can think of. > > > > > > > > > > > > > > > > The latest code compiles much cleaner and a lot of fixes > went in > > > > to make > > > > > > > > that possible. We'd like this release to function well, so > > > > whatever you > > > > > > > can > > > > > > > > do to exercise the code would be most appreciated. > > > > > > > > > > > > > > > > If you find a bug or odd operation, report it here: > > > > > > > > > > > > > > > > https://github.com/Xastir/Xastir/issues > > > > > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > > -- > > > > > > > > Curt, WE7Uhttp://we7u.wetnet.net > > > > > > > > http://www.sarguydigital.com > > > > > > > > ___ > > > > > > > > Xastir mailing list > > > > > > > > xas...@lists.xastir.org > > > > > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > > > > > > > > ___ > > > > > > > Xastir mailing list > > > > > > > xas...@lists.xastir.org > > > > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Curt, WE7Uhttp://we7u.wetnet.net > > > > http://www.sarguydigital.com > > > > > > ___ > > > > > > Xastir mailing list > > > > > > xas...@lists.xastir.org > > > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > > > -- > > > > > Tom RussoKM5VY > > > > > Tijeras, NM > > > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > > [n-z][a-m] > > > > > > > > > > ___ > > > > > Xastir-dev mailing list > > > > > Xastir-dev@lists.xastir.org > > > > > http://xastir.org/mailman/listinfo/xastir-dev > > > > > > > > -- > > > > Tom RussoKM5VY > > > > Tijeras, NM > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > > [n-z][a-m] > > > > > > > > ___ > > > > Xastir mailing list > > > > xas...@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > Tom RussoKM5VY > > Tijeras, NM > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > [n-z][a-m] > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > [n-z][a-m] > > -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir-dev mailing list Xastir-dev@lists.xastir.org http://xastir.org/mailman/listinfo/xastir-dev
Re: [Xastir] [Xastir-dev] ATTENTION: Preparing for next release: Please thrash on the code
. Is > > > > > > > whether or not that is supported in our platform based on what > > > > version of > > > > > > > curl is installed? > > > > > > > > > > > > > > - now that dlm.c handles downloading tiles, is there anything > left in > > > > > > > tile_mgmnt.c that is still needed or could tile_mgmnt.h and > > > > tile_mgmnt.c be > > > > > > > removed? It seems at a minimum the "getOneTile" portion of > > > > tile_mgmnt.c is > > > > > > > no longer needed. > > > > > > > > > > > > > > Looks like you guys are doing a lot of cleanup in this > release, so > > > > brought > > > > > > > that up just in case there's some stuff there that could be > > > > streamlined a > > > > > > > bit. > > > > > > > > > > > > > > Fyi, my Odroid XU4 (arm based) beats the pants off my Intel > Celeron > > > > based > > > > > > > laptop in terms of map download speed. Both are on Ubuntu > 18.04 > > > > with the > > > > > > > MATE desktop. Am wondering if the fact that the XU4 has an > octa-core > > > > cpu > > > > > > > makes a difference with respect to curl-multi. > > > > > > > > > > > > > > The cleaner compiling is very noticeable, and the earlier note > about > > > > newer > > > > > > > compilers spitting out more warnings matches what I saw. > Compiling > > > > is > > > > > > > cleaner in Debian Stretch and Ubuntu 16.04 than it is in Ubuntu > > > > 18.04, but > > > > > > > it still builds fine. (And even in Ubuntu 18.04 the new code > still > > > > > > > compiles a lot cleaner that the older code did) > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > Lee > > > > > > > K5DAT > > > > > > > > > > > > > > > > > > > > > On Thu, May 9, 2019 at 9:57 AM Curt Mills > > > > > wrote: > > > > > > > > > > > > > > > We're planning to do a release within a few weeks. It might > be as > > > > few as > > > > > > > 2 > > > > > > > > weeks. > > > > > > > > > > > > > > > > Please check out / compile / thrash on the latest Github > Xastir > > > > code. > > > > > > > Find > > > > > > > > anything that broke with our latest code fixes. Exercise all > types > > > > of > > > > > > > > interfaces, messaging, bulletins, weather stations, tracking, > > > > following > > > > > > > > stations, maps, etc. Anything you can think of. > > > > > > > > > > > > > > > > The latest code compiles much cleaner and a lot of fixes > went in > > > > to make > > > > > > > > that possible. We'd like this release to function well, so > > > > whatever you > > > > > > > can > > > > > > > > do to exercise the code would be most appreciated. > > > > > > > > > > > > > > > > If you find a bug or odd operation, report it here: > > > > > > > > > > > > > > > > https://github.com/Xastir/Xastir/issues > > > > > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > > -- > > > > > > > > Curt, WE7Uhttp://we7u.wetnet.net > > > > > > > > http://www.sarguydigital.com > > > > > > > > ___ > > > > > > > > Xastir mailing list > > > > > > > > Xastir@lists.xastir.org > > > > > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > > > > > > > > ___ > > > > > > > Xastir mailing list > > > > > > > Xastir@lists.xastir.org > > > > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Curt, WE7Uhttp://we7u.wetnet.net > > > > http://www.sarguydigital.com > > > > > > ___ > > > > > > Xastir mailing list > > > > > > Xastir@lists.xastir.org > > > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > > > -- > > > > > Tom RussoKM5VY > > > > > Tijeras, NM > > > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > > [n-z][a-m] > > > > > > > > > > ___ > > > > > Xastir-dev mailing list > > > > > xastir-...@lists.xastir.org > > > > > http://xastir.org/mailman/listinfo/xastir-dev > > > > > > > > -- > > > > Tom RussoKM5VY > > > > Tijeras, NM > > > > > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > > > > [n-z][a-m] > > > > > > > > ___ > > > > Xastir mailing list > > > > Xastir@lists.xastir.org > > > > http://xastir.org/mailman/listinfo/xastir > > > > > > > > -- > > Tom RussoKM5VY > > Tijeras, NM > > > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > [n-z][a-m] > > -- > Tom RussoKM5VY > Tijeras, NM > > echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] > [n-z][a-m] > > -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir-dev] [Xastir] ATTENTION: Preparing for next release: Please thrash on the code
Fine by me. I can do all the announcements. On Mon, May 27, 2019, 10:07 AM Tom Russo wrote: > On Thu, May 23, 2019 at 01:05:53PM -0600, we recorded a bogon-computron > collision of the flavor, containing: > > On Thu, May 23, 2019 at 07:15:52AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > > Anyone else have any reports, good or bad? > > > > > > FWIW: For the types of things I do the latest code has been stable for > me. > > > > > > We're getting close to a release and Tom will most likely be the one > doing > > > it. No target date has been mentioned. If we run into any nasty bugs > that > > > might delay. > > > > Let's set a date right now. I can set aside the time to do the release > > on only a few days in the upcoming weeks (it doesn't take long, but it's > > a process that takes some attention, and is documented in > README.developers.md). > > > > The days I could do it are: > > Friday, 31 May > > Friday, 14 June > > Sometime on the weekend of 21-23 June. > > Can we pick one? I propose we just rip off the band-aid and do it > Friday 31 May. I can take care of the git work if you'll handle doing all > the various announcements. > > > I think that we are already at a point where there has been sufficient > time > > to shake out the code on master, and we could release today if we wanted > > to. Next friday is the earliest I have the opportunity to spend on it. > > > > If someone else wanted to try out the release process, it's all > documented > > in gory detail in README.developers.md, and if followed precisely would > > produce a new release that would be ready (down to file names of > tarballs) > > to slot into the package creation processes various distros use, just by > > changing the version number. Or pick a date and I'll do it then. > > > > > On Fri, May 17, 2019 at 6:16 PM Lee Bengston > wrote: > > > > > > > I've played with it some and and have not found any issues. I put > together > > > > a BPQ packet node in January, and I haven't fully back-filled what I > had > > > > "stolen" from aprs, so testing capability is fairly limited. From > what I > > > > can tell, though, it's nice and stable. > > > > > > > > I do have a few questions about the source ( yeah, always one in the > crowd > > > > :-) ) > > > > > > > > - In dlm.c noticed references to "curl-multi" and evidently the > capability > > > > to leverage parallel downloading of map tiles as supported by > libcurl. Is > > > > whether or not that is supported in our platform based on what > version of > > > > curl is installed? > > > > > > > > - now that dlm.c handles downloading tiles, is there anything left in > > > > tile_mgmnt.c that is still needed or could tile_mgmnt.h and > tile_mgmnt.c be > > > > removed? It seems at a minimum the "getOneTile" portion of > tile_mgmnt.c is > > > > no longer needed. > > > > > > > > Looks like you guys are doing a lot of cleanup in this release, so > brought > > > > that up just in case there's some stuff there that could be > streamlined a > > > > bit. > > > > > > > > Fyi, my Odroid XU4 (arm based) beats the pants off my Intel Celeron > based > > > > laptop in terms of map download speed. Both are on Ubuntu 18.04 > with the > > > > MATE desktop. Am wondering if the fact that the XU4 has an octa-core > cpu > > > > makes a difference with respect to curl-multi. > > > > > > > > The cleaner compiling is very noticeable, and the earlier note about > newer > > > > compilers spitting out more warnings matches what I saw. Compiling > is > > > > cleaner in Debian Stretch and Ubuntu 16.04 than it is in Ubuntu > 18.04, but > > > > it still builds fine. (And even in Ubuntu 18.04 the new code still > > > > compiles a lot cleaner that the older code did) > > > > > > > > Thanks, > > > > > > > > Lee > > > > K5DAT > > > > > > > > > > > > On Thu, May 9, 2019 at 9:57 AM Curt Mills > wrote: > > > > > > > > > We're planning to do a release within a few weeks. It might be as > few as > > > > 2 > > > > > weeks. > > > > > > > > > > Please check out / compile / thrash o
Re: [Xastir] [Xastir-dev] ATTENTION: Preparing for next release: Please thrash on the code
Fine by me. I can do all the announcements. On Mon, May 27, 2019, 10:07 AM Tom Russo wrote: > On Thu, May 23, 2019 at 01:05:53PM -0600, we recorded a bogon-computron > collision of the flavor, containing: > > On Thu, May 23, 2019 at 07:15:52AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > > Anyone else have any reports, good or bad? > > > > > > FWIW: For the types of things I do the latest code has been stable for > me. > > > > > > We're getting close to a release and Tom will most likely be the one > doing > > > it. No target date has been mentioned. If we run into any nasty bugs > that > > > might delay. > > > > Let's set a date right now. I can set aside the time to do the release > > on only a few days in the upcoming weeks (it doesn't take long, but it's > > a process that takes some attention, and is documented in > README.developers.md). > > > > The days I could do it are: > > Friday, 31 May > > Friday, 14 June > > Sometime on the weekend of 21-23 June. > > Can we pick one? I propose we just rip off the band-aid and do it > Friday 31 May. I can take care of the git work if you'll handle doing all > the various announcements. > > > I think that we are already at a point where there has been sufficient > time > > to shake out the code on master, and we could release today if we wanted > > to. Next friday is the earliest I have the opportunity to spend on it. > > > > If someone else wanted to try out the release process, it's all > documented > > in gory detail in README.developers.md, and if followed precisely would > > produce a new release that would be ready (down to file names of > tarballs) > > to slot into the package creation processes various distros use, just by > > changing the version number. Or pick a date and I'll do it then. > > > > > On Fri, May 17, 2019 at 6:16 PM Lee Bengston > wrote: > > > > > > > I've played with it some and and have not found any issues. I put > together > > > > a BPQ packet node in January, and I haven't fully back-filled what I > had > > > > "stolen" from aprs, so testing capability is fairly limited. From > what I > > > > can tell, though, it's nice and stable. > > > > > > > > I do have a few questions about the source ( yeah, always one in the > crowd > > > > :-) ) > > > > > > > > - In dlm.c noticed references to "curl-multi" and evidently the > capability > > > > to leverage parallel downloading of map tiles as supported by > libcurl. Is > > > > whether or not that is supported in our platform based on what > version of > > > > curl is installed? > > > > > > > > - now that dlm.c handles downloading tiles, is there anything left in > > > > tile_mgmnt.c that is still needed or could tile_mgmnt.h and > tile_mgmnt.c be > > > > removed? It seems at a minimum the "getOneTile" portion of > tile_mgmnt.c is > > > > no longer needed. > > > > > > > > Looks like you guys are doing a lot of cleanup in this release, so > brought > > > > that up just in case there's some stuff there that could be > streamlined a > > > > bit. > > > > > > > > Fyi, my Odroid XU4 (arm based) beats the pants off my Intel Celeron > based > > > > laptop in terms of map download speed. Both are on Ubuntu 18.04 > with the > > > > MATE desktop. Am wondering if the fact that the XU4 has an octa-core > cpu > > > > makes a difference with respect to curl-multi. > > > > > > > > The cleaner compiling is very noticeable, and the earlier note about > newer > > > > compilers spitting out more warnings matches what I saw. Compiling > is > > > > cleaner in Debian Stretch and Ubuntu 16.04 than it is in Ubuntu > 18.04, but > > > > it still builds fine. (And even in Ubuntu 18.04 the new code still > > > > compiles a lot cleaner that the older code did) > > > > > > > > Thanks, > > > > > > > > Lee > > > > K5DAT > > > > > > > > > > > > On Thu, May 9, 2019 at 9:57 AM Curt Mills > wrote: > > > > > > > > > We're planning to do a release within a few weeks. It might be as > few as > > > > 2 > > > > > weeks. > > > > > > > > > > Please check out / compile / thrash on t
Re: [Xastir] ATTENTION: Preparing for next release: Please thrash on the code
Totally your choice. The sooner the better as far as I'm concerned, unless bugs turn up between now and then. On Thu, May 23, 2019 at 12:06 PM Tom Russo wrote: > On Thu, May 23, 2019 at 07:15:52AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > Anyone else have any reports, good or bad? > > > > FWIW: For the types of things I do the latest code has been stable for > me. > > > > We're getting close to a release and Tom will most likely be the one > doing > > it. No target date has been mentioned. If we run into any nasty bugs that > > might delay. > > Let's set a date right now. I can set aside the time to do the release > on only a few days in the upcoming weeks (it doesn't take long, but it's > a process that takes some attention, and is documented in > README.developers.md). > > The days I could do it are: > Friday, 31 May > Friday, 14 June > Sometime on the weekend of 21-23 June. > > I think that we are already at a point where there has been sufficient time > to shake out the code on master, and we could release today if we wanted > to. Next friday is the earliest I have the opportunity to spend on it. > > If someone else wanted to try out the release process, it's all documented > in gory detail in README.developers.md, and if followed precisely would > produce a new release that would be ready (down to file names of tarballs) > to slot into the package creation processes various distros use, just by > changing the version number. Or pick a date and I'll do it then. > > > On Fri, May 17, 2019 at 6:16 PM Lee Bengston > wrote: > > > > > I've played with it some and and have not found any issues. I put > together > > > a BPQ packet node in January, and I haven't fully back-filled what I > had > > > "stolen" from aprs, so testing capability is fairly limited. From > what I > > > can tell, though, it's nice and stable. > > > > > > I do have a few questions about the source ( yeah, always one in the > crowd > > > :-) ) > > > > > > - In dlm.c noticed references to "curl-multi" and evidently the > capability > > > to leverage parallel downloading of map tiles as supported by libcurl. > Is > > > whether or not that is supported in our platform based on what version > of > > > curl is installed? > > > > > > - now that dlm.c handles downloading tiles, is there anything left in > > > tile_mgmnt.c that is still needed or could tile_mgmnt.h and > tile_mgmnt.c be > > > removed? It seems at a minimum the "getOneTile" portion of > tile_mgmnt.c is > > > no longer needed. > > > > > > Looks like you guys are doing a lot of cleanup in this release, so > brought > > > that up just in case there's some stuff there that could be > streamlined a > > > bit. > > > > > > Fyi, my Odroid XU4 (arm based) beats the pants off my Intel Celeron > based > > > laptop in terms of map download speed. Both are on Ubuntu 18.04 with > the > > > MATE desktop. Am wondering if the fact that the XU4 has an octa-core > cpu > > > makes a difference with respect to curl-multi. > > > > > > The cleaner compiling is very noticeable, and the earlier note about > newer > > > compilers spitting out more warnings matches what I saw. Compiling is > > > cleaner in Debian Stretch and Ubuntu 16.04 than it is in Ubuntu 18.04, > but > > > it still builds fine. (And even in Ubuntu 18.04 the new code still > > > compiles a lot cleaner that the older code did) > > > > > > Thanks, > > > > > > Lee > > > K5DAT > > > > > > > > > On Thu, May 9, 2019 at 9:57 AM Curt Mills wrote: > > > > > > > We're planning to do a release within a few weeks. It might be as > few as > > > 2 > > > > weeks. > > > > > > > > Please check out / compile / thrash on the latest Github Xastir code. > > > Find > > > > anything that broke with our latest code fixes. Exercise all types of > > > > interfaces, messaging, bulletins, weather stations, tracking, > following > > > > stations, maps, etc. Anything you can think of. > > > > > > > > The latest code compiles much cleaner and a lot of fixes went in to > make > > > > that possible. We'd like this release to function well, so whatever > you > > > can > > > > do to exercise the code would be most appreciated. > > > > > > > > If you
Re: [Xastir-dev] [Xastir] ATTENTION: Preparing for next release: Please thrash on the code
Totally your choice. The sooner the better as far as I'm concerned, unless bugs turn up between now and then. On Thu, May 23, 2019 at 12:06 PM Tom Russo wrote: > On Thu, May 23, 2019 at 07:15:52AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > Anyone else have any reports, good or bad? > > > > FWIW: For the types of things I do the latest code has been stable for > me. > > > > We're getting close to a release and Tom will most likely be the one > doing > > it. No target date has been mentioned. If we run into any nasty bugs that > > might delay. > > Let's set a date right now. I can set aside the time to do the release > on only a few days in the upcoming weeks (it doesn't take long, but it's > a process that takes some attention, and is documented in > README.developers.md). > > The days I could do it are: > Friday, 31 May > Friday, 14 June > Sometime on the weekend of 21-23 June. > > I think that we are already at a point where there has been sufficient time > to shake out the code on master, and we could release today if we wanted > to. Next friday is the earliest I have the opportunity to spend on it. > > If someone else wanted to try out the release process, it's all documented > in gory detail in README.developers.md, and if followed precisely would > produce a new release that would be ready (down to file names of tarballs) > to slot into the package creation processes various distros use, just by > changing the version number. Or pick a date and I'll do it then. > > > On Fri, May 17, 2019 at 6:16 PM Lee Bengston > wrote: > > > > > I've played with it some and and have not found any issues. I put > together > > > a BPQ packet node in January, and I haven't fully back-filled what I > had > > > "stolen" from aprs, so testing capability is fairly limited. From > what I > > > can tell, though, it's nice and stable. > > > > > > I do have a few questions about the source ( yeah, always one in the > crowd > > > :-) ) > > > > > > - In dlm.c noticed references to "curl-multi" and evidently the > capability > > > to leverage parallel downloading of map tiles as supported by libcurl. > Is > > > whether or not that is supported in our platform based on what version > of > > > curl is installed? > > > > > > - now that dlm.c handles downloading tiles, is there anything left in > > > tile_mgmnt.c that is still needed or could tile_mgmnt.h and > tile_mgmnt.c be > > > removed? It seems at a minimum the "getOneTile" portion of > tile_mgmnt.c is > > > no longer needed. > > > > > > Looks like you guys are doing a lot of cleanup in this release, so > brought > > > that up just in case there's some stuff there that could be > streamlined a > > > bit. > > > > > > Fyi, my Odroid XU4 (arm based) beats the pants off my Intel Celeron > based > > > laptop in terms of map download speed. Both are on Ubuntu 18.04 with > the > > > MATE desktop. Am wondering if the fact that the XU4 has an octa-core > cpu > > > makes a difference with respect to curl-multi. > > > > > > The cleaner compiling is very noticeable, and the earlier note about > newer > > > compilers spitting out more warnings matches what I saw. Compiling is > > > cleaner in Debian Stretch and Ubuntu 16.04 than it is in Ubuntu 18.04, > but > > > it still builds fine. (And even in Ubuntu 18.04 the new code still > > > compiles a lot cleaner that the older code did) > > > > > > Thanks, > > > > > > Lee > > > K5DAT > > > > > > > > > On Thu, May 9, 2019 at 9:57 AM Curt Mills wrote: > > > > > > > We're planning to do a release within a few weeks. It might be as > few as > > > 2 > > > > weeks. > > > > > > > > Please check out / compile / thrash on the latest Github Xastir code. > > > Find > > > > anything that broke with our latest code fixes. Exercise all types of > > > > interfaces, messaging, bulletins, weather stations, tracking, > following > > > > stations, maps, etc. Anything you can think of. > > > > > > > > The latest code compiles much cleaner and a lot of fixes went in to > make > > > > that possible. We'd like this release to function well, so whatever > you > > > can > > > > do to exercise the code would be most appreciated. > > > > > > > > If you
Re: [Xastir] ATTENTION: Preparing for next release: Please thrash on the code
Anyone else have any reports, good or bad? FWIW: For the types of things I do the latest code has been stable for me. We're getting close to a release and Tom will most likely be the one doing it. No target date has been mentioned. If we run into any nasty bugs that might delay. On Fri, May 17, 2019 at 6:16 PM Lee Bengston wrote: > I've played with it some and and have not found any issues. I put together > a BPQ packet node in January, and I haven't fully back-filled what I had > "stolen" from aprs, so testing capability is fairly limited. From what I > can tell, though, it's nice and stable. > > I do have a few questions about the source ( yeah, always one in the crowd > :-) ) > > - In dlm.c noticed references to "curl-multi" and evidently the capability > to leverage parallel downloading of map tiles as supported by libcurl. Is > whether or not that is supported in our platform based on what version of > curl is installed? > > - now that dlm.c handles downloading tiles, is there anything left in > tile_mgmnt.c that is still needed or could tile_mgmnt.h and tile_mgmnt.c be > removed? It seems at a minimum the "getOneTile" portion of tile_mgmnt.c is > no longer needed. > > Looks like you guys are doing a lot of cleanup in this release, so brought > that up just in case there's some stuff there that could be streamlined a > bit. > > Fyi, my Odroid XU4 (arm based) beats the pants off my Intel Celeron based > laptop in terms of map download speed. Both are on Ubuntu 18.04 with the > MATE desktop. Am wondering if the fact that the XU4 has an octa-core cpu > makes a difference with respect to curl-multi. > > The cleaner compiling is very noticeable, and the earlier note about newer > compilers spitting out more warnings matches what I saw. Compiling is > cleaner in Debian Stretch and Ubuntu 16.04 than it is in Ubuntu 18.04, but > it still builds fine. (And even in Ubuntu 18.04 the new code still > compiles a lot cleaner that the older code did) > > Thanks, > > Lee > K5DAT > > > On Thu, May 9, 2019 at 9:57 AM Curt Mills wrote: > > > We're planning to do a release within a few weeks. It might be as few as > 2 > > weeks. > > > > Please check out / compile / thrash on the latest Github Xastir code. > Find > > anything that broke with our latest code fixes. Exercise all types of > > interfaces, messaging, bulletins, weather stations, tracking, following > > stations, maps, etc. Anything you can think of. > > > > The latest code compiles much cleaner and a lot of fixes went in to make > > that possible. We'd like this release to function well, so whatever you > can > > do to exercise the code would be most appreciated. > > > > If you find a bug or odd operation, report it here: > > > > https://github.com/Xastir/Xastir/issues > > > > Thanks! > > > > -- > > Curt, WE7Uhttp://we7u.wetnet.net > > http://www.sarguydigital.com > > ___ > > Xastir mailing list > > Xastir@lists.xastir.org > > http://xastir.org/mailman/listinfo/xastir > > > ___ > Xastir mailing list > Xastir@lists.xastir.org > http://xastir.org/mailman/listinfo/xastir > -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
