further pypy repo migrations
hi all, i'd like to continue consolidation of PyPy repositories (and more generally pypy services but that in a separate mail). Thanks to Ronny Pfannschmidt, sponsorship from merlinux (my company), and work from Armin, Anto and others the main PyPy development repository has been migrated to mercurial on Bitbucket. Btw, we just asked and Bitbucket nicely upgraded the PyPy project account to become an unlimited one, thanks! Now we still have some more repositories on codespeak svn. One is "extradoc" which contains a lot of talk, sprint, misc infos and the "pypy.org" website content. We can either move this wholesale to an "extradoc" one on bitbucket or split it maybe into "pypy.org" and "extradoc". Note that the old codespeak.net subversion URLs will remain valid for quite some time so any cleanup/removal of dirs should better happen in the new mercurial repo. Another repo is "pypy-z", maybe not known to most. It is a repository where core project members keep information about more internal bits, like our previous contracts with Google, the European Union and some un-named entities (ask your favourite PSU representative for more info). I suggest we move this to become a "private" mercurial repo on bitbucket. Any more pypy related repositories that need migration or any notes/comments? best holger --
On 17/02/11 15:23, holger krekel wrote:
Thanks to Ronny Pfannschmidt, sponsorship from merlinux (my company), and work from Armin, Anto and others the main PyPy development repository has been migrated to mercurial on Bitbucket. Btw, we just asked and Bitbucket nicely upgraded the PyPy project account to become an unlimited one, thanks!
just to clarify: "unlimited account" means that we can have private repositories with as many users as we want (which is what we needed for pypy-z). Thanks to Bitbucket also from my side :-)
Any more pypy related repositories that need migration or any notes/comments?
currently, pypy has three svn subrepos which live on codespeak: greenlet = [svn]http://codespeak.net/svn/greenlet/trunk/c testrunner = [svn]http://codespeak.net/svn/pypy/build/testrunner lib_pypy/pyrepl = [svn]http://codespeak.net/svn/pyrepl/trunk/pyrepl/pyrepl we will need to migrate those as well at some point, and probably make them mercurial subrepositories instead of svn ones. ciao, Anto
On 2/17/11 3:48 PM, Antonio Cuni wrote:
On 17/02/11 15:23, holger krekel wrote:
Thanks to Ronny Pfannschmidt, sponsorship from merlinux (my company), and work from Armin, Anto and others the main PyPy development repository has been migrated to mercurial on Bitbucket. Btw, we just asked and Bitbucket nicely upgraded the PyPy project account to become an unlimited one, thanks! just to clarify: "unlimited account" means that we can have private repositories with as many users as we want (which is what we needed for pypy-z). Thanks to Bitbucket also from my side :-)
Any more pypy related repositories that need migration or any notes/comments? currently, pypy has three svn subrepos which live on codespeak:
greenlet = [svn]http://codespeak.net/svn/greenlet/trunk/c testrunner = [svn]http://codespeak.net/svn/pypy/build/testrunner lib_pypy/pyrepl = [svn]http://codespeak.net/svn/pyrepl/trunk/pyrepl/pyrepl
we will need to migrate those as well at some point, and probably make them mercurial subrepositories instead of svn ones.
ciao, Anto _______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
Hi folks, if it helps, then I can offer to build a repos or website on my machine. I have a big machine with plenty of resources, which are only little used. Maybe for something that doesn't fit bitbucket very well, or as a mirror site, whatever makes sense. Right now I'm hosting starship.python.net and stackless.com as virtual machines, plus some experimental hidden servers. I'd be happy to donate an OpenVZ Debian server of reasonable size. Just let me know. cheers - chris -- Christian Tismer :^)<mailto:tismer@stackless.com> tismerysoft GmbH : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/
On 02/17/2011 03:23 PM, holger krekel wrote:
i'd like to continue consolidation of PyPy repositories (and more generally pypy services but that in a separate mail).
Thanks to Ronny Pfannschmidt, sponsorship from merlinux (my company), and work from Armin, Anto and others the main PyPy development repository has been migrated to mercurial on Bitbucket. Btw, we just asked and Bitbucket nicely upgraded the PyPy project account to become an unlimited one, thanks!
Now we still have some more repositories on codespeak svn. One is "extradoc" which contains a lot of talk, sprint, misc infos and the "pypy.org" website content. We can either move this wholesale to an "extradoc" one on bitbucket or split it maybe into "pypy.org" and "extradoc". Note that the old codespeak.net subversion URLs will remain valid for quite some time so any cleanup/removal of dirs should better happen in the new mercurial repo.
Another repo is "pypy-z", maybe not known to most. It is a repository where core project members keep information about more internal bits, like our previous contracts with Google, the European Union and some un-named entities (ask your favourite PSU representative for more info). I suggest we move this to become a "private" mercurial repo on bitbucket.
Any more pypy related repositories that need migration or any notes/comments?
There are also the repos in svn/pypy/lang that would need conversion. At least the Smalltalk one has branches in its history, maybe it's not important to keep the precise branch history though. Another consideration I have is that we have been handing out external pointers into our repositories from various places, e.g. from our blog posts and also in some papers. I don't see an easy solution to keep them valid, which is a bit of a pity. Cheers, Carl Friedrich
On Monday, February 21, 2011 at 9:12 AM, Carl Friedrich Bolz wrote: On 02/17/2011 03:23 PM, holger krekel wrote:
i'd like to continue consolidation of PyPy repositories (and more generally pypy services but that in a separate mail).
Thanks to Ronny Pfannschmidt, sponsorship from merlinux (my company), and work from Armin, Anto and others the main PyPy development repository has been migrated to mercurial on Bitbucket. Btw, we just asked and Bitbucket nicely upgraded the PyPy project account to become an unlimited one, thanks!
Now we still have some more repositories on codespeak svn. One is "extradoc" which contains a lot of talk, sprint, misc infos and the "pypy.org" website content. We can either move this wholesale to an "extradoc" one on bitbucket or split it maybe into "pypy.org" and "extradoc". Note that the old codespeak.net subversion URLs will remain valid for quite some time so any cleanup/removal of dirs should better happen in the new mercurial repo.
Another repo is "pypy-z", maybe not known to most. It is a repository where core project members keep information about more internal bits, like our previous contracts with Google, the European Union and some un-named entities (ask your favourite PSU representative for more info). I suggest we move this to become a "private" mercurial repo on bitbucket.
Any more pypy related repositories that need migration or any notes/comments?
There are also the repos in svn/pypy/lang that would need conversion. At least the Smalltalk one has branches in its history, maybe it's not important to keep the precise branch history though.
Another consideration I have is that we have been handing out external pointers into our repositories from various places, e.g. from our blog posts and also in some papers. I don't see an easy solution to keep them valid, which is a bit of a pity. I'd be happy to write a forwarding application that can redirect any requests to the codespeak svn. This would allow the group to move these additional repositories to bitbucket, but not break existing links. With a good url mapping, this application could serve to forward most codespeak projects beyond pypy, which might be enticing for the codespeak admins. The application is fairly simple, so let me know if there is interest and I'll finish up the preliminary code that I've got done now.
--Dan
Hi Dan, On 02/22/2011 03:39 AM, Dan Colish wrote:
I'd be happy to write a forwarding application that can redirect any requests to the codespeak svn. This would allow the group to move these additional repositories to bitbucket, but not break existing links. With a good url mapping, this application could serve to forward most codespeak projects beyond pypy, which might be enticing for the codespeak admins. The application is fairly simple, so let me know if there is interest and I'll finish up the preliminary code that I've got done now.
That sounds very cool. I have no clue how that would be integrated in whatever codespeak is going to end up being. Carl Friedrich
On Tuesday, February 22, 2011 at 9:48 AM, Carl Friedrich Bolz wrote: Hi Dan,
On 02/22/2011 03:39 AM, Dan Colish wrote:
I'd be happy to write a forwarding application that can redirect any requests to the codespeak svn. This would allow the group to move these additional repositories to bitbucket, but not break existing links. With a good url mapping, this application could serve to forward most codespeak projects beyond pypy, which might be enticing for the codespeak admins. The application is fairly simple, so let me know if there is interest and I'll finish up the preliminary code that I've got done now.
That sounds very cool. I have no clue how that would be integrated in whatever codespeak is going to end up being.
Who can I contact at codespeak to begin a discussion on integrating this bouncer application? I've got a working draft that seems to do the trick up on bitbucket now, so I think I can grind this bit of the migration out pretty quickly. --Dan
Just a quick update, I've sketched out a working bouncer for just the pypy svn trunk. Its living here for now: https://gist.github.com/838189 -- Dan
Errr, sorry I lied. The code's here https://bitbucket.org/dcolish/pypy-bouncer. There were a few more files that made it worth getting into a proper vcs repo. -- Dan
On Mon, Feb 21, 2011 at 18:12 +0100, Carl Friedrich Bolz wrote:
On 02/17/2011 03:23 PM, holger krekel wrote:
There are also the repos in svn/pypy/lang that would need conversion. At least the Smalltalk one has branches in its history, maybe it's not important to keep the precise branch history though.
OK, thanks for pointing out.
Another consideration I have is that we have been handing out external pointers into our repositories from various places, e.g. from our blog posts and also in some papers. I don't see an easy solution to keep them valid, which is a bit of a pity.
As posted earlier i plan to keep a read-only version of the svn repo around. We could degrade this to statically serving files or maybe use Dan's forwarder. best, holger
participants (5)
-
Antonio Cuni -
Carl Friedrich Bolz -
Christian Tismer -
Dan Colish -
holger krekel