RE: [Axiom-developer] Axiom silver branch

[Bill Page]

On April 8, 2006 4:35 PM Frederic Lehobey wrote:
> 
> 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.

That is very bad news. :( I was hoping that this error was
confined to Windows.

> 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
> ... 
> 
> Therefore I am not sure I can trust svn from sourceforge.
> The branch has been impossible to use so far for me.

The same for me. :( I think the error above with tar file is
probably caused by the fact that the .tgz files in the current
CVS and tla archives are not properly marked as 'binary' files.
This has caused me problem before when using the Axiom CVS
under Windows because some Windows CVS packages do silly things
like automatically converting the unix line ending to CF LF on
Windows and of course that trashes any binary file that the
system thinks is text.

Apparently this is a known complication when converting CVS
archives to SVN. E.g.

http://list.coin-or.org/pipermail/project-managers/2005-October/000008.html
http://subversion.tigris.org/faq.html#binary-files

Storing binary files in a source code archive is something that
I have always objected to, but Tim insists on re-distributing
code this way. I really think we should stop doing this.

> 
> 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.

In my case I have no other problems using ssh to the sourceforge
site from Windows using other software.

Regards,
Bill Page.