This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
web/1653: gdb cvs HEAD version.in stuck at 2004-04-17
- From: mec dot gnu at mindspring dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 16 May 2004 19:19:46 -0000
- Subject: web/1653: gdb cvs HEAD version.in stuck at 2004-04-17
- Reply-to: mec dot gnu at mindspring dot com
>Number: 1653
>Category: web
>Synopsis: gdb cvs HEAD version.in stuck at 2004-04-17
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: maintenance
>Submitter-Id: net
>Arrival-Date: Sun May 16 19:28:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: mec.gnu@mindspring.com
>Release: gdb HEAD 2004-05-16
>Organization:
>Environment:
>Description:
In gdb HEAD, the last update of version.in was on 2004-04-17.
>How-To-Repeat:
cat version.in
Or start up gdb and look at the date.
>Fix:
I looked in gdbadmin but did not see anything suspicious.
crontab/crontab was last updated on 2004-02-28.
ss/update-cvs-version was last updated on 2001-01-12.
The update on gdb_6_1-branch kept happening fine on 2004-04-17 and afterwards.
I don't have access to read the log files on sourceware.
The important logs are $HOME/log/update-cvs-version and $HOME/log/update-cvs-version.gdb_6_1-branch
>Release-Note:
>Audit-Trail:
>Unformatted: