David Once the decision is made I need to know so I can nudge the correct people to start the ball rolling at the Debian level and also alert the Ubuntu folks to start watching Debian and have it auto-magically roll downhill into Ubuntu and the cousins (Mint, Puppy, Etc.). Someone else would need to do the same with the Fedora chain to keep the various worlds in sync.
The 2.0.6-5 package is in place to satiate the "Jasper Bug" that had Xastir on the "Debian Euthanasia list" as I saw things at the time until I made some noise. At one point I thought the Debian packagers were on this list as well but that could have changed for all I know and given the work load they have keeping up with all the packages they deal with. The one that did the 2.0.6-5 package is a daily user of Xastir in the UK so he would be one of the ones that I would be alerting. Dave KB3EFS On 06/27/2016 04:25 PM, David Ranch wrote: > > Hey Dave, > > Indeed your right and I see a 2.0.6-5 dated as of 6/2/2016: > > �� https://packages.qa.debian.org/x/xastir.html > > that's unusual using that as a 2.0.6 update when it's actually coming > from CVS.� It's not to say it's not done but usually the package name > includes a string like xaster-2.0.6-cvs20160602 or something like > that.�� None the less, cutting a new release is the best route and I'm > sure the Debian group would be happy to deprecate that 2.0.6-5 release > in favor of something newer.� The real benefit for non-compile savvy > HAMs comes from the backports to get say this 2.0.7 into Debian > Jessie, Ubuntu 16.04LTS, etc. > > --David > KI6ZHD > _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
