FreeBSD web build failed on www.freebsd.org

[John Baldwin]

On Thursday 01 June 2006 21:52, World Wide Web Owner wrote:
> ===> news/2001
> ===> news/2002
> ===> news/2003
> ===> news/status
> ===> platforms
> ===> platforms/amd64
> ===> platforms/ia64
> ===> portmgr
> ===> projects
> ===> projects/acpi
> ===> projects/busdma
> ===> projects/c99
> ===> projects/dingo
> ===> projects/gnats4
> ===> projects/ideas
> ===> projects/mips
> ===> projects/bigdisk
> ===> projects/netperf
> ===> projects/nanobsd
> ===> prstats
> ===> prstats/../../tools/prstats
> ./go.tcl /c/gnats
> 61960 <State-Changed-From-To: closed-> > <closed > <> <closed>
> 86216 <State-Changed-From-To: open-> > <open > <> <open>
> 86217 <State-Changed-From-To: open-> > <open > <> <open>
> 74652 <State-Changed-From-To: open-> > <open > <> <open>
> 82276 <State-Changed-From-To: open-> > <open > <> <open>
> unable to convert date-time string "Fri Jun 2 00:35:12 EEST 2006"
>     while executing
> "clock scan [lrange $a 1 end"
>     (procedure "PR" line 10)
>     invoked from within
> "PR $pr"
>     ("foreach" body line 2)
>     invoked from within
> "foreach pr [glob $gnatsdir] {
> 	PR $pr
> }
> "
>     (file "./go.tcl" line 46)
> *** Error code 1
> 
> Stop in /w/www/build/www/tools/prstats.
> *** Error code 1

After some grep'ing, this appears to be due to an update made to PR 98311 
yesterday.  Other places that use 'EEST' seem to use a timestamp that 
includes the GMT offset (+0300) in the date time string:

% grep -r 'EEST' usb/
usb/80487:      for <FreeBSD-gnats-submit at freebsd.org>; Sat, 30 Apr 2005 
22:33:35 +0300 (EEST)
usb/80487:      for <FreeBSD-gnats-submit at freebsd.org>; Sat, 30 Apr 2005 
21:27:22 +0300 (EEST)
usb/80487:      Sat, 30 Apr 2005 21:27:20 +0300 (EEST)
usb/80487:Date: Sat, 30 Apr 2005 21:27:20 +0300 (EEST)
usb/80487:System: FreeBSD 5.4-STABLE FreeBSD 5.4-STABLE #0: Fri Apr 29 
12:19:56 EEST 2005 r at p:/usr/obj/usr/src/sys/L i386

So perhaps this can be fixed by just changing the two EEST date stamps in this 
PR to use that format instead.  Alternatively the tcl script could be fixed 
if possible.  I'll defer to bugmaster@ on this one though.

-- 
John Baldwin