bug#26081: closed (Re: bug#26081: --date=STRING error that started midnight 3/12)

[Fevzi Karavelioglu]

It is a great FAQ and yes I see it covers this.  Now I understand it 
would not be able to tell me the 2AM for the day we are skipping it. 
What threw me off was also the fact that 'tomorrow' was a day we did not 
skip 2AM.  So the clocks went forward at 2AM on 3/12. But I was asking 
for the next day 2AM. So it was still failing because the 2AM was 
skipped on the previous day, correct?

And yes it is working fine today.

Luckily my application is not mission critical.  But I still need to 
figure out a way to avoid this problem in the future (unless we do away 
with DST real soon, can't happen too soon for me!). I will need to add 
special logic to my code to handle this. It is going to be fun.

Fevzi

On 3/13/17 5:18 AM, GNU bug Tracking System wrote:
> Your bug report
>
> #26081: --date=STRING error that started midnight 3/12
>
> which was filed against the coreutils package, has been closed.
>
> The explanation is attached below, along with your original report.
> If you require more details, please reply to address@hidden