root <[EMAIL PROTECTED]> writes:
| the checkout worked for me also, once i used the correct repository path.
this moment must be celebrated :-)
-- Gaby
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listin
the checkout worked for me also, once i used the correct repository path.
t
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
Doing:
[EMAIL PROTECTED]:~/sandbox$ svn co http://code.google.com/p/axiom/source
svn: PROPFIND request failed on '/p/axiom/source'
svn: PROPFIND of '/p/axiom/source': 400 Bad Request (http://code.google.com)
but this is not the address to the repository. Probably it was not
clear on previous ema
root <[EMAIL PROTECTED]> writes:
...
>> http://code.google.com/p/axiom/source
>
> My attempt to check out this code fails with:
>
> svn: PROPFIND request failed on /p/axiom/source
> svn: PROPFIND of '/p/axiom/source': 400 Bad Request (http://code.google.com)
I've had no problem with
# svn checkou
> > Does this mean that the Axiom sources are available from Google?
> > (I have been unable to use svn to check out from the silver repository
> > at Sourceforge for a while.) If so, how do you do it?
>
> http://code.google.com/p/axiom/source
My attempt to check out this code fails with:
svn:
http://code.google.com/p/axiom/source
Thanks; I'm getting it now. This should probably go in the wiki.
Could someone more familiar with the google repository add an entry on
http://wiki.axiom-developer.org/AxiomSources
I lost track.
And as the most important point, it should be stated how
I had fixed that in r75 under build-improvements. I guess, it is still
not in the trunk (Silver).
Ralf
On 10/10/2006 09:57 PM, Jay Belanger wrote:
http://code.google.com/p/axiom/source
Thanks; I'm getting it now.
This seems to have the old "unwritable .svn directories" problem.
_
>> http://code.google.com/p/axiom/source
>
> Thanks; I'm getting it now.
This seems to have the old "unwritable .svn directories" problem.
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-devel
"Bill Page" <[EMAIL PROTECTED]> writes:
> Quoting Jay Belanger <[EMAIL PROTECTED]>:
>
>> Does this mean that the Axiom sources are available from Google?
>> (I have been unable to use svn to check out from the silver repository
>> at Sourceforge for a while.) If so, how do you do it?
>
> http://
Quoting Jay Belanger <[EMAIL PROTECTED]>:
Does this mean that the Axiom sources are available from Google?
(I have been unable to use svn to check out from the silver repository
at Sourceforge for a while.) If so, how do you do it?
http://code.google.com/p/axiom/source
_
"Ben Collins-Sussman" <[EMAIL PROTECTED]> writes:
...
Does this mean that the Axiom sources are available from Google?
(I have been unable to use svn to check out from the silver repository
at Sourceforge for a while.) If so, how do you do it?
Jay
_
"Ben Collins-Sussman" <[EMAIL PROTECTED]> writes:
| On 10/6/06, [EMAIL PROTECTED]
| <[EMAIL PROTECTED]> 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? ;)
| >
|
On 10/6/06, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> 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
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? ;)
Regards,
Bill Page.
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.
[EMAIL PROTECTED] writes:
[...]
| This time I got this quota error message even though I have checked in
| advance that the resulting mirror is much smaller than 250 Mbytes when
| created locally via file:///. So maybe this time your quota program really
| is making a mistake?
Can we get the 1G
Ben,
I am away at a computer algebra meeting until Wednesday, so my email
might be a little less responsive than usual.
Unfortunately, after 72 of about 170 revisions, I got the following
message:
..
Copied properties for revision 72.
Committed revision 73.
Copied properties for revissvnsync: M
> You are the only one I know who would seriously think of keeping
> video in their *source code* control system! Of course it's a
> matter of perspective. What do we want to do with which tools?
Where the tutorial shows a picture and a bunch of words about
how to interact with hyperdoc you could
On 10/5/06, Bill Page <[EMAIL PROTECTED]> wrote:
When you say "integral part of the axiom src distribution" why
do you assume that it must be via subversion, cvs, Arch, etc.?
I think that's the central issue here. A version control system has
exactly one audience: developers. It's meant fo
Tim,
On October 5, 2006 11:08 AM you wrote:
> ...
> the 'src/video' directory will likely hold between a CD and
> a DVD worth of mini-tutorial topics. these can be added and
> deleted in small, section-sized segments as they get modified
> with better information. they will be an integral part of
On 10/5/06, root <[EMAIL PROTECTED]> wrote:
does it make sense to rely on a version control system that fails
to handle 20M files?
perhaps CVS/SVN needs a bit of redesign to handle the future.
Sorry, I think I was being unclear in my previous mail. I was trying to say:
1. CVS is badly desig
> > any system that considers 20M to be 'huge' needs a rethink.
> >
>
> The term "monstrously huge" is being used in a relative sense, i.e. 80
> megs of .zip files is big compared to a typical tree of source code.
>
> There's no limit to the size of files that can be uploaded/downloaded.
> It's
Ben,
>
> On October 4, 2006 10:12 PM you wrote:
>
> > Can we try two things:
> >
> > * try running sync a couple more times, see if it ever
> > successfuly commits r3.
> >
On October 5, 2006 9:10 AM I wrote:
>
> Ok.
>
Well, a little over an hour ago I did
$ nohup svnsync sync https://a
On 10/5/06, root <[EMAIL PROTECTED]> wrote:
any system that considers 20M to be 'huge' needs a rethink.
The term "monstrously huge" is being used in a relative sense, i.e. 80
megs of .zip files is big compared to a typical tree of source code.
There's no limit to the size of files that can b
> > Looking at your errors, I'm guessing that revision 3 of your
> > repository is some monstrously huge thing,
>
> It's big with a few monstrously huge files (the infamous zips
> directory).
monstrously huge?
the largest file in zips is 20M.
i have MS Word documents that big.
i regularly downloa
Ben,
On October 4, 2006 10:12 PM you wrote:
> ...
> Looking at your errors, I'm guessing that revision 3 of your
> repository is some monstrously huge thing,
It's big with a few monstrously huge files (the infamous zips
directory).
> and that it's taking hours to commit...
As I recall 'svk sme
On 10/4/06, Bill Page <[EMAIL PROTECTED]> wrote:
The problems that I have been having with svnsync seem more like
network/webserver issues than archive issues as such. This is the
same kind of problem that we have been having with SourceForge,
which makes we wonder about the quality and robustne
Gaby,
On October 4, 2006 6:19 PM you wrote:
>
> "Bill Page" <[EMAIL PROTECTED]> writes:
>
> [...]
>
> | 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
> | b
"Bill Page" <[EMAIL PROTECTED]> writes:
[...]
| 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.
10:46 AM
> To: [EMAIL PROTECTED]
> Cc: axiom-dev; Gabriel Dos Reis
> Subject: Re: [Axiom-developer] RE: [M#73697383] Re: Disk-quota
> Request
>
>
> On 10/3/06, Page, Bill <[EMAIL PROTECTED]> wrote:
> ...
> > svnsync: PROPFIND request failed on '/svn'
&g
On 10/3/06, Page, Bill <[EMAIL PROTECTED]> wrote:
I left the auth and the /svn.* directories in place (empty)
since the file dates indicated they had been created about
the time I first installed and used svn. I hopt that this
"surgery" was the right thing to do.
Yes, you did the right thing.
res
V 1
8
K 15
svn:realmstring
V 31
https://svn.sourceforge.net:443
END
[EMAIL PROTECTED] svn.ssl.server]$ ls
6dbbdbd4b65b578204189cb3a6f4b9ae dc5a395eac239ee84380e60694cec8f1
[EMAIL PROTECTED] svn.ssl.server]$ mv * ~
[EMAIL PROTECTED] svn.ssl.server]$ cd ~
-
> -Original Message-
Ben,
On Tuesday, October 03, 2006 10:48 PM you wrote:
> ...
> I just reset your repository.
>
Ok. Thanks.
> ...
> If you try again with svnsync, keep a careful transcript of
> everything you do.
Ok. I will.
> Do *not* use the --no-interactive switch. I want to see
> exactly how/when you g
On 10/3/06, Page, Bill <[EMAIL PROTECTED]> wrote:
PS. Surely there is some way to permit users to have more control
over their repositories without having to always be bothering the
"highly paid staff" ;) - a re-initialize repository button, perhaps?
Yeah, we're working on that feature. :-)
> [EMAIL PROTECTED] LatexWiki]# cd ~
> [EMAIL PROTECTED] ~]# cd /var/lib/zope/Products/LatexWiki
>
> The first one is a correction to the Maxima Lisp interface code.
sorry, i saw this posted by alfredo.
i guess it was while running from a doyen CD.
t
___
On Tuesday, October 03, 2006 8:33 PM Tim Daly wrote:
>
> I believe that Alfredo uses 'root'.
>
No Alfredo Portes uses 'doyenatccny' as his Google account.
And he has his own account on axiom-developer.org. I don't
see any connection with what I have been trying to do.
Regards,
Bill Page.
___
Bill,
I believe that Alfredo uses 'root'.
t
___
Axiom-developer mailing list
Axiom-developer@nongnu.org
http://lists.nongnu.org/mailman/listinfo/axiom-developer
Ben,
On Tuesday, October 03, 2006 8:22 PM you wrote:
> ...
> svn and svnsync are both 'official' svn clients, and thus both
> use the cached password in your ~/.subversion/auth/ area. So
> that's why your commits are working, no matter which of the two
> tools you're using. :-)
>
??? But, but
svk is a separate client from svn, it only uses the svn network protocol.
svn and svnsync are both 'official' svn clients, and thus both use the
cached password in your ~/.subversion/auth/ area. So that's why your
commits are working, no matter which of the two tools you're using.
:-)
On 10/3/
Ben,
Further note: SVK prompted me to enter my user id and password,
but svnsnch did not even bother. I have not idea why it choose
'root' since I was not logged in to axiom-developer.org as root.
Anyway...
On Tuesday, October 03, 2006 4:40 PM I wrote:
> ...
> So it seems I must repeat the 'svn
Ben,
On Tuesday, October 03, 2006 4:12 PM I wrote:
> ...
> My Google user id is 'synthesis.anikast.ca'. This is the
> user id that I am using when I perform the 'svnsynch'.
I am sorry, your comment prompted me to look at the commit
messages that were sent to my email address. The commits from
m
an [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 03, 2006 3:59 PM
> To: [EMAIL PROTECTED]
> Cc: axiom-dev; Gabriel Dos Reis
> Subject: Re: [Axiom-developer] RE: [M#73697383] Re: Disk-quota Request
>
> On 10/3/06, Page, Bill <[EMAIL PROTECTED]> wrote:
>
>
On 10/3/06, Page, Bill <[EMAIL PROTECTED]> wrote:
> svnsync: At least one property change failed; repository is
> unchanged
Sorry for not replying sooner. This error message simply means you
don't have permission to change all of the revision-properties on the
googlecode repository. You ne
c stopped.
>
> Do you have any idea what might have gone wrong?
>
> Regards,
> Bill Page.
>
>
> > -Original Message-
> > From: Ben Collins-Sussman [mailto:[EMAIL PROTECTED]
> > Sent: Monday, October 02, 2006 10:47 AM
> > To: Bill Page
>
TECTED]
> Sent: Monday, October 02, 2006 10:47 AM
> To: Bill Page
> Cc: axiom-dev; Gabriel Dos Reis
> Subject: Re: [Axiom-developer] RE: [M#73697383] Re: Disk-quota Request
>
> On 10/1/06, Bill Page <[EMAIL PROTECTED]> wrote:
>
> > Now, how do I use this at Google C
On 10/2/06, Bill Page <[EMAIL PROTECTED]> wrote:
The documentation of 'svnsync' refers to the mirror that it
constructs as "read-only". I presume that this means only that
there is no provision for two-way updating of the mirror via
this mechanism? So we would be free to commit changes at Google
On 10/1/06, Bill Page <[EMAIL PROTECTED]> wrote:
Now, how do I use this at Google Code?
svnsync can replicate any repository to any other, over any network
protocol. So you'd do something like:
# reset google repos to r0
# initialize google repos:
$ svnsync init https://axiom.googlecode.com
e some other method (e.g. svk smerge')
to maintain more than one copy of this archive. Right?
Thanks.
Bill Page.
> -Original Message-
> From: Bill Page [mailto:[EMAIL PROTECTED]
> Sent: October 1, 2006 2:17 PM
> To: 'Ben Collins-Sussman'
> Cc: 'axiom-d
> * Saying 'svn isn't ready for primetime' is mildly amusing to me. I'm
> one of subversion's original designers, and the system has been
> evolving for 6 years now. Apache, GCC, KDE, Gnome, Samba, and nearly
> every project started within the last 3 years uses it. Sourceforge
> and Google offer
Earlier I wrote:
>
> But the 'svnsync sync' command says:
>
> $ svnsync --non-interactive sync file:///home/page/axiom_sync
>
> svnsync: REPORT request failed on
> 'https://svn.sourceforge.net/svnroot/axiom'
> svnsync: The requested report is unknown.
> ...
Ok, the following worked, startin
On October 1, 2006 1:39 PM Gabriel Dos Reis wrote:
>
> On Sun, 1 Oct 2006, Bill Page wrote:
>
> | that using subversion with the Axiom project is a viable. To a
> | first time user like me who has previous experience with a tool
> | like darcs, subversion seems overly complicated, especially when
On Sun, 1 Oct 2006, Bill Page wrote:
| that using subversion with the Axiom project is a viable. To a
| first time user like me who has previous experience with a tool
| like darcs, subversion seems overly complicated, especially when
| SVK is layered on top.
Hmm, I find SVK an excellent interfac
Ben,
On October 1, 2006 9:26 AM you wrote:
>
> On 9/30/06, Bill Page wrote:
>
> > So this confirms that 'svk smerge' does not re-create the
> > repository in the same compact form in which it exists on
> > SourceForge. :-(
> >
>
> Another experiment you can try: subversion 1.4 now ships with a
On 9/30/06, Bill Page <[EMAIL PROTECTED]> wrote:
So this confirms that 'svk smerge' does not re-create the repository
in the same compact form in which it exists on SourceForge. :-(
Another experiment you can try: subversion 1.4 now ships with a
mirroring tool called 'svnsync'. Try using 's
root <[EMAIL PROTECTED]> writes:
[...]
| Plus if you apt-get GCL you might get a version from stable,
| unstable, or testing. Yet GCL-2.6.8pre only works on some
| systems and GCL-2.6.8pre2 only works on others and there is
| no build-time way to distinguish them. Nor is there a tag
| so you can'
On September 30, 2006 10:34 PM Gaby wrote:
>
> Bill Page writes:
>
> [...]
>
> | No they don't work for every user - just 95% of them.
>
> Where do you get that from?
>
It was a rhetorical statement with no basis in fact. I have no
idea if it is true or not or even how to find out. Sorry.
B
Ben,
On September 30, 2006 6:22 PM you wrote:
>
> On 9/30/06, Bill Page wrote:
>
> > The complete svn repository on SourceForge is only 233,248 Kb.
> > It should have fit on Google!
>
> Google Guy Here. :-)
>
Thank you very much for your reply and your suggestion below.
> Can you do me a fa
[ I removed Ben from the CC: list because I don't think he really want
to get into our internal issues. ]
"Bill Page" <[EMAIL PROTECTED]> writes:
[...]
| No they don't work for every user - just 95% of them.
Where do you get that from?
-- Gaby
__
On September 30, 2006 9:17 PM Tim Daly wrote:
> Bill Page wrote:
>
> > PS. On a related issue. The more I think about the 'zips'
> > directory in the Axiom distribution the more I think it
> > was a ReallyStupid (tm) invention. Why take a source code
> > tarball from another project (gcl) and sti
On Sat, 30 Sep 2006, root wrote:
| Part of your frustration seems to be coming from SVN. I'm using
| SVN in work and it 'locks' the source tree, insists I run 'cleanup'
| (which NEVER works), and forces me to unwind changes, blow away my
| source tree, refetch the repository, re-apply my changes,
> PS. On a related issue. The more I think about the 'zips'
> directory in the Axiom distribution the more I think it was a
> ReallyStupid (tm) invention. Why take a source code tarball from
> another project (gcl) and stick it into the Axiom repository?
I see your 'reasons' cache has expired agai
On Sat, 30 Sep 2006, Bill Page wrote:
| PS. On a related issue. The more I think about the 'zips'
| directory in the Axiom distribution the more I think it was a
| ReallyStupid (tm) invention. Why take a source code tarball from
| another project (gcl) and stick it into the Axiom repository?
| If
On 9/30/06, Bill Page <[EMAIL PROTECTED]> wrote:
The complete svn repository on SourceForge is only 233,248 Kb.
It should have fit on Google!
Google Guy Here. :-)
Can you do me a favor? Can you try using svk to 'push' your
repository to some other local repository (in the same way you're
pu
Gaby,
On September 29, 2006 4:10 PM you wrote:
>
> On Fri, 29 Sep 2006, Bill Page wrote:
>
> | On September 29, 2006 8:19 AM Ben Collins-Sussman wrote:
> | >
> | > Yes, this is definitely a client-side error. When the svn client
> | > sends a file to the server (during a commit), it uses xdelta
Thanks for the explanation. Our service providers has modified
the configuration of /tmp on our server to provide more space
and the 'svk smerge' command is now working happy apparently
re-creating the Axiom subversion repository on Google in the
expected manner. :-)
Good to hear Bill. :-) If ev
On Fri, 29 Sep 2006, Bill Page wrote:
| On September 29, 2006 8:19 AM Ben Collins-Sussman wrote:
| >
| > Yes, this is definitely a client-side error. When the svn client
| > sends a file to the server (during a commit), it uses xdelta to
| > diff-encode the data into a temporary file, then the ne
On September 29, 2006 8:19 AM Ben Collins-Sussman wrote:
>
> Yes, this is definitely a client-side error. When the svn client
> sends a file to the server (during a commit), it uses xdelta to
> diff-encode the data into a temporary file, then the neon library
> (an http client library) pushes the
Yes, this is definitely a client-side error. When the svn client
sends a file to the server (during a commit), it uses xdelta to
diff-encode the data into a temporary file, then the neon library (an
http client library) pushes the tmpfile over the wire.
As an experiment, you might want to create
On Thursday, September 28, 2006 7:13 PM I wrote:
>
> After several attempts using SVK, first trying the mirroring
> method that I mentioned earlier, and then later using just a
> simple 'commit' of the most recent revision of trunk from
> the Axiom Silver, the result is the same error message:
>
Alfredo, Gaby, et al.
On Thursday, September 28, 2006 10:49 AM Alfredo Portes wrote:
>
> This is an email sent by Ben Collins from Google. The
> repository has been reseted.
>
> Let me know please if it works fine.
>
Unfortunately it does not work. :(
After several attempts using SVK, first t
69 matches
Mail list logo
