[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ✘GPS WKRO workaround
|
From: |
Bernd Zeimetz |
|
Subject: |
Re: ✘GPS WKRO workaround |
|
Date: |
Sun, 8 Dec 2019 14:08:26 +0100 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 |
On 12/7/19 7:51 PM, Gary E. Miller wrote:
How are you getting "current GPS leap second"?
>
> The base layer is that gpsd is compiled in with a starting leap
> second value. Right now that comes from timebase.h, which is created
> by leapsecond.py. The value there is 19, but the correct current value
> is 18. leapsecond.py must die.
If I remember right a found a fix for that issue without letting it die,
so if removing the code is too much work right now, we could at least
just fix it. I can did it out and commit if if you want.
Bernd
--
Bernd Zeimetz Debian GNU/Linux Developer
http://bzed.de http://www.debian.org
GPG Fingerprint: ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
- ✘GPS WKRO workaround, Gary E. Miller, 2019/12/06
- Re: ✘GPS WKRO workaround, Fred Wright, 2019/12/08
- Re: ✘GPS WKRO workaround, Gary E. Miller, 2019/12/09
- ✘ Release blockers?, Gary E. Miller, 2019/12/11
- Re: ✘ Release blockers?, Fred Wright, 2019/12/11
- Re: ✘ Release blockers?, Gary E. Miller, 2019/12/12
- Re: ✘ Release blockers?, Gary E. Miller, 2019/12/12
- Re: ✘ Release blockers?, Fred Wright, 2019/12/12
- Re: ✘ Release blockers?, Gary E. Miller, 2019/12/12