[Savannah-hackers] [support #103379] savannah coreutils repository stopped working Sept. 6

[Elfyn McBratney]

This mail is an automated notification from the support tracker
 of the project: Savannah Administration.

/**************************************************************************/
[support #103379] Latest Modifications:

Changes by: 
                Elfyn McBratney <address@hidden>
'Date: 
                Wed 09/22/2004 at 14:34 (Europe/London)

------------------ Additional Follow-up Comments ----------------------------
Apologies, I'm pretty sure I broke this.  I'll fix it now.  

Btw, note that write access is not permitted for remote repositories (such as 
automake, coreutils, gcc and others).  In fact developer cvs should not even be 
enabled for coreutils, but I guess that's anoth bug.  Sigh...






/**************************************************************************/
[support #103379] Full Item Snapshot:

URL: <http://savannah.gnu.org/support/?func=detailitem&item_id=103379>
Project: Savannah Administration
Submitted by: Paul Eggert
On: Sun 09/19/2004 at 03:50

Category:  Savannah website
Priority:  5 - Normal
Severity:  7 - Major
Resolution:  Postponed
Privacy:  Public
Assigned to:  Beuc
Originator Email:  address@hidden
Status:  Open


Summary:  savannah coreutils repository stopped working Sept. 6

Original Submission:  The coreutils project is a bit unusual: its CVS files are 
maintained offsite, and savannah polls it once an hour.  This procedure stopped 
working 12 days ago; the last update of Savannah coreutils that I can find is 
dated Mon Sep 6 07:49:21 2004 UTC. Savannah is still polling the offsite 
location every  hour (12 minutes after the hour), and is obtaining the updates, 
but these updates are not being published via Savannah's web interface. Also, 
CVS readonly access doesn't work, e.g.:

$ cvs -d :ext:address@hidden:/cvsroot/coreutils co coreutils
Invalid CVSROOT (2)
cvs checkout: invalid data from cvs server


Follow-up Comments
------------------


-------------------------------------------------------
Date: Wed 09/22/2004 at 14:34       By: Elfyn McBratney <beu>
Apologies, I'm pretty sure I broke this.  I'll fix it now.  

Btw, note that write access is not permitted for remote repositories (such as 
automake, coreutils, gcc and others).  In fact developer cvs should not even be 
enabled for coreutils, but I guess that's anoth bug.  Sigh...

-------------------------------------------------------
Date: Wed 09/22/2004 at 05:48       By: Paul Eggert <eggert>
Unfortunately the problem is not yet fixed.
The Savannah website and CVS repository are
still not being updated by the automated
procedure that I mentioned.

The only thing that has been fixed is remote
readonly CVS access (which was support #103358).

What has not been fixed is that the Savannah
CVS repository is still not being updated
automatically, as it should be.  Savannah is
still polling the master copy of the CVS
files via rsync every hour, but Savannah is
apparently not making the updated CVS files
accessible to its CVS server or web server.


-------------------------------------------------------
Date: Tue 09/21/2004 at 23:11       By: Sylvain Beucler <Beuc>
It is temporarily fixed. The owner were not well set. I'll check this issue in 
detail as soon as I have more time. I let the item open for now.




CC List
-------

CC Address                          | Comment
------------------------------------+-----------------------------
ldv                                 | 
meyering                            | 
rwp                                 | 









For detailed info, follow this link:
<http://savannah.gnu.org/support/?func=detailitem&item_id=103379>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/