axiom-developer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] Axiom silver branch


From: Frederic Lehobey
Subject: Re: [Axiom-developer] Axiom silver branch
Date: Sat, 8 Apr 2006 22:34:38 +0200
User-agent: Mutt/1.5.9i

Hi,

On Fri, Apr 07, 2006 at 11:51:49AM -0400, Bill Page wrote:

> Can someone confirm they successfully done a checkout of this archive?

> but after transferring about 30 Mbytes it gives me the following
> error message:
> 
>   Error  REPORT request failed on '/svnroot/axiom/!svn/vcc/default'
>   Error  REPORT of '/svnroot/axiom/!svn/vcc/default':
>            Could not read response body:
>              Secure connection truncated
>                (https://svn.sourceforge.net)

I am seeing this almost all the time:

svn: REPORT request failed on '/svnroot/axiom/!svn/vcc/default'
svn: REPORT of '/svnroot/axiom/!svn/vcc/default': Could not read response body: 
Secure connection truncated (https://svn.sourceforge.net)

(on Debian sarge) for the command:

$ svn co https://svn.sourceforge.net/svnroot/axiom/trunk/axiom silver

I have tried this something like 10 times.  And for the 1 or 2 times
it completed, I got the following error after make:

----------------------------------------------------------------
$ LANG=C make
13 making noweb
tar: Skipping to next header
tar: Archive contains obsolescent base-64 headers
 incomplete literal tree

gzip: stdin: invalid compressed data--format violated
tar: Child returned status 1
tar: Error exit delayed from previous errors
/bin/sh: line 1: cd: /home/fdl/axiom/silver/obj/noweb/src/c: No such file or 
directory
can't find file to patch at input line 3
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|--- modules.c  Wed Mar 28 13:49:22 2001
|+++ modules.c.tpd      Mon Nov 18 22:26:35 2002
--------------------------
----------------------------------------------------------------

Therefore I am not sure I can trust svn from sourceforge.  The branch
has been impossible to use so far for me.

It *might* be a problem with my provider not allowing enough ssh
traffic (very hard to prove but I have suspicions from other
problems).

It might also simply be sourceforge too overloaded.

Best regards,
Frédéric




reply via email to

[Prev in Thread] Current Thread [Next in Thread]