Subject: bug#13938: Bug: date(1) -d "relative-to-skipped-time" problem (also in touch(1) -d)

From: Assaf Gordon <[email-masked]>
Date: Tue, 23 Oct 2018 16:37:35 -0600

close 13938
stop

(triaging old bugs)

On 12/03/13 11:23 PM, Bob Proulx wrote:
> Aleš Kantor wrote:
>> Set date to Mar 10, 2013  (the day clocks moved fwd)
> 
> In which timezone?  Please tell us what timezone you are in because
> the tzdata is different for everyone.
> 
> Instead of setting the time simply include the date in the timestamp.
> But for the purpose of recreating the problem please do include the
> timezone too.  The -R,--rfc-2822 option is good to use to avoid the
> ambiguous timezone naming used in the traditional legacy output.
> 
>    $ env TZ=US/Mountain date -R -d "2013-03-10 12:00"
>    Sun, 10 Mar 2013 12:00:00 -0600
> 
>> This command
>>      date -d 2:30am
>> gives "Invalid date," probably reasonable, since that time didn't exist.
> 
> Correct.  In US timezones at least that time does not exist.
> 
>> This one should work, but fails as well:
>>    date  -d "2:00am yesterday"
>> date: invalid date `2:00am yesterday'
> 

With no further comments to Bob's explanation in 5 years,
I'm closing this bug.

-assaf