Re: ✘ Release blockers?

[Fred Wright]

On Wed, 11 Dec 2019, Gary E. Miller wrote:
> On Sun, 8 Dec 2019 20:10:40 -0800 (PST)
> Fred Wright <address@hidden> wrote:
>
> > On Fri, 6 Dec 2019, Gary E. Miller wrote:
> >
> > [...]
> > > Anything else that shold be addressed before next release?
> >
> > There are two regressions since the last release that I'm aware of:
>
> One fixed, one to go.  See below.  Any others anyone sees?
>
> > 1) The C++ build breakage related to timespec_str.  I already have a
> > tentative fix for that, but just as I was about to test it, I ran
> > into a disk-space issue for my VMs, which I'm in the process of
> > sorting out.  The whole C++ area is pretty much a mess, but at least
> > this can make it no worse than it used to be.
>
> Any progress?

After getting the VM setup working again, I ran across another regression 
which I fixed.  There's still an issue that only shows up on OpenBSD, 
though I haven't yet determined why.  Unfortunately, my time is really 
limited this week.  If you're not in too much of a rush to get a release 
out, I can probably fix a couple of other things in the "not regressions 
but nice to fix" category next week.

> > 2) The rename of the altitude field has an interoperability issue
> > with other GPSD versions.  The client and server can be on different
> > machines, and not necessarily the same version.  At least one
> > direction should be fixable with a bit of fallback code.
>
> I restored "alr"/"altitude" and marked it deprecated and undefined.

I'm not sure that alone is enough to fix it, but I'll try it when I get a 
chance.

Fred Wright