Re: [Xastir] A few changes
On Wed, May 8, 2019, 12:18 PM Tom Russo wrote: > On Wed, May 08, 2019 at 11:17:49AM -0500, we recorded a bogon-computron > collision of the flavor, containing: > > On Tue, May 7, 2019 at 10:33 PM Tom Russo wrote: > > > > > On Tue, May 07, 2019 at 10:20:12PM -0500, we recorded a bogon-computron > > > collision of the flavor, containing: > > > > A little late to this thread, sorry. Did a clean install on a > relatively > > > > new Odroid XU4 on Ubuntu 18.04. Seems to be fine, and no error > messages > > > in > > > > the terminal. "Help About" gave me the detailed release number as > > > expected. > > > > > > > > Noticed the Nationalmap.gov onine maps are still broken. I have > some new > > > > nationalmap.gov geos I can share that do work - no code changes > > > required - > > > > just new geo files with updated WMS links. Will follow up with those > > > given > > > > they can't be attached to messages on this list. > > > > > > If you could do it via a pull request it will be easier to handle than > > > by posting on the mailing list. It'd be great to update the borken > > > geos. > > > > > > Pull request completed. > > No, you opened a pull request and then closed it before we did anything > with > it. Made it look like you changed your mind about it. If you go ahead > and reopen the pull request we can check it out and then merge it. > Ok, first one I've ever done. By closing it I thought that just meant I was done adding the comment. It has been reopened. Thanks, Lee > ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] A few changes
On Wed, May 08, 2019 at 11:17:49AM -0500, we recorded a bogon-computron collision of the flavor, containing: > On Tue, May 7, 2019 at 10:33 PM Tom Russo wrote: > > > On Tue, May 07, 2019 at 10:20:12PM -0500, we recorded a bogon-computron > > collision of the flavor, containing: > > > A little late to this thread, sorry. Did a clean install on a relatively > > > new Odroid XU4 on Ubuntu 18.04. Seems to be fine, and no error messages > > in > > > the terminal. "Help About" gave me the detailed release number as > > expected. > > > > > > Noticed the Nationalmap.gov onine maps are still broken. I have some new > > > nationalmap.gov geos I can share that do work - no code changes > > required - > > > just new geo files with updated WMS links. Will follow up with those > > given > > > they can't be attached to messages on this list. > > > > If you could do it via a pull request it will be easier to handle than > > by posting on the mailing list. It'd be great to update the borken > > geos. > > > Pull request completed. No, you opened a pull request and then closed it before we did anything with it. Made it look like you changed your mind about it. If you go ahead and reopen the pull request we can check it out and then merge it. -- 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
Re: [Xastir] A few changes
On Tue, May 7, 2019 at 10:33 PM Tom Russo wrote: > On Tue, May 07, 2019 at 10:20:12PM -0500, we recorded a bogon-computron > collision of the flavor, containing: > > A little late to this thread, sorry. Did a clean install on a relatively > > new Odroid XU4 on Ubuntu 18.04. Seems to be fine, and no error messages > in > > the terminal. "Help About" gave me the detailed release number as > expected. > > > > Noticed the Nationalmap.gov onine maps are still broken. I have some new > > nationalmap.gov geos I can share that do work - no code changes > required - > > just new geo files with updated WMS links. Will follow up with those > given > > they can't be attached to messages on this list. > > If you could do it via a pull request it will be easier to handle than > by posting on the mailing list. It'd be great to update the borken > geos. Pull request completed. Lee K5DAT Near Portage, WI ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] A few changes
On Tue, May 7, 2019 at 10:33 PM Tom Russo wrote: > On Tue, May 07, 2019 at 10:20:12PM -0500, we recorded a bogon-computron > collision of the flavor, containing: > > A little late to this thread, sorry. Did a clean install on a relatively > > new Odroid XU4 on Ubuntu 18.04. Seems to be fine, and no error messages > in > > the terminal. "Help About" gave me the detailed release number as > expected. > > > > Noticed the Nationalmap.gov onine maps are still broken. I have some new > > nationalmap.gov geos I can share that do work - no code changes > required - > > just new geo files with updated WMS links. Will follow up with those > given > > they can't be attached to messages on this list. > > If you could do it via a pull request it will be easier to handle than > by posting on the mailing list. It'd be great to update the borken > geos. > > Will look at that tomorrow. Didn't catch up to this message until after I > sent the one with the link to the zip file. In the meantime people can try > out the geo files... Lee ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] A few changes
A little late to this thread, sorry. Did a clean install on a relatively new Odroid XU4 on Ubuntu 18.04. Seems to be fine, and no error messages in the terminal. "Help About" gave me the detailed release number as expected. Noticed the Nationalmap.gov onine maps are still broken. I have some new nationalmap.gov geos I can share that do work - no code changes required - just new geo files with updated WMS links. Will follow up with those given they can't be attached to messages on this list. Lee K5DAT > > ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] A few changes
On Sat, May 04, 2019 at 06:12:44PM -0600, we recorded a bogon-computron collision of the flavor, containing: > On Sat, May 04, 2019 at 07:09:28PM -0500, we recorded a bogon-computron > collision of the flavor, containing: > > I didn???t read Curt???s email closely enough (a number LIKE > > indicating git version) so I did it twice on my pi, once with the update > > script and once with a new clean clone. Both worked. I was confused at > > first until I realized it was compiling fine, I just wasn???t seeing > > warnings. :| > > > > When making librtree.a there???s a message from ar > > > > ar: ???u??? modifier ignored since ???D??? is the default (see ???U???) > > Well know issue with GNU automake and libtool. Been a problem for ages > and they haven't fixed it yet. > > Google "automake ar modifier ignored" and you'll see tons of packages > complaining about it. > > > But About tells me I have rtree support and librtree.a exists so its > > apparently informational. > > Just ignore it. Sometime in the next 10 years they'll get it fixed. BTW, there are tons of suggestions for workarounds such as replacing AR_FLAGS with "cr" to override the default "cru", but I have tried all of them out and none actually silences this warning. This is one we just have to ignore just as almost everyone else that uses automake has to. > > > On Apr 30, 2019, at 9:58 AM, Curt Mills wrote: > > > > > > 1) After updating from Git you'll see a new message in the configure > > > summary: > > > > > >RECOMMENDED OPTIONS: > > > Xpm / Snapshots ... : yes > > > > > > If you have libxpm and libxpm-dev packages installed (the names of the > > > packages may vary on your system) then you'll see a "yes" there. That > > > enables the Snapshot facility in Xastir. That was somewhat hidden before, > > > perhaps only greying-out the button in the menus if it wasn't present > > > during configure/compile. > > > > > > 2) In the Help->About dialog you'll see at the very top something like: > > > > > >Xastir V2.1.1 (cf75dd5a) > > > > > > That last number is the 8-digit short-form version of the most recent Git > > > commit. That tells you _exactly_ which code is in your compile. > > > > > > 3) You may notice an absence or a severe reduction in compile warnings. > > > This is a result of multiple people working over the last 1.5 weeks on > > > this > > > particular issue (Issue #24). We still have a few warnings related to > > > geotiff / graphicsmagick / imagemagick: These appear to be problems in > > > their headers, not our code. With a very new GCC compiler (7 or 8?) you > > > may > > > also see a bunch of messages about snprintf but there exist some compiler > > > flags which will quiet those: We're using them in one of our Travis-CI > > > configs to do just that. > > > > > > 4) While working on #3 above we found some real bugs and worked to fix > > > them > > > or in some cases add them to our bug list. > > > > > > 5) Travis-CI is building Xastir every time there is a commit or a pull > > > request. It currently builds on three Ubuntu-16.04 systems and one OSX > > > 10.13.3 system and feeds back warnings/errors to us. You can see this at: > > > https://travis-ci.org/Xastir/Xastir > > > Thanks to Jason Godfrey for setting this up. We're worked quite a bit on > > > the configuration in the last week to make it do what we want. > > > > > > 6) The project is currently at zero pull requests and only a few > > > outstanding bugs. > > > https://github.com/Xastir/Xastir > > > > > > -- > > > 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 > > -- > 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
Re: [Xastir] A few changes
On Sat, May 04, 2019 at 07:09:28PM -0500, we recorded a bogon-computron collision of the flavor, containing: > I didn???t read Curt???s email closely enough (a number LIKE indicating > git version) so I did it twice on my pi, once with the update script and once > with a new clean clone. Both worked. I was confused at first until I realized > it was compiling fine, I just wasn???t seeing warnings. :| > > When making librtree.a there???s a message from ar > > ar: ???u??? modifier ignored since ???D??? is the default (see ???U???) Well know issue with GNU automake and libtool. Been a problem for ages and they haven't fixed it yet. Google "automake ar modifier ignored" and you'll see tons of packages complaining about it. > But About tells me I have rtree support and librtree.a exists so its > apparently informational. Just ignore it. Sometime in the next 10 years they'll get it fixed. > > On Apr 30, 2019, at 9:58 AM, Curt Mills wrote: > > > > 1) After updating from Git you'll see a new message in the configure > > summary: > > > >RECOMMENDED OPTIONS: > > Xpm / Snapshots ... : yes > > > > If you have libxpm and libxpm-dev packages installed (the names of the > > packages may vary on your system) then you'll see a "yes" there. That > > enables the Snapshot facility in Xastir. That was somewhat hidden before, > > perhaps only greying-out the button in the menus if it wasn't present > > during configure/compile. > > > > 2) In the Help->About dialog you'll see at the very top something like: > > > >Xastir V2.1.1 (cf75dd5a) > > > > That last number is the 8-digit short-form version of the most recent Git > > commit. That tells you _exactly_ which code is in your compile. > > > > 3) You may notice an absence or a severe reduction in compile warnings. > > This is a result of multiple people working over the last 1.5 weeks on this > > particular issue (Issue #24). We still have a few warnings related to > > geotiff / graphicsmagick / imagemagick: These appear to be problems in > > their headers, not our code. With a very new GCC compiler (7 or 8?) you may > > also see a bunch of messages about snprintf but there exist some compiler > > flags which will quiet those: We're using them in one of our Travis-CI > > configs to do just that. > > > > 4) While working on #3 above we found some real bugs and worked to fix them > > or in some cases add them to our bug list. > > > > 5) Travis-CI is building Xastir every time there is a commit or a pull > > request. It currently builds on three Ubuntu-16.04 systems and one OSX > > 10.13.3 system and feeds back warnings/errors to us. You can see this at: > > https://travis-ci.org/Xastir/Xastir > > Thanks to Jason Godfrey for setting this up. We're worked quite a bit on > > the configuration in the last week to make it do what we want. > > > > 6) The project is currently at zero pull requests and only a few > > outstanding bugs. > > https://github.com/Xastir/Xastir > > > > -- > > Curt, WE7Uhttp://we7u.wetnet.nethttp://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 -- 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
Re: [Xastir] A few changes
I didn’t read Curt’s email closely enough (a number LIKE indicating git version) so I did it twice on my pi, once with the update script and once with a new clean clone. Both worked. I was confused at first until I realized it was compiling fine, I just wasn’t seeing warnings. :| When making librtree.a there’s a message from ar ar: ‘u’ modifier ignored since ‘D’ is the default (see ‘U’) But About tells me I have rtree support and librtree.a exists so its apparently informational. Thanks guys! -Jason > On Apr 30, 2019, at 9:58 AM, Curt Mills wrote: > > 1) After updating from Git you'll see a new message in the configure > summary: > >RECOMMENDED OPTIONS: > Xpm / Snapshots ... : yes > > If you have libxpm and libxpm-dev packages installed (the names of the > packages may vary on your system) then you'll see a "yes" there. That > enables the Snapshot facility in Xastir. That was somewhat hidden before, > perhaps only greying-out the button in the menus if it wasn't present > during configure/compile. > > 2) In the Help->About dialog you'll see at the very top something like: > >Xastir V2.1.1 (cf75dd5a) > > That last number is the 8-digit short-form version of the most recent Git > commit. That tells you _exactly_ which code is in your compile. > > 3) You may notice an absence or a severe reduction in compile warnings. > This is a result of multiple people working over the last 1.5 weeks on this > particular issue (Issue #24). We still have a few warnings related to > geotiff / graphicsmagick / imagemagick: These appear to be problems in > their headers, not our code. With a very new GCC compiler (7 or 8?) you may > also see a bunch of messages about snprintf but there exist some compiler > flags which will quiet those: We're using them in one of our Travis-CI > configs to do just that. > > 4) While working on #3 above we found some real bugs and worked to fix them > or in some cases add them to our bug list. > > 5) Travis-CI is building Xastir every time there is a commit or a pull > request. It currently builds on three Ubuntu-16.04 systems and one OSX > 10.13.3 system and feeds back warnings/errors to us. You can see this at: > https://travis-ci.org/Xastir/Xastir > Thanks to Jason Godfrey for setting this up. We're worked quite a bit on > the configuration in the last week to make it do what we want. > > 6) The project is currently at zero pull requests and only a few > outstanding bugs. > https://github.com/Xastir/Xastir > > -- > Curt, WE7Uhttp://we7u.wetnet.nethttp://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
Re: [Xastir] A few changes
On Sat, May 04, 2019 at 01:22:37PM -0700, we recorded a bogon-computron collision of the flavor, containing: > > Hey Tom, > > > The list does not accept attachments. > > So I noticed... bummer. > > > > > If you're not getting the git SHA in the about box, there may be > > something up with how you're building Xastir. Are you building from sources > > out of a git clone, or are you downloading a zip file from the > > github web interface? > > git clone > > > What does "git log --pretty=format:%h -1" show when you're in the source > > directory? > > Ok.. I think I know what's going on here. I'm using the git clone data > but I'm packaging things into an RPM and in that process, I tar up the > sources but I strip out the .git stuff as it's all bloat): > > tar czvf > /usr/src/redhat/SOURCES/xastir-2.1.1git-20190501gitaf3d59d9.tgz > xastir-2.1.1git/* --exclude xastir-2.1.1git/.git Yeah, there's why. Don't do that for this experiment. Just build out of the source tree for now, then go back to packaging your RPM as you see fit. -- 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
Re: [Xastir] A few changes
Hey Tom, The list does not accept attachments. So I noticed... bummer. If you're not getting the git SHA in the about box, there may be something up with how you're building Xastir. Are you building from sources out of a git clone, or are you downloading a zip file from the github web interface? git clone What does "git log --pretty=format:%h -1" show when you're in the source directory? Ok.. I think I know what's going on here. I'm using the git clone data but I'm packaging things into an RPM and in that process, I tar up the sources but I strip out the .git stuff as it's all bloat): tar czvf /usr/src/redhat/SOURCES/xastir-2.1.1git-20190501gitaf3d59d9.tgz xastir-2.1.1git/* --exclude xastir-2.1.1git/.git Would it be enough to just keep: .git/logs/HEAD to make this all work? 1.b Shows they year 2018 Is this just in the copyright date? That's hard coded and needs updating before we release, but doesn't help determine what version's actually running. Yes.. and seems it should be updated. :-) A graceless exit will still cause stray Xastir processes -- -but they should no longer cause double windows on startup. You still have to kill them by hand. Ok.. I'll test that. What would be the best way to kill Xastir to reproduce this. Will using the "kill " be enough or should I send a specific signal? Good news, but we should confirm that you're actually testing exactly the current code, which is hard to do if the git SHA-1 doesn't show up in your about box. Agreed though I'm pretty sure I'm testing the right code as I package EVERYTHING. --David KI6ZHD ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] A few changes
On Sat, May 04, 2019 at 12:28:42PM -0700, we recorded a bogon-computron collision of the flavor, containing: > > I've build and installed the Git master branch (5/1/19) here on Centos > 6.10 and it seems to be running ok but a few things: > > 1. In the Help --> About window, > >1.a it's NOT showing the Git version as this thread talks about > (attaching a screen capture to this email - let's see if it makes it) The list does not accept attachments. If you're not getting the git SHA in the about box, there may be something up with how you're building Xastir. Are you building from sources out of a git clone, or are you downloading a zip file from the github web interface? The SHA will only show up if you're building out of a clone. What does "git log --pretty=format:%h -1" show when you're in the source directory? >1.b Shows they year 2018 Is this just in the copyright date? That's hard coded and needs updating before we release, but doesn't help determine what version's actually running. > 2. No errors are showing from STDOUT upon start or graceful exit > > 3. No stray Xastir processes found upon graceful exit A graceless exit will still cause stray Xastir processes -- -but they should no longer cause double windows on startup. You still have to kill them by hand. > So far, the zoom in/out and panning is working fine. Good news, but we should confirm that you're actually testing exactly the current code, which is hard to do if the git SHA-1 doesn't show up in your about box. > On 04/30/2019 08:23 AM, km5vy Tom Russo wrote: > > On Tue, Apr 30, 2019 at 08:09:21AM -0700, we recorded a bogon-computron > > collision of the flavor, containing: > >> Yes on the NWS script being up-to-date. With all the places the code has > >> been tweaked recently I'd like to see the dust settle for a few weeks. Give > >> us time to test out all the different types of maps. I'd like to see > >> messaging tested as well. Having a bunch of users pound on it is probably > >> the best method because everybody uses Xastir in different ways. > > > > Yeah, we should probably be considering the current state of master as a > > release candidate, and anyone who can possibly pull it down, build it, and > > feed back any new bugs should do so. > > > > My point, though, is that we should probably be slowing down on these tweaks > > (we've really done a ton of work in the last couple of weeks), and when the > > dust settles and we get some confirmation that there's no new breakagee, > > we should call it 2.1.2 without further ado. > > > >> On Tue, Apr 30, 2019 at 8:04 AM Tom Russo wrote: > >> > >>> On Tue, Apr 30, 2019 at 07:58:26AM -0700, we recorded a bogon-computron > >>> collision of the flavor, containing: > 2) In the Help->About dialog you'll see at the very top something like: > > Xastir V2.1.1 (cf75dd5a) > > That last number is the 8-digit short-form version of the most recent Git > commit. That tells you _exactly_ which code is in your compile. > >>> This is not a recent change. It's been happening since August 2017. It > >>> is > >>> automatically enabled if you're building the code from a git clone instead > >>> of a tarball. > >>> > 6) The project is currently at zero pull requests and only a few > outstanding bugs. > https://github.com/Xastir/Xastir > >>> I'd say that once we get some feedback about whether bug #66 is still a > >>> problem (Xastir crashing when zooming in and out with OSM maps enabled), > >>> we're probably ready to start kicking release 2.1.2 out of the nest. Are > >>> the > >>> NWS and other download scripts up to date? For 2.1.0, NWS changed the > >>> download > >>> site really soon after the release, so perhaps this is always going to be > >>> a moving target. > >>> > >>> -- > >>> 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
Re: [Xastir] A few changes
I've build and installed the Git master branch (5/1/19) here on Centos 6.10 and it seems to be running ok but a few things: 1. In the Help --> About window, 1.a it's NOT showing the Git version as this thread talks about (attaching a screen capture to this email - let's see if it makes it) 1.b Shows they year 2018 2. No errors are showing from STDOUT upon start or graceful exit 3. No stray Xastir processes found upon graceful exit So far, the zoom in/out and panning is working fine. --David KI6ZHD On 04/30/2019 08:23 AM, km5vy Tom Russo wrote: On Tue, Apr 30, 2019 at 08:09:21AM -0700, we recorded a bogon-computron collision of the flavor, containing: Yes on the NWS script being up-to-date. With all the places the code has been tweaked recently I'd like to see the dust settle for a few weeks. Give us time to test out all the different types of maps. I'd like to see messaging tested as well. Having a bunch of users pound on it is probably the best method because everybody uses Xastir in different ways. Yeah, we should probably be considering the current state of master as a release candidate, and anyone who can possibly pull it down, build it, and feed back any new bugs should do so. My point, though, is that we should probably be slowing down on these tweaks (we've really done a ton of work in the last couple of weeks), and when the dust settles and we get some confirmation that there's no new breakagee, we should call it 2.1.2 without further ado. On Tue, Apr 30, 2019 at 8:04 AM Tom Russo wrote: On Tue, Apr 30, 2019 at 07:58:26AM -0700, we recorded a bogon-computron collision of the flavor, containing: 2) In the Help->About dialog you'll see at the very top something like: Xastir V2.1.1 (cf75dd5a) That last number is the 8-digit short-form version of the most recent Git commit. That tells you _exactly_ which code is in your compile. This is not a recent change. It's been happening since August 2017. It is automatically enabled if you're building the code from a git clone instead of a tarball. 6) The project is currently at zero pull requests and only a few outstanding bugs. https://github.com/Xastir/Xastir I'd say that once we get some feedback about whether bug #66 is still a problem (Xastir crashing when zooming in and out with OSM maps enabled), we're probably ready to start kicking release 2.1.2 out of the nest. Are the NWS and other download scripts up to date? For 2.1.0, NWS changed the download site really soon after the release, so perhaps this is always going to be a moving target. -- 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
Re: [Xastir] A few changes
On Tue, Apr 30, 2019 at 8:23 AM km5vy Tom Russo wrote: > > Yeah, we should probably be considering the current state of master as a > release candidate, and anyone who can possibly pull it down, build it, and > feed back any new bugs should do so. > > My point, though, is that we should probably be slowing down on these > tweaks > (we've really done a ton of work in the last couple of weeks), and when the > dust settles and we get some confirmation that there's no new breakagee, > we should call it 2.1.2 without further ado. > Agreed. -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] A few changes
On Tue, Apr 30, 2019 at 08:09:21AM -0700, we recorded a bogon-computron collision of the flavor, containing: > Yes on the NWS script being up-to-date. With all the places the code has > been tweaked recently I'd like to see the dust settle for a few weeks. Give > us time to test out all the different types of maps. I'd like to see > messaging tested as well. Having a bunch of users pound on it is probably > the best method because everybody uses Xastir in different ways. Yeah, we should probably be considering the current state of master as a release candidate, and anyone who can possibly pull it down, build it, and feed back any new bugs should do so. My point, though, is that we should probably be slowing down on these tweaks (we've really done a ton of work in the last couple of weeks), and when the dust settles and we get some confirmation that there's no new breakagee, we should call it 2.1.2 without further ado. > On Tue, Apr 30, 2019 at 8:04 AM Tom Russo wrote: > > > On Tue, Apr 30, 2019 at 07:58:26AM -0700, we recorded a bogon-computron > > collision of the flavor, containing: > > > > > > 2) In the Help->About dialog you'll see at the very top something like: > > > > > > Xastir V2.1.1 (cf75dd5a) > > > > > > That last number is the 8-digit short-form version of the most recent Git > > > commit. That tells you _exactly_ which code is in your compile. > > > > This is not a recent change. It's been happening since August 2017. It is > > automatically enabled if you're building the code from a git clone instead > > of a tarball. > > > > > 6) The project is currently at zero pull requests and only a few > > > outstanding bugs. > > > https://github.com/Xastir/Xastir > > > > I'd say that once we get some feedback about whether bug #66 is still a > > problem (Xastir crashing when zooming in and out with OSM maps enabled), > > we're probably ready to start kicking release 2.1.2 out of the nest. Are > > the > > NWS and other download scripts up to date? For 2.1.0, NWS changed the > > download > > site really soon after the release, so perhaps this is always going to be > > a moving target. > > > > -- > > 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] ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
Re: [Xastir] A few changes
Yes on the NWS script being up-to-date. With all the places the code has been tweaked recently I'd like to see the dust settle for a few weeks. Give us time to test out all the different types of maps. I'd like to see messaging tested as well. Having a bunch of users pound on it is probably the best method because everybody uses Xastir in different ways. On Tue, Apr 30, 2019 at 8:04 AM Tom Russo wrote: > On Tue, Apr 30, 2019 at 07:58:26AM -0700, we recorded a bogon-computron > collision of the flavor, containing: > > > > 2) In the Help->About dialog you'll see at the very top something like: > > > > Xastir V2.1.1 (cf75dd5a) > > > > That last number is the 8-digit short-form version of the most recent Git > > commit. That tells you _exactly_ which code is in your compile. > > This is not a recent change. It's been happening since August 2017. It is > automatically enabled if you're building the code from a git clone instead > of a tarball. > > > 6) The project is currently at zero pull requests and only a few > > outstanding bugs. > > https://github.com/Xastir/Xastir > > I'd say that once we get some feedback about whether bug #66 is still a > problem (Xastir crashing when zooming in and out with OSM maps enabled), > we're probably ready to start kicking release 2.1.2 out of the nest. Are > the > NWS and other download scripts up to date? For 2.1.0, NWS changed the > download > site really soon after the release, so perhaps this is always going to be > a moving target. > > -- > 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] A few changes
On Tue, Apr 30, 2019 at 07:58:26AM -0700, we recorded a bogon-computron collision of the flavor, containing: > > 2) In the Help->About dialog you'll see at the very top something like: > > Xastir V2.1.1 (cf75dd5a) > > That last number is the 8-digit short-form version of the most recent Git > commit. That tells you _exactly_ which code is in your compile. This is not a recent change. It's been happening since August 2017. It is automatically enabled if you're building the code from a git clone instead of a tarball. > 6) The project is currently at zero pull requests and only a few > outstanding bugs. > https://github.com/Xastir/Xastir I'd say that once we get some feedback about whether bug #66 is still a problem (Xastir crashing when zooming in and out with OSM maps enabled), we're probably ready to start kicking release 2.1.2 out of the nest. Are the NWS and other download scripts up to date? For 2.1.0, NWS changed the download site really soon after the release, so perhaps this is always going to be a moving target. -- 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] A few changes
1) After updating from Git you'll see a new message in the configure summary: RECOMMENDED OPTIONS: Xpm / Snapshots ... : yes If you have libxpm and libxpm-dev packages installed (the names of the packages may vary on your system) then you'll see a "yes" there. That enables the Snapshot facility in Xastir. That was somewhat hidden before, perhaps only greying-out the button in the menus if it wasn't present during configure/compile. 2) In the Help->About dialog you'll see at the very top something like: Xastir V2.1.1 (cf75dd5a) That last number is the 8-digit short-form version of the most recent Git commit. That tells you _exactly_ which code is in your compile. 3) You may notice an absence or a severe reduction in compile warnings. This is a result of multiple people working over the last 1.5 weeks on this particular issue (Issue #24). We still have a few warnings related to geotiff / graphicsmagick / imagemagick: These appear to be problems in their headers, not our code. With a very new GCC compiler (7 or 8?) you may also see a bunch of messages about snprintf but there exist some compiler flags which will quiet those: We're using them in one of our Travis-CI configs to do just that. 4) While working on #3 above we found some real bugs and worked to fix them or in some cases add them to our bug list. 5) Travis-CI is building Xastir every time there is a commit or a pull request. It currently builds on three Ubuntu-16.04 systems and one OSX 10.13.3 system and feeds back warnings/errors to us. You can see this at: https://travis-ci.org/Xastir/Xastir Thanks to Jason Godfrey for setting this up. We're worked quite a bit on the configuration in the last week to make it do what we want. 6) The project is currently at zero pull requests and only a few outstanding bugs. https://github.com/Xastir/Xastir -- Curt, WE7Uhttp://we7u.wetnet.nethttp://www.sarguydigital.com ___ Xastir mailing list Xastir@lists.xastir.org http://xastir.org/mailman/listinfo/xastir
