bug#26081: --date=STRING error that started midnight 3/12

2017-03-13 Thread Fevzi Karavelioglu
Thank you yes, the debug option is going to be very useful. Fevzi On 3/13/17 9:06 PM, Pádraig Brady wrote: On 13/03/17 05:17, Eric Blake wrote: tag 26081 notabug thanks On 03/13/2017 12:09 AM, Fevzi Karavelioglu wrote: Hello, I started getting an error with the following command: $> date --

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

2017-03-13 Thread 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

bug#26081: --date=STRING error that started midnight 3/12

2017-03-13 Thread Pádraig Brady
On 13/03/17 05:17, Eric Blake wrote: > tag 26081 notabug > thanks > > On 03/13/2017 12:09 AM, Fevzi Karavelioglu wrote: >> Hello, I started getting an error with the following command: >> >> $> date --date="02:05 tomorrow" +%s >> *date: invalid date `02:05 tomorrow'* >> >> It appears any time 2 in

bug#26081: --date=STRING error that started midnight 3/12

2017-03-13 Thread Eric Blake
tag 26081 notabug thanks On 03/13/2017 12:09 AM, Fevzi Karavelioglu wrote: > Hello, I started getting an error with the following command: > > $> date --date="02:05 tomorrow" +%s > *date: invalid date `02:05 tomorrow'* > > It appears any time 2 in the morning causes the error. But everything els