[Savannah-help-public] [sr #106105] Problems with cvs commit

Update of sr #106105 (project administration): Status:None => Done Open/Closed:Open => Closed ___ Follow-up Comment #10: Ok, all do

[Savannah-help-public] [sr #106105] Problems with cvs commit

Follow-up Comment #9, sr #106105 (project administration): Please remove the following directories as well: [metaexchange] / metaexchange / scantest / SNAPSHOTS [metaexchange] / metaexchange / atest / SNAPSHOTS [metaexchange] / metaexchange / dc_test / SNAPSHOTS [metaexchange] / metaexchange / l

[Savannah-help-public] [sr #106105] Problems with cvs commit

Follow-up Comment #8, sr #106105 (project administration): Hi, I removed the 'SNAPSHOTS' directory. Indeed CVS does not allow data to be truly removed, so this had to be done by an admin. Please let me know if things are ok for you. ___

[Savannah-help-public] [sr #106105] Problems with cvs commit

Follow-up Comment #7, sr #106105 (project administration): > To sum up I think it's best to move the snapshots outside of the > repository, and select a subset of snapshots you want to publish > (the recent ones, one by month?) - either do it yourself or I can > script some export locally at S

[Savannah-help-public] [sr #106105] Problems with cvs commit

Follow-up Comment #6, sr #106105 (project administration): Hi, - Yes, there is a download area that is hosted at Savannah, and it's different than the alpha.gnu.org/ftp.gnu.org. However, GNU projects tend not to use it, because they don't really need it. I suggested using it because the direct S

[Savannah-help-public] [sr #106105] Problems with cvs commit

Follow-up Comment #5, sr #106105 (project administration): > Hmm, for tarballs, don't you want to use the download area? > (possibly the Savannah one, which can be managed by SFTP, unlike > ftp.gnu.org). Maybe the Savannah one, of which I was not aware. I know there's a download area for each

[Savannah-help-public] [sr #106105] Problems with cvs commit

Follow-up Comment #4, sr #106105 (project administration): Hmm, for tarballs, don't you want to use the download area? (possibly the Savannah one, which can be managed by SFTP, unlike ftp.gnu.org). In particular, 3DLDFsnp.tar.gz,v alone has a size of 1.5GB... "It certainly doesn't pay to calcu

[Savannah-help-public] [sr #106105] Problems with cvs commit

Follow-up Comment #3, sr #106105 (project administration): Thank you, Sylvain. It's working now. I take it this problem has nothing to do with my project, i.e., it's not my RCS files that ViewVC doesn't like? By the way, unless I'm adding a file, I usually submit batches of files, including a

[Savannah-help-public] [sr #106105] Problems with cvs commit

Follow-up Comment #2, sr #106105 (project administration): You sent by mail: > Yes, right now: Thu Dec 6 23:50:11 CET 2007 > > Not just a slow-down; the commit timed-out and I couldn't load any webpages from Savannah. That's ViewVC for you: eating all the CPU when processing some RCS files i

[Savannah-help-public] [sr #106105] Problems with cvs commit

Update of sr #106105 (project administration): Assigned to:None => Beuc ___ Follow-up Comment #1: I don't know what I can say, the system appears to be fine. Can you note the precise ti

[Savannah-help-public] [sr #106105] Problems with cvs commit

URL: Summary: Problems with cvs commit Project: Savannah Administration Submitted by: lfinsto1 Submitted on: Thursday 11/29/2007 at 22:20 Category: Developer CVS P