CVS repository down

CVS repository down

[Peter Stephenson]

http://apps.sourceforge.net/wordpress/sourceforge/  says this:

2009-03-10: Service CVS unplanned downtime
March 10th, 2009

CVS repositories that begin with the letters (a e h i m o r w z) are
experiencing unplanned downtime since 2009-03-10 18:00 UTC.
SourceForge.net staff are actively working to resolve the issue and
anticipate having the service returned sometime in the next 2
days. Questions or concerns may be directed to us by Support Request.


-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070

Re: CVS repository down

[Phil Pennock]

On 2009-03-11 at 10:13 +0000, Peter Stephenson wrote:
> http://apps.sourceforge.net/wordpress/sourceforge/  says this:
> 
> 2009-03-10: Service CVS unplanned downtime
> March 10th, 2009
> 
> CVS repositories that begin with the letters (a e h i m o r w z) are
> experiencing unplanned downtime since 2009-03-10 18:00 UTC.
> SourceForge.net staff are actively working to resolve the issue and
> anticipate having the service returned sometime in the next 2
> days. Questions or concerns may be directed to us by Support Request.

In case this proves to be more catastrophic than suggested:

I rsync the SF CVS repository periodically to local, so I'm not waiting
on SF for sync's (it's gotten better though, IIRC) and to let me run
local repository browsing tools.  That's the full CVS repository, not a
check-out.

Looks like I last rsync'd on Feb 28th.  Most recent change I have is:

----------------------------8< cut here >8------------------------------
2009-02-28  Clint Adams  <clint@zsh.org>

        * Daniel Friesel: 26636: Completion/X/Command/_mplayer: complete
        .flac files for mplayer.
----------------------------8< cut here >8------------------------------

If things head further south, shout and I'll sort out a way for you to
recover this "backup".  du(1) says:
 27M    CVSROOT
 30M    zsh
where almost all of CVSROOT/ is the "history" file which compresses down
to 6% of the original size.

-Phil

Re: CVS repository down

[Mikael Magnusson]

2009/3/11 Peter Stephenson <pws@csr.com>:
> http://apps.sourceforge.net/wordpress/sourceforge/  says this:
>
> 2009-03-10: Service CVS unplanned downtime
> March 10th, 2009
>
> CVS repositories that begin with the letters (a e h i m o r w z) are
> experiencing unplanned downtime since 2009-03-10 18:00 UTC.
> SourceForge.net staff are actively working to resolve the issue and
> anticipate having the service returned sometime in the next 2
> days. Questions or concerns may be directed to us by Support Request.

If someone wants to get the source before sf has their stuff fixed,
you can clone it from one of the git repos that have imported cvs. I
have one here:
git clone git://git.mika.l3ib.org/zsh-cvs.git
and there is one at
git clone git://repo.or.cz/zsh.git

-- 
Mikael Magnusson


(if you don't want the full history you can save about 3MB (out of
10MB) of transfer by giving --depth=1, or 7.5MB by doing (in a new
dir)
git init
git remote add origin git://theuri
git fetch --depth=1 origin master:refs/remotes/origin/master
git merge origin/master
)

Re: CVS repository down

[Wayne Davison]

On Wed, Mar 11, 2009 at 11:31:09AM +0100, Mikael Magnusson wrote:
> and there is one at
> git clone git://repo.or.cz/zsh.git

I pushed that one to sourceforge, just in case folks want to try out
the SF git support.  It's not enabled (user-visible) on the project,
but folks can clone/push/pull using it, if you want to give it a go:

    git://zsh.git.sf.net/gitroot/zsh            (read-only)
    ssh://USERNAME@zsh.git.sf.net/gitroot/zsh   (read/write)

..wayne..

Re: CVS repository down

[Frank Terbeck]

Wayne Davison <wayned@users.sourceforge.net>:
> Mikael Magnusson wrote:
> > git clone git://repo.or.cz/zsh.git
> 
> I pushed that one to sourceforge [...]

That is a clone of Clint's cvs-to-git conversion from git.debian.org.
He uses tailor¹ to perform the conversion. It seems that tailor gets
confused here and there, as it quite often creates two (sometimes even
three) git commits per cvs commit.

[snip]
(6086)-/tmp/zsh [master]-% git log -12 | git shortlog
pws (12):
      add whole-path style to _perforce completer
      add whole-path style to _perforce completer
      unposted: fix definition of _perforce_whole_path in 26690
      unposted: fix definition of _perforce_whole_path in 26690
      26697: test for Linux- and Mac-style xattr functions
      derf@sievert.tabularazor.org: 26701: new devtodo completion
      derf@sievert.tabularazor.org: 26701: new devtodo completion
      26072: lexsave()/lexrestore() to fix bug with sourcing from "funny" places
      26072: lexsave()/lexrestore() to fix bug with sourcing from "funny" places
      26705: multibyte characters with Meta in ${(%)foo} etc.
      26705: multibyte characters with Meta in ${(%)foo} etc.
      print message if we give up trying to crate a lock file with hard links
[snap]

I think Clint chose tailor, because at the time 'git cvsimport' failed
to import the zsh repository. That however, isn't the case anymore.
And the history created by 'git cvsimport' seems to be a lot more
consistent with cvs's history.

To import the cvs repository into a git repository, the following
script may be used:

[snip]
#!/bin/sh

PROJECT='zsh'
MODULE='zsh'
DESTINATION="/usr/src/${PROJECT}.git"
AUTHORS="/usr/src/${PROJECT}-authors.txt"
CVS="/usr/src/mirror/${PROJECT}-cvs"
RSYNCURI="rsync://${PROJECT}.cvs.sourceforge.net/cvsroot/${PROJECT}"

[ ! -d "${CVS}" ] && { mkdir -p "${CVS}" || { printf 'Could not create %s.\n' "${CVS}" && exit 1 ; } ; }
(cd "${CVS}"; rsync -av "${RSYNCURI}/*" .)

if [ -f "${AUTHORS}" ] ; then
    git cvsimport -v -k -s- -a -u -A "${AUTHORS}" -C "${DESTINATION}" -d"${CVS}" "${MODULE}"
else
    git cvsimport -v -k -s- -a -u -C "${DESTINATION}" -d"${CVS}" "${MODULE}"
fi
[snap]

If you create a file that describes the cvs-usernames a little
further, git will transform that to "User Name <e@mail.tld>" - which
is the common format when using git.

If the script above is unchanged, such a file would be named
/usr/src/zsh-authors.txt and it would look like this:

[snip]
pws=Peter Stephenson <pws@foo.tld>
barts=Bart Schaefer <schaefer@somewhereelse.tld>
[snap]

And so on...

The initial import takes about 40 minutes on my really not up to date
laptop. After that you got a clean history in git, too.

Regards, Frank

¹ <http://progetti.arstecnica.it/tailor>

-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925

Re: CVS repository down

[Frank Terbeck]

Frank Terbeck <ft@bewatermyfriend.org>:
[...]
> To import the cvs repository into a git repository, the following
> script may be used:

I forgot to mention that the script can be used to incrementally
update the import, too. No need to go through the forty minute initial
import each time. :)

Regards, Frank

-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925

Re: CVS repository down

[Wayne Davison]

On Thu, Mar 12, 2009 at 01:06:44PM +0100, Frank Terbeck wrote:
> That is a clone of Clint's cvs-to-git conversion from git.debian.org.
> He uses tailor¹ to perform the conversion. It seems that tailor gets
> confused here and there, as it quite often creates two (sometimes even
> three) git commits per cvs commit.

Thanks for the info.  I've created a repo with all authors defined as
their USERNAME@users.sourceforge.net email (which is what SF recommends
be used for git commits).  This repo looks much better.  I can set
something up to keep it updated from CVS in the future.

..wayne..

Re: CVS repository down

[Frank Terbeck]

Wayne Davison <wayned@users.sourceforge.net>:
> On Thu, Mar 12, 2009 at 01:06:44PM +0100, Frank Terbeck wrote:
> > That is a clone of Clint's cvs-to-git conversion from git.debian.org.
> > He uses tailor¹ to perform the conversion. It seems that tailor gets
> > confused here and there, as it quite often creates two (sometimes even
> > three) git commits per cvs commit.
> 
> Thanks for the info.  I've created a repo with all authors defined as
> their USERNAME@users.sourceforge.net email (which is what SF recommends
> be used for git commits).  This repo looks much better.  I can set
> something up to keep it updated from CVS in the future.

If it matters: I would like that very much. :)

Regards, Frank

-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925