jq fromdate is one hour off and hence FTBFS when local time is during daylight savings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
jq (Debian) |
Fix Released
|
Unknown
|
|||
jq (Ubuntu) |
Fix Released
|
Medium
|
Christian Ehrhardt | ||
Focal |
Fix Released
|
Low
|
Unassigned | ||
Groovy |
Fix Released
|
Low
|
Unassigned | ||
Hirsute |
Fix Released
|
Medium
|
Christian Ehrhardt |
Bug Description
[Impact]
* An upstream change in version 1.6 turned out to break
depending on the current timezone (that is how it went undetected
for so long)
* Upstream undid the change and we want to follow them by backporting
that.
[Test Case]
* root@h:~# TZ=America/New_York jq -n '"2018-
"2018-08-
This should return the same time as it was passed.
[Where problems could occur]
* jq can do many things and handling date conversions is just a small
fraction of it. But in that fraction fromdate|todate and regressions
would happen to take place.
And vice versa - if a jq user does not use those conversions it should
be a no-op for him.
Another regression could be if users were aware and added workarounds
(like doing -1 after the conversion). Obviously by fixing this it would
then be -1 off afterwards.
[Other Info]
* n/a
---
When trying to build jq locally it FTBFS for me since the unit tests that run during the build and check the output of fromdate fail:
Testing 'fromdate' at line number 642
*** Expected 1425599507, but got 1425603107 for test at line number 644: fromdate
Testing 'strptime(
Testing 'strptime(
*** Expected 1425599507, but got 1425603107 for test at line number 652: strptime(
This is caused by this upstream bug https:/
See attached for a debdiff which includes the upstream patch to resolve this.
Changed in jq (Debian): | |
status: | Unknown → New |
Changed in jq (Debian): | |
status: | New → Fix Released |
The attachment "updated debdiff which references this bug number" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]