Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

On Fri, Feb 09, 2018 at 01:50:57PM -0800, Curt, WE7U wrote: > On Fri, 9 Feb 2018, Tom Russo wrote: > > > Yesterday I checked and Xastir.org had an IPv6 address returned by DNS > > queries. > > Today it does not. Looks like Curt took care of this. > > Yep. Until I have time to figure out why

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

On Fri, 9 Feb 2018, Tom Russo wrote: Yesterday I checked and Xastir.org had an IPv6 address returned by DNS queries. Today it does not. Looks like Curt took care of this. Yep. Until I have time to figure out why routing to/fro on IPv6 doesn't work it seemed like the best option. -- Curt,

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

8, 2018 13:13 To: Xastir-dev - APRS client software developer's discussion <xastir-...@xastir.org> Subject: Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion On Thu, 8 Feb 2018, David Brooke G6GZH wrote: > With the mention of

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

Yesterday I checked and Xastir.org had an IPv6 address returned by DNS queries. Today it does not. Looks like Curt took care of this. Does it still seem slow? On Thu, Feb 08, 2018 at 06:39:11PM +, we recorded a bogon-computron collision of the flavor, containing: >

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

On Thu, Feb 08, 2018 at 10:12:34AM -0800, Curt, WE7U wrote: > > Is IPv6 truly needed? I guess that's a matter for debate; having used IPv6 for over 10 years I kind of regard it as standard but I'm not aware of many sites that don't also have IPv4. However the presence of an record in DNS

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

On Thu, 8 Feb 2018, David Brooke G6GZH wrote: With the mention of the wiki I was just having a look at it and it seemed slow - looks like IPv6 routing is broken from me at least traceroute to xastir.org (2001:1868:205::1001) from 2001:8b0:3d7:1:c9ac:a899:bdcb:1d59, 30 hops max, 24 byte

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

With the mention of the wiki I was just having a look at it and it seemed slow - looks like IPv6 routing is broken from me at least traceroute to xastir.org (2001:1868:205::1001) from 2001:8b0:3d7:1:c9ac:a899:bdcb:1d59, 30 hops max, 24 byte packets 1 rb-lan.dbrooke.me.uk (2001:8b0:3d7:1::1)

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

On Thu, 8 Feb 2018, Tom Russo wrote: If there is anyone who would like to take on tasks of wiki clean-up (it's pretty stale) and documentation proofreading, please jump on board. If anyone points out particular pages / sections of pages that need updating I can do some. If they contain

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

On Wed, 7 Feb 2018 11:52:48 -0700 Tom Russo wrote: > To test out the release mechanism on github, I've gone ahead and > created a "new" Xastir 2.0.8 release branch (branched from the > xastir208 tag that was used for the SourceForge stable release), > bootstrapped it, pushed it

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

On Thu, Feb 08, 2018 at 04:00:22PM +, we recorded a bogon-computron collision of the flavor, containing: > On Wed, Feb 07, 2018 at 11:52:48AM -0700, Tom Russo wrote: > > > > If you're a package maintainer for any OS, you might start looking into how > > you have to

Re: [Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

On Wed, Feb 07, 2018 at 11:52:48AM -0700, Tom Russo wrote: > > If you're a package maintainer for any OS, you might start looking into how > you have to change your package build process to access the Github release > tarballs instead of SourceForge. I've made the necessary changes for CRUX.

[Xastir-dev] New release coming up soon, old release "regenerated" on Github, call for discussion

I think I am days away from pushing out an Xastir 2.1.0 stable release, which will pretty much be exactly the code that's at the head of master right now. To test out the release mechanism on github, I've gone ahead and created a "new" Xastir 2.0.8 release branch (branched from the xastir208 tag