zsh has migrated cvs -> zsh

zsh has migrated cvs -> zsh

[Phil Pennock]

The rest of the details are in an old thread, possibly skipped by folks,
so I'm going to try to gather the details here into one, hopefully
clear, email.

1. The trigger was pulled.  zsh now uses git.

2. CVS is dead.  "cvs up" will fail.  "/cvsroot/zsh/zsh" is not on the
   server.

3. On the CVS server, the old zsh content is now in a directory
   "zsh-OLD-DIR-USE-GIT" which is not inside the normal module, thus the
   death above.  So you can still get to the content.

4. git clone git://git.code.sf.net/p/zsh/code
   git remote set-url --push origin ssh://${SFUSER}@git.code.sf.net/p/zsh/code

That's the core of it.

If you have set up ~/.ssh/config to set "User" automatically, then you
can just use simpler URLs that can be shared and used by others.
Alternatively, you can remap the URLs in your ~/.gitconfig; I've
included examples of both of these, for user "fredbloggs1", below.
I use the ~/.ssh/config approach, myself.

 Code:    ssh://git.code.sf.net/p/zsh/code
 Website: ssh://git.code.sf.net/p/zsh/web

Kudos to Wayne, Frank and Aaron for doing the work of switching,
handling patchlevel, and so on.

Dear ${deity} it's so nice to have a fast SCM "log" command.

Regards,
-Phil

Example ~/.ssh/config setting:
----------------------------8< cut here >8------------------------------
Host *.sf.net *.sourceforge.net
	User fredbloggs1
	ForwardAgent no
	ForwardX11 no
	GSSAPIAuthentication no
----------------------------8< cut here >8------------------------------

Example ~/.gitconfig setting:
----------------------------8< cut here >8------------------------------
[url "ssh://fredbloggs1@git.code.sf.net"]
	insteadOf = git://git.code.sf.net
	insteadOf = ssh://git.code.sf.net
----------------------------8< cut here >8------------------------------

Re: zsh has migrated cvs -> zsh

[Greg Klanderman]

>>>>> On April 3, 2013 Phil Pennock <zsh-workers+phil.pennock@spodhuis.org> wrote:

> 4. git clone git://git.code.sf.net/p/zsh/code
>    git remote set-url --push origin ssh://${SFUSER}@git.code.sf.net/p/zsh/code

Hi Phil,

Do I need a sourceforge username if I just want a read-only checkout
like I got with cvs :pserver:?

Greg

Re: zsh has migrated cvs -> zsh

[Aaron Schrab]

At 09:21 -0400 04 Apr 2013, Greg Klanderman <gak@klanderman.net> wrote:
>>>>>> On April 3, 2013 Phil Pennock <zsh-workers+phil.pennock@spodhuis.org> wrote:
>
>> 4. git clone git://git.code.sf.net/p/zsh/code
>>    git remote set-url --push origin ssh://${SFUSER}@git.code.sf.net/p/zsh/code
>
>Hi Phil,
>
>Do I need a sourceforge username if I just want a read-only checkout
>like I got with cvs :pserver:?

For a read-only checkout you can skip the second command above, that's 
only needed to allow pushing to the repository.  The reason that is 
needed is that the URL used for cloning and fetching from the repository 
doesn't do any authentication.

So, no, you do NOT need to have a sourceforge account to checkout the 
git repository.

Re: zsh has migrated cvs -> zsh

[Simon Ruderich]

[-- Attachment #1: Type: text/plain, Size: 610 bytes --]

On Thu, Apr 04, 2013 at 09:21:58AM -0400, Greg Klanderman wrote:
>> 4. git clone git://git.code.sf.net/p/zsh/code
>>    git remote set-url --push origin ssh://${SFUSER}@git.code.sf.net/p/zsh/code
>
> Hi Phil,
>
> Do I need a sourceforge username if I just want a read-only checkout
> like I got with cvs :pserver:?

Hi Greg,

The second line is optional and only relevant if you want to push
commits to the Git repository. For a read-only checkout the first
line is all you need.

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: zsh has migrated cvs -> zsh

[Peter Stephenson]

We should probably change the main web page to note this (the old NEWS
here is well out of date).  This is mostly a simple summary for
non-developers; developers should be reading this list.  Even so, I
imagine it can be improved (my use of <pre> tags has always been a bit
rough and ready).  Then a corresponding Sourceforge NEWS item can be
added.

diff --git a/index.html b/index.html
index d54383d..f5b9576 100644
--- a/index.html
+++ b/index.html
@@ -85,14 +85,12 @@ read something that has been polished by a professional editor you can
 <a href="http://www.amazon.com/exec/obidos/tg/detail/-/1590593766/"/>buy
 the book</a>.
 
-<p><b>NEWS</b>: Those parts of the zsh project
-that were hosted at <a href="http://dotsrc.org">dotsrc.org</a> will
-be moving to new homes.  In particular the mailing lists have
-transferred to <tt>zsh.org</tt> from <tt>sunsite.dk</tt>.
-Existing subscribers have been automatically moved, but not
-all documentation has yet been updated.
-The version of the web site at Sourceforge is now the master.</p>
+<p><b>NEWS</b>: CVS has been replaced by git as the archive tool
+for source code and web pages.  For the source code,
 
+<pre>git clone git://git.code.sf.net/p/zsh/code</pre>
+
+or use <tt>https</tt> or <tt>ssh</tt> access where necessary.</p>
 
 <P>
 <hr size=2 noshade>

pws

Re: zsh has migrated cvs -> zsh

[Peter Stephenson]

On Thu, 04 Apr 2013 16:39:55 +0100
Peter Stephenson <p.stephenson@samsung.com> wrote:
> We should probably change the main web page to note this (the old NEWS
> here is well out of date).  This is mostly a simple summary for
> non-developers; developers should be reading this list.

I've pushed this; not sure if it gets any further automatically at the
moment.  Feel free to tweak further.

pws

Re: zsh has migrated cvs -> zsh

[Simon Ruderich]

[-- Attachment #1: Type: text/plain, Size: 574 bytes --]

On Fri, Apr 05, 2013 at 09:45:34AM +0100, Peter Stephenson wrote:
> I've pushed this; not sure if it gets any further automatically at the
> moment.  Feel free to tweak further.

Looks good.

What do you mean with "gets any further automatically"?

I've updated the website to remove the remaining references to
CVS, added a link to the website Git repository and fixed some
broken prev/next buttons [1].

Regards
Simon

[1]: http://sourceforge.net/p/zsh/web/
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: zsh has migrated cvs -> zsh

[Peter Stephenson]

On Fri, 05 Apr 2013 16:21:44 +0200
Simon Ruderich <simon@ruderich.org> wrote:
> What do you mean with "gets any further automatically"?
> 
> I've updated the website to remove the remaining references to
> CVS, added a link to the website Git repository and fixed some
> broken prev/next buttons [1].

I think you've just said it does now propagate to the web site itself
automatically, thanks.

pws

Re: zsh has migrated cvs -> zsh

[Simon Ruderich]

[-- Attachment #1: Type: text/plain, Size: 442 bytes --]

On Fri, Apr 05, 2013 at 03:45:08PM +0100, Peter Stephenson wrote:
> I think you've just said it does now propagate to the web site itself
> automatically, thanks.

No, AFAIK the website stills needs to be rsynced manually after
committing the changes in Git. I'm not sure if there's a way to
automate it (hooks maybe).

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: zsh has migrated cvs -> zsh

[Peter Stephenson]

On Fri, 05 Apr 2013 17:59:22 +0200
Simon Ruderich <simon@ruderich.org> wrote:
> No, AFAIK the website stills needs to be rsynced manually after
> committing the changes in Git. I'm not sure if there's a way to
> automate it (hooks maybe).

Sounds like that probably ought to be a straightforward job for someone
who knows git, assuming we've got a checkout on the server that can be
rsync'd.

pws

Re: zsh has migrated cvs -> zsh

[Simon Ruderich]

[-- Attachment #1: Type: text/plain, Size: 493 bytes --]

On Fri, Apr 05, 2013 at 03:45:08PM +0100, Peter Stephenson wrote:
> I think you've just said it does now propagate to the web site itself
> automatically, thanks.

Ah, sorry. I meant the patch looks good. The change still need to
be rsynced manually.

I've committed a short README which documents the necessary
commands [1].

Regards
Simon

[1]: http://zsh.sourceforge.net/README
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: zsh has migrated cvs -> zsh

[Simon Ruderich]

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

On Fri, Apr 05, 2013 at 05:10:58PM +0100, Peter Stephenson wrote:
> On Fri, 05 Apr 2013 17:59:22 +0200 Simon Ruderich wrote:
>> No, AFAIK the website stills needs to be rsynced manually after
>> committing the changes in Git. I'm not sure if there's a way to
>> automate it (hooks maybe).
>
> Sounds like that probably ought to be a straightforward job for someone
> who knows git, assuming we've got a checkout on the server that can be
> rsync'd.

Shouldn't be too difficult, but I don't know if there's a
checkout on the server or if Sourceforge has any tools for this
task.

Wayne, do you know if Sourceforge has any deployment tools for
Git and the website? If it can be accomplished without too much
trouble it would be useful. But rsyncing manually isn't very
complicated either - and we don't update the website too often.

Regards
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: zsh has migrated cvs -> zsh

[Greg Klanderman]

>>>>> On April 4, 2013 Simon Ruderich <simon@ruderich.org> wrote:

> The second line is optional and only relevant if you want to push
> commits to the Git repository. For a read-only checkout the first
> line is all you need.

>>>>> On April 4, 2013 Aaron Schrab <aaron@schrab.com> wrote:

> For a read-only checkout you can skip the second command above, that's only
> needed to allow pushing to the repository.  The reason that is needed is that
> the URL used for cloning and fetching from the repository doesn't do any
> authentication.

> So, no, you do NOT need to have a sourceforge account to checkout the git
> repository.

Thank you Simon and Aaron, that worked perfectly.

Greg