RE: [Axiom-developer] RE: [M#73697383] Re: Disk-quota Request

[Bill Page]

Ben,

Hmmm, "bleeding edge" you say? I think I'm going to need a
transfusion soon ... ;)

Here's the latest:

~=~=~= PuTTY log 2006.10.04 11:52:26 =~=~=~
address@hidden page]$ svnsync init
  https://axiom.googlecode.com/svn file:///home/page/axiom-sf
Authentication realm: <https://axiom.googlecode.com:443>
 Google Code Subversion Repository
Password for 'page': 
Authentication realm: <https://axiom.googlecode.com:443>
 Google Code Subversion Repository
Username: synthesis.anikast.ca
Password for 'synthesis.anikast.ca': 
Copied properties for revision 0.
address@hidden page]$ svnsync sync
  https://axiom.googlecode.com/svn
Committed revision 1.
Copied properties for revision 1.
Committed revision 2.
Copied properties for revision 2.

--------

After about 1 hour the console session was unexpectedly
interrupted by my host computer (probably a connection
time- out because of no console traffic).

I restarted with the command:

address@hidden page]$ nohup svnsync sync
  https://axiom.googlecode.com/svn &

After about an hour I saw the synsync process had terminated.
nohup.out contains only:

svnsync: Caught signal

--------

<sigh> So I restarted it again:

address@hidden page]$ nohup svnsync sync
  https://axiom.googlecode.com/svn &

And about an hour later again svnsync terminated. In the log
I see:

svnsync: PUT of
'/svn/!svn/wrk/29cc7f0b-011f-0410-b261-d5f055a290b5/trunk/axiom/src/input/tk
not.input.pamphlet':
 403 Forbidden (https://axiom.googlecode.com)

----------

I am patient but you can guess my conclusions from my experience
so far.

We can either continue debugging this process or wait until someone
else does since it seems unlikely that decision to use subversion
(and associated tools) will be changed just because two of the Axiom
developers can't seem to get it to work. :-(

So I remain: at your service. ;)

What's next?

Regards,
Bill Page.




> -----Original Message-----
> From: Ben Collins-Sussman [mailto:address@hidden 
> Sent: October 4, 2006 10:46 AM
> To: address@hidden
> Cc: axiom-dev; Gabriel Dos Reis
> Subject: Re: [Axiom-developer] RE: [M#73697383] Re: Disk-quota
> Request
> 
> 
> On 10/3/06, Page, Bill <address@hidden> wrote:
> ...
> > svnsync: PROPFIND request failed on '/svn'
> > svnsync: PROPFIND of '/svn': Could not read status line:
> > Secure connection truncated (https://axiom.googlecode.com)
> 
> Hm, that actually looks like a server crash!  I'll investigate.
> 
> However, I do see a problem:  it's a bug in my function to reset
> the repository.  While it removes all revisions back to revision
> 0, it doesn't actually remove the old rev-props attached to
> revision 0! Witness all the svn:svnsync* revision properties left
> behind by your last attempt to run svnsync:
> 
> $ svn proplist --verbose --revprop -r0 http://axiom.googlecode.com/svn
> Unversioned properties on revision 0:
>   svn:sync-from-uuid : 54bea96e-1511-0410-8851-aaeae44645fa
>   svn:sync-currently-copying : 3
>   svn:sync-last-merged-rev : 2
>   svn:date : 2006-04-10T15:40:55.446251Z
>   svn:sync-from-url : file:///home/page/axiom-sf
> 
> I've worked around the problem by manually running 'svn propdel'
> to delete each of these, so now your r0 is all clear of metadata.
> (And I'll get to fixing the reset() bug too.)
> 
> I suspect the problems may have come from svnsync just dying when
> it was running into its own obsolete/stale revision-props from
> previous runs.  Try doing the 'svnsync init' again, and see if
> it works.
> 
> > I really do not understand why I am having so much trouble
> > with subversion. :-( I do feel like I am making a very serious
> > effort to try to make it work but getting nowhere.
> 
> Have patience!  You're on the bleeding edge here, literally.  :-)
> 
> While subversion itself is old and stable, svnsync is a brand new
> tool, *just* released a couple of weeks ago.  And googlecode is a
> brand new subversion service running a newly written repository-
> backend implementation.  I was able to use svnsync to push my own
> project's history up to googlecode, and therefore you should be
> able to as well.  However, bleeding edge is still bleeding edge...
> as you can see, we're discovering little snags and buglets here
> and there.  Thanks for being such a great tester!
>