[Bug 354793] Re: date returns "invalid date" for some timezone's DST

[Sven Ehret]

It is still not working as expected with Lucid.

And it's breaking a script of mine, sending every instance to an
endless, CPU eating loop…

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/354793

Title:
  date returns "invalid date" for some timezone's DST

Status in “apt” package in Ubuntu:
  Fix Released
Status in “coreutils” package in Ubuntu:
  Won't Fix
Status in “apt” source package in Dapper:
  Fix Released
Status in “coreutils” source package in Dapper:
  Won't Fix
Status in “apt” source package in Gutsy:
  Won't Fix
Status in “coreutils” source package in Gutsy:
  Won't Fix
Status in “apt” source package in Hardy:
  Fix Released
Status in “coreutils” source package in Hardy:
  Won't Fix
Status in “apt” source package in Intrepid:
  Fix Released
Status in “coreutils” source package in Intrepid:
  Won't Fix
Status in “apt” source package in Jaunty:
  Fix Released
Status in “coreutils” source package in Jaunty:
  Won't Fix

Bug description:
  Date command gives an error when trying to get a day that starts the
  daylight saving time. Examples:

  $ date --date=2008-10-18
  Sáb Out 18 00:00:00 BRT 2008
  $ date --date=2008-10-19
  date: data inválida "2008-10-19"
  $ date --date=2008-10-20
  Seg Out 20 00:00:00 BRST 2008

  $ date --date=2009-10-17
  Sáb Out 17 00:00:00 BRT 2009
  $ date --date=2009-10-18
  date: data inválida "2009-10-18"
  $ date --date=2009-10-19
  Seg Out 19 00:00:00 BRST 2009

  I checked this as a security bug as this can cause scripts to fail.
  For example, cron's apt script fails if update-stamp is in this day,
  causing the system to never more update periodically. In other words:
  Many servers can be out of date because of this bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/354793/+subscriptions