All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: Robert Hancock <robert.hancock@calian.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Cc: "bernd.kuhls@t-online.de" <bernd.kuhls@t-online.de>,
	Peter Korsgaard <jacmet@sunsite.dk>
Subject: Re: [Buildroot] Serious time jump bug found in gpsd 3.20+
Date: Thu, 5 Aug 2021 22:26:58 +0200	[thread overview]
Message-ID: <202fcb4f-1edb-30bd-806d-e530619d510d@mind.be> (raw)
In-Reply-To: <4a27ed904dd80b00498185003c9a7bb26dc9a128.camel@calian.com>



On 05/08/2021 22:09, Robert Hancock via buildroot wrote:
> A heads up to the Buildroot community about a significant bug that has been
> found in versions 3.20 and newer of the gpsd package, and which is fixed in
> version 3.23 (not yet released, supposed to be shortly):
> 
> https://gitlab.com/gpsd/gpsd/-/issues/144
> 
> This will cause the calculated GPS time (and NTP time, if synchronizing to it)
> to jump from 2021 back to 2002 when GPS week 2180 arrives on October 24, 2021,
> with potentially disastrous results for applications depending on accurate time
> keeping.
> 
> A patch has now been added to the gpsd repository to fix it (note that the
> commit message incorrectly refers to 2020 rather than 2021 as pointed out by a
> commenter): 
> https://gitlab.com/gpsd/gpsd/-/commit/7f30d88d04dc62b8bd6265ad1d09d72d220f97f6
> 
> I am not sure if the best solution for Buildroot is to just update the package
> when released, or apply the specific patch to fix the issue? Currently
> Buildroot master is on 3.21 and the 2021.02.x LTS branch is on 3.20, both of
> which are affected.

 For master, I think we can still afford to update to 3.23.

 For 2021.05.x and 2021.02.x, we'll need to backport the patch. Unless if Peter
thinks that in this case (since upstream's policy is "always update to latest")
it's OK to just bump it there as well?

 Regards,
 Arnout

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-08-05 20:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-05 20:09 [Buildroot] Serious time jump bug found in gpsd 3.20+ Robert Hancock via buildroot
2021-08-05 20:26 ` Arnout Vandecappelle [this message]
2021-08-05 20:29   ` Arnout Vandecappelle
2021-08-06 20:56     ` Peter Korsgaard
2021-08-06 20:55   ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202fcb4f-1edb-30bd-806d-e530619d510d@mind.be \
    --to=arnout@mind.be \
    --cc=bernd.kuhls@t-online.de \
    --cc=buildroot@buildroot.org \
    --cc=jacmet@sunsite.dk \
    --cc=robert.hancock@calian.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.