Hi Boian, On Sun, Dec 10, 2023 at 01:10:01AM +0200, Boian Bonev wrote: > Hi, > > That report states that the bug affects 3.25.1~dev. There is no such gpsd > release. > > I did check with upstream - that is a development git tree. And the problem is > already fixed and will not affect the next gpsd version (supposedly 3.26) > > 3.25-2 in Debian is also not affected. > > I'd suggest closing this bug.
Thanks for the input on the bugreport. Note we cannot generally just trust version informations. But your comment let me look again at the issue. If I'm not mistaken, the fixing commit is https://gitlab.com/gpsd/gpsd/-/commit/3e5c6c28c422102dd453e31912e1e79d1f7ff7f2 . But this is not 100% assessed, but looks to be valid following the issue description from the TALOS report. I was so far unable to reprdouce with a "fake" TRIP caster. Form the sourround code the issue might still only be introduced with https://gitlab.com/gpsd/gpsd/-/commit/6ccd477f5e21a45f6c52a21ad323c93e59aa2461 https://gitlab.com/gpsd/gpsd/-/commit/c1c1c2706c4f5b9bf3be437d0a8f0106ef00c5e7 We need to be able to assess is this ist the correct deduction. If so then you are correct, and it won't affect even the version in unstable. gpsd Maintainers, had you already a chance to look closer at the issue? Regards, Salvatore
