On Tue, Oct 4, 2011 at 8:49 PM, s.pl...@juno.com <s.pl...@juno.com> wrote: > From: steve > To: bug-bash@gnu.org > Subject: bug in date command > > Configuration Information [Automatically generated, do not change]: > Machine: i586 > OS: linux-gnu > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' > -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-mandriva-linux-gnu' > -DCONF_VENDOR='mandriva' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' > -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -O2 -pipe > -Wp,-D_FORTIFY_SOURCE=2 -fomit-frame-pointer -march=i586 -mtune=generic > -fasynchronous-unwind-tables > uname output: Linux PCLOS 2.6.33.5-pclos1.bfs #1 SMP PREEMPT Sun May 30 > 02:37:14 CDT 2010 i686 i686 i386 GNU/Linux > Machine Type: i586-mandriva-linux-gnu > > Bash Version: 4.1 > Patch Level: 0 > Release Status: release > > Description: > When using date command with -d option, if the date is between > "2010-03-14 02:00" and "2010-03-14 02:59" inclusive, it gives an > "invalid date" error. You can test this with the following command: > echo $(date -d "2010-03-14 02:00" +%s) > Dates outside this range work fine.
This is an issue with GNU date, and has nothing to do with bash. Please report the bug to the email address included in the GNU date documentation, bug-coreut...@gnu.org
