GNU bug report logs -
#41106
date --date '20180325 02:58:00' fails
Previous Next
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Wed, 6 May 2020 17:41:16 +0200
with message-id <5e011005-ca11-8ee4-319e-4c09ffa852a2 <at> bernhard-voelker.de>
and subject line Re: bug#41106: date --date '20180325 02:58:00' fails
has caused the debbugs.gnu.org bug report #41106,
regarding date --date '20180325 02:58:00' fails
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
41106: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41106
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Sorry I just found the reason in the FAQ... :-(
https://www.gnu.org/software/coreutils/faq/coreutils-faq.html#The-date-command-is-not-working-right_002e
I am in local daylight saving time change case.
Thanks
________________________________________
De : Julien Demaria
Envoyé : mercredi 6 mai 2020 09:59
À : bug-coreutils <at> gnu.org
Objet : date --date '20180325 02:58:00' fails
Hi,
We found this very suspect behavior:
$ date --date '20180325 02:58:00'
date: invalid date `20180325 02:58:00'
but for the previous day it works...:
$ date --date '20180323 02:58:00'
Fri Mar 23 02:58:00 CET 2018
Is it a bug?
Adding -u or setting TZ seems a workaround.
Tested with version 8.28 on Ubuntu 18.04.4 LTS
and also with version 8.13 on Debian GNU/Linux 7
Thanks in advance,
Julien
[Message part 3 (message/rfc822, inline)]
tag 41106 notabug
thanks
On 2020-05-06 10:04, Julien Demaria wrote:
>> $ date --date '20180325 02:58:00'
>> date: invalid date `20180325 02:58:00'
> Sorry I just found the reason in the FAQ... :-(
> https://www.gnu.org/software/coreutils/faq/coreutils-faq.html#The-date-command-is-not-working-right_002e
> I am in local daylight saving time change case.
Indeed, the debug option shows it:
date --debug --date '20180325 02:58:00'
date: parsed number part: (Y-M-D) 2018-03-25
date: parsed time part: 02:58:00
date: input timezone: system default
date: using specified time as starting value: '02:58:00'
date: error: invalid date/time value:
date: user provided time: '(Y-M-D) 2018-03-25 02:58:00'
date: normalized time: '(Y-M-D) 2018-03-25 03:58:00'
date: --
date: possible reasons:
date: non-existing due to daylight-saving time;
date: numeric values overflow;
date: missing timezone
date: invalid date '20180325 02:58:00'
As such, I'm marking this issue as 'notabug' in our bug tracker.
Have a nice day,
Berny
This bug report was last modified 5 years and 99 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.