RE: [Axiom-developer] build-improvements on cygwin

[Page, Bill]

Ben,

We are having some problems again with our Axiom repository on
Google Code. I am copying you on the email below as background.
To make a long story short: I think we need to ask you to delete
the current repository and rebuild it again via 'svnadmin load'
as you did back on October 9 (see copy of your email below).

Since that time the size of the Axiom repository on SourceForge
has grown from 165MB to about 364M due to the creation of two
new branches. Even accounting for the larger storage factor at
Google (roughly double), I think this should still fit within
our current 750MB quota.

If you have any questions about this please ask. Also if you can
give us an update on the status of the problem which you mentioned
in October 9 message, that would be great.

Regards,
Bill Page.

On Tuesday, November 28, 2006 2:56 PM Waldek Hebisch wrote:
> 
> Bill Page wrote:
> ... 
> > But because of the space problems on Google I am not certain
> > that the Google versions of these are identical to the
> > SourceForge versions.
> > 
> 
> Google shows revision 214. It looks that we exceeded Google quota
> by creating 'silver'.
> 

Yes, I think that is correct. Here is my attempt at post mortem:

Up to revision 199 (October 26), the 'svk smerge' transactions from
the axiom-developer.org server that are intended to synchronize the
Google repository with the SourceForge repository were properly
processed by Google. For reasons that I don't understand, the svk
smerge process did not automatically create the correct branch
structure at Google when we created 'silver' on SVN SourceForge.

Revision 214 on Google was the last of several transactions starting
with Revision 200 (including some errors) which I submitted to try
to create /silver with has the same structure as on SourceForge.
I ran a separate svk smerge job to try to transfer the contents
of 'silver' from SourceForge to Google. Revisions 200-210 appeared
to work but still resulted in wrong name and structure due to my
errors. Revision 210 was dated Sat Oct 28 03:44:24 2006.

After that I received notices each day from my svk smerge job on
the axiom-developer.org server showing that the storage quota was
exceeded on Google.

On November 15 I submitted 4 more revisons 211 to 214 which corrected
my errors by renaming and deleting unused branches. But this did not
have any positive effect at Google. Update transactions are still
not be processed.

Now I no longer even get any commit messages from Google at all
although the svk smerge job is still running each night and shows
that the local Google mirror on axiom-developer.org is being updated
successfully. It is not clear to me why I no longer seeing commit
attempts - either Google is not processing them or 'svk sync' is no
longer sending them. I have even recreated the svk google mirror
repository on axiom-developer in an attempt to re-synch. This worked
as expected but still no commit transactions seem to be attempted
at Google.

------

So I think the problems definitely were caused by the creation of
'silver'. But because we only have svn commit access to Google and
no svnadmin privileges, it seems impossible to be to correct this
problem without the intervention of people at Google.

Regards,
Bill Page.


> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden 
> Sent: Wednesday, November 15, 2006 2:27 PM
> To: address@hidden
> Subject: [axiom commit] r214 - silver_old
> 
> Author: synthesis.anikast.ca
> Date: Wed Nov 15 10:40:08 2006
> New Revision: 214
> 
> Removed:
>    silver_old/
> 
> Log:
> not needed
> 

...

> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden 
> Sent: Friday, October 27, 2006 4:26 AM
> To: address@hidden
> Subject: [axiom commit] r200 - trunk2
> 
> Author: synthesis.anikast.ca
> Date: Fri Oct 27 01:25:47 2006
> New Revision: 200
> 
> Added:
>    trunk2/
> Modified:
>    /   (props changed)
> 
> Log:
> Create /trunk2
> 

 

> -----Original Message-----
> From: address@hidden 
> [mailto:address@hidden 
> Sent: Thursday, October 26, 2006 4:29 AM
> To: address@hidden
> Subject: [axiom commit] r199 - branches/build-improvements/src/interp
> 
> Author: synthesis.anikast.ca
> Date: Thu Oct 26 01:28:07 2006
> New Revision: 199
> 
> Modified:
>    /   (props changed)
>    branches/build-improvements/src/interp/ChangeLog.build-improvements
>    branches/build-improvements/src/interp/Makefile.in
>    branches/build-improvements/src/interp/Makefile.pamphlet
>    branches/build-improvements/src/interp/debugsys.lisp.pamphlet
> 
> Log:
> 
>         * debugsys.lisp.pamphlet (build-interpsys): Adjust pathname to
>         files that are local to the current build directory.
> 
>         * Makefile.pamphlet: Remove individual rules for making object
>         codes out of Boot pamphlet using bootsys.
>         (BOOT_TO_LISP, COMPILE_LISP): New.
>         (AXIOMsys_boot_sources): Likewise.  List core Boot files here.
>         (<<extract source codes>>): New chunk.  Abstract over special
>         individual rules to translate Boot to object code, using
>         bootsys.
>         * Makefile.in: Regenerate.


> -----Original Message-----
> From: Ben Collins-Sussman [mailto:address@hidden 
> Sent: October 9, 2006 2:14 PM
> To: address@hidden
> Cc: Gabriel Dos Reis; address@hidden
> Subject: Re: [Axiom-developer] RE: [M#73697383] Re: Disk-quota Request
> 
> 
> On 10/6/06, address@hidden
> <address@hidden> wrote:
> > Gabriel Dos Reis wrote:
> > > ...
> > > Can we get the 1G and be done with it?
> > >
> >
> > .. but then how would help debug the Google, svnsync, svk, and svn
> > programs? ;)
> >
> 
> Enough is enough.  You guys have been more than patient as 
> our guinea pigs!
> 
> I just rsync'd your sourceforge svn repository down to my local box
> (165MB), made a dumpfile from that, then did an 'svnadmin load' in our
> datacenter.  Disturbingly, it still took two hours to load the history
> and used up 381MB of space.  I don't know whether our size-counting
> code is buggy, or if our Bigtable storage schema is just really that
> bad, I'll be investigating.  It's not your problem.  :-)
> 
> You're now live... all 176 revisions are up and happy.  You're only
> using 381 of 750MB of quota, so you should be fine for a good while.
> 
> Let me know if you have any more problems.
> 
> (Remember, do an https:// checkout if you intend to commit changes;
> http:// checkouts produce read-only working copies.)
> 
>