bug#12650: Bug in date command

2018-10-23 Thread Assaf Gordon
close 12650 stop (triaging old bugs) On 14/10/12 05:28 PM, Bob Proulx wrote: Thiago Picharski wrote: I'm trying run this command "date -d 12-10-21", but occur the follow error, date: invalid date "12-10-21" and finalize with error code 1. [...] The basic problem is that when you specify 12-

bug#23270: Bug in 'date' command

2016-04-11 Thread Assaf Gordon
tag 23270 notabug close 23270 thanks Hello Maarten Mastbroek, On 04/11/2016 12:36 PM, Maarten wrote: I recently discovered a bug, or at least unexpected behavior, about the ‘date’ command which I want to report. The bug is related to the moment of ‘daylight saving time’ (summertime / wintertim

bug#23270: Bug in 'date' command

2016-04-11 Thread Maarten
Hello,   I recently discovered a bug, or at least unexpected behavior, about the ‘date’ command which I want to report.  The bug is related to the moment of ‘daylight saving time’ (summertime / wintertime)   On Monday the 28st of march at 0.15 I run an automated script with the command: # dat

bug#15927: Bug in date command

2013-11-19 Thread Bob Proulx
tag 15927 - moreinfo + notabug close 15927 thanks Hello Claudio, Please keep the bug log in the recipient list. That way others in the team on the mailing list can participate in the discussion. Claudio Pinto wrote: > Current default time zone: 'America/Sao_Paulo' > Local time is now: Ter

bug#15927: Bug in date command

2013-11-19 Thread Bob Proulx
tag 15927 + moreinfo thanks Claudio Pinto wrote: > date --date=10/20/2013 > result in > date: invalid date `10/20/2013' In what timezone? You didn't give your timezone therefore it is impossible to know for sure but your problem statement matches one of the very common cases where Daylight Savin

bug#15927: Bug in date command

2013-11-19 Thread Eric Blake
tag 15927 needinfo thanks On 11/19/2013 05:23 AM, Claudio Pinto wrote: > date --date=10/20/2013 > > result in > > date: invalid date `10/20/2013' We need more details, such as your current timezone. I suspect that you are running into a FAQ: https://www.gnu.org/software/coreutils/faq/coreutil

bug#15927: Bug in date command

2013-11-19 Thread Claudio Pinto
date --date=10/20/2013 result in date: invalid date `10/20/2013' version: date (GNU coreutils) 8.13

bug#12650: Bug in date command

2012-10-14 Thread Bob Proulx
tags 12650 + moreinfo thanks Thiago Picharski wrote: > I'm trying run this command "date -d 12-10-21", but occur the follow > error, date: invalid date "12-10-21" > and finalize with error code 1. What timezone are you in? Almost certainly that timezone experienced a daylight savings time change

bug#12650: Bug in date command

2012-10-14 Thread Thiago Picharski
Hello, I'm trying run this command "date -d 12-10-21", but occur the follow error, date: invalid date "12-10-21" and finalize with error code 1. Interestingly, when i run "date -d 12-10-20" or "date -d 12-10-22" this work fine. Thanks! Thiago H. S. Picharski

Re: bug in date command

2009-08-19 Thread Pádraig Brady
Prog piR wrote: > date +%^B gives the month in capital letters > > but in french august is "août", and the accentued letter is not capitalized > > date +%^B gives AOûT instead of AOÛT Nor does tr '[:lower:]' '[:upper:]' support multibyte chars either, I'll add that to the list of multibyte stuff

bug in date command

2009-08-19 Thread Prog piR
date +%^B gives the month in capital letters but in french august is "août", and the accentued letter is not capitalized date +%^B gives AOûT instead of AOÛT In addition, is there any option to have lowercase ? Thanks

Re: bug in date-command

2009-03-13 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bob Proulx on 3/13/2009 3:03 PM: >> This works perfect for all dates I used so far, apart from a (strangely >> enough) 20081026 >> date -d "20081026 1 days" +%Y%m%d >> returns the same datecode: 20081026 > > You probably want to do the d

Re: bug in date-command

2009-03-13 Thread Bob Proulx
Bas Mijling wrote: > I use the date command to find the next day of a date written in the > 'mmdd' format, > e.g. for 25 October 2008 Just a side note: I like using %F for this type of string. > This works perfect for all dates I used so far, apart from a (strangely > enough) 20081026 > dat

bug in date-command

2009-03-13 Thread Bas Mijling
Hi, I use the date command to find the next day of a date written in the 'mmdd' format, e.g. for 25 October 2008 date -d "20081025 1 days" +%Y%m%d which gives as result the next day: 20081026 This works perfect for all dates I used so far, apart from a (strangely enough) 20081026 dat

Re: Bug in date command

2009-01-07 Thread Bob Proulx
Eric Blake wrote: > A couple of nits: > > "The parsing of dates with date --date=STRING is a GNU extension and not > covered by any standards beyond those to which GNU holds itself." Not > entirely true any longer, now that POSIX 2008 requires that 'touch -d > STRING' parse a limited format of IS

Re: Bug in date command

2009-01-07 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bob Proulx on 1/7/2009 3:12 PM: > > http://www.gnu.org/software/coreutils/faq/coreutils-faq.html#The-date-command-is-not-working-right_002e > > How does that look? A couple of nits: "The parsing of dates with date --date=STRING is a

Re: Bug in date command

2009-01-07 Thread Bob Proulx
Eric Blake wrote: > There seems to always be a rash of "bug" reports about date at the > turn of the year (and also around daylight savings changes), due to > the large number of people who don't realize the subtleties > involved. Perhaps we should create a FAQ entry with the most common > of thes

Re: Bug in date command

2009-01-07 Thread Bob Proulx
Bob Kline wrote: > The date command reports the wrong ISO week number in some cases. For > example: > > $ date -d 2008-12-31 +%Y%V > 200801 > > Clearly the last day of the year can't be in the first week of that > year. According to ISO 8601 it can. See the official standard for the authoritat

Re: Bug in date command

2009-01-07 Thread Eric Blake
Bob Kline rksystems.com> writes: > > The date command reports the wrong ISO week number in some cases. For > example: > > $ date -d 2008-12-31 +%Y%V > 200801 Not a bug in date, but in your misuse of incompatible formats. 2008-12-31 is in the first ISO week of 2009, as evidenced by: $ date

Bug in date command

2009-01-07 Thread Bob Kline
The date command reports the wrong ISO week number in some cases. For example: $ date -d 2008-12-31 +%Y%V 200801 Clearly the last day of the year can't be in the first week of that year. -- Bob Kline http://www.rksystems.com mailto:bkl...@rksystems.com __

Re: Bug in date command

2007-11-22 Thread Santiago Vila
On Wed, 21 Nov 2007, Eric Blake wrote: > So it looks like a lot of work still needs doing. Indeed. Thanks for the reminder. ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gnu.org/mailman/listinfo/bug-coreutils

Re: Bug in date command

2007-11-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [Please keep replies on the list, so that others can read about it] [Adding the last-documented Spanish translation team] According to Toni on 11/21/2007 10:32 PM: > According to Toni on 11/21/2007 2:28 PM: >> date +%R does not show seconds > > Not a

Re: Bug in date command

2007-11-21 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Toni on 11/21/2007 2:28 PM: > date +%R does not show seconds Not a bug, since that is what it is documented to do: $ date --help | grep %R %R 24-hour hour and minute; same as %H:%M - -- Don't work too hard, make some time for fun as

Bug in date command

2007-11-21 Thread Toni
Linux version 2.6.22-14-generic ([EMAIL PROTECTED]) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14 23:05:12 GMT 2007 date +%R does not show seconds ___ Bug-coreutils mailing list Bug-coreutils@gnu.org http://lists.gn

Re: bug in date command

2004-05-14 Thread Andreas Schwab
Bauke Jan Douma <[EMAIL PROTECTED]> writes: > On Fri, May 14, 2004 at 11:27:53AM +0200, Andreas Schwab wrote: >> Bauke Jan Douma <[EMAIL PROTECTED]> writes: >> >> > On Fri, May 14, 2004 at 12:51:20AM +0200, Andreas Schwab wrote: >> >> "duncan brown" <[EMAIL PROTECTED]> writes: >> >> >> >> > date

Re: bug in date command

2004-05-14 Thread Bauke Jan Douma
On Fri, May 14, 2004 at 11:27:53AM +0200, Andreas Schwab wrote: > Bauke Jan Douma <[EMAIL PROTECTED]> writes: > > > On Fri, May 14, 2004 at 12:51:20AM +0200, Andreas Schwab wrote: > >> "duncan brown" <[EMAIL PROTECTED]> writes: > >> > >> > date +%C reports the 20th century, but we've been in the

Re: bug in date command

2004-05-14 Thread Andreas Schwab
Bauke Jan Douma <[EMAIL PROTECTED]> writes: > On Fri, May 14, 2004 at 12:51:20AM +0200, Andreas Schwab wrote: >> "duncan brown" <[EMAIL PROTECTED]> writes: >> >> > date +%C reports the 20th century, but we've been in the 21st since jan 01, >> > 00:00:00 >> >> %C century (year divided by 100

Re: bug in date command

2004-05-13 Thread Bauke Jan Douma
On Fri, May 14, 2004 at 12:51:20AM +0200, Andreas Schwab wrote: > "duncan brown" <[EMAIL PROTECTED]> writes: > > > date +%C reports the 20th century, but we've been in the 21st since jan 01, > > 00:00:00 > > %C century (year divided by 100 and truncated to an integer) [00-99] Surely this mu

Re: bug in date command

2004-05-13 Thread Andreas Schwab
"duncan brown" <[EMAIL PROTECTED]> writes: > date +%C reports the 20th century, but we've been in the 21st since jan 01, 00:00:00 %C century (year divided by 100 and truncated to an integer) [00-99] Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux AG, Maxfeldstraße 5, 90

bug in date command

2004-05-13 Thread duncan brown
date +%C reports the 20th century, but we've been in the 21st since jan 01, 00:00:00 -d Time will end all my troubles, but I don't always approve of Time's methods. +( duncan brown +( [EMAIL PROTECTED] +( http://www.linuxadvocate.net ___ Bug-coreuti