Brett Cannon wrote:
> And any other problems people come across or questions they have about
> Subversion and its use, please do ask. I will try to start a new
> section in the dev FAQ for svn-specific issues.
Please integrate
http://www.python.org/dev/svn.html
(linked from 1.3 of devfaq.html)
[EMAIL PROTECTED] wrote:
> Can you let us know again the magic incantation to check out the source from
> the repository?
See
http://www.python.org/dev/svn.html
It's (say)
svn co svn+ssh://[EMAIL PROTECTED]/python/trunk/Misc
for read-write access, and
svn co http://svn.python.org/projects/pyt
Phillip J. Eby wrote:
> What will the procedure be for getting a login? I assume our SF logins
> won't simply be transferred/transferrable.
You should send your SSH2 public key along with your preferred logname
(firstname.lastname) to [EMAIL PROTECTED]
Regards,
Martin
__
On 10/18/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Martin> If people want to test the installation before the switch
> Martin> happens, this would be the time to do it.
>
> Martin,
>
> Can you let us know again the magic incantation to check out the source from
> the repository?
Martin> If people want to test the installation before the switch
Martin> happens, this would be the time to do it.
Martin,
Can you let us know again the magic incantation to check out the source from
the repository?
Thx,
Skip
___
Python-Dev
At 12:19 AM 10/19/2005 +0200, Martin v. Löwis wrote:
>If people want to test the installation before the switch happens,
>this would be the time to do it.
What will the procedure be for getting a login? I assume our SF logins
won't simply be transferred/transferrable.
__
AFAICT, everything is now setup to actually switch to subversion.
The infrastructure is complete, the conversion procedure is complete,
and Guido pronounced that the migration could happen.
One open issue is where to do the hosting: whether to pay a commercial
hosting company (i.e. wush.net), or w
On 07 March 2005, "Martin v. Löwis" said:
> OTOH, I wonder whether the distutils CVS needs to be converted at all,
> or whether it would be sufficient to only migrate the python "module"
> (in which case your approach would be sufficient).
The last time I looked (late 2000), there was useful conte
Greg Ward wrote:
Presumably for Python's repository, this would work:
cvs2svn -s /home/svn/python /home/cvs/python/python
...except, umm, isn't distutils a separate top-level directory in the
Python repository or something?
Ok. Removing the CVSROOT before the conversion (from CVS) or after
the c
Barry Warsaw wrote:
I personally have had no success doing this, but the last time I tried
was with a fairly old version of svn.
It gives an error message when you try. You then need to interpret the
error message, retry, and it gives you another error message. You do
this three times, and end up w
On Sun, 2005-03-06 at 14:16, "Martin v. Löwis" wrote:
> I don't know whether anybody has done this before,
> but I just tried to run cvs2svn on the Python repository.
> The conversion took 7 hours, and the result is now
> available at
>
> http://www.dcl.hpi.uni-potsdam.de/python/branches/
>
> Bec
On 06 March 2005, "Martin v. Löwis" said:
> - It has imported the CVSROOT directory as well. I don't
> know whether this is deliberate/useful.
This is just an artifact of how SourceForge CVS repositories are
organized. When I converted Optik's CVS to Subversion, I just did this:
cvs2svn -s /
I don't know whether anybody has done this before,
but I just tried to run cvs2svn on the Python repository.
The conversion took 7 hours, and the result is now
available at
http://www.dcl.hpi.uni-potsdam.de/python/branches/
Because of the load that the conversion produces on
the machine, I cannot r
13 matches
Mail list logo
