[Xmltv-devel] CVS down

[Robert Eden]

FYI.. the Sourceforge CVS servers are down.

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

Robert

[Nick Morrott]

Post by Robert Eden
FYI.. the Sourceforge CVS servers are down.
http://sourceforge.net/apps/wordpress/sourceforge/

Having read some of the recent SF staff posts regarding turning off
the CVS service in the near future, should we start discussing whether
we should move to SVN or git sooner rather than later?

I note the CVS service is still down - hope it's back up soon.

Cheers,
Nick

[Robert Eden]

Post by Nick Morrott

Post by Robert Eden
FYI.. the Sourceforge CVS servers are down.
http://sourceforge.net/apps/wordpress/sourceforge/

Having read some of the recent SF staff posts regarding turning off
the CVS service in the near future, should we start discussing whether
we should move to SVN or git sooner rather than later?
I note the CVS service is still down - hope it's back up soon.

I suspect the same thing could happen if we were on SVN. If SF does
plan on shutting down CVS we can move, but I don't see any benefit in
doing it before necessary.

Robert

[Ben Bucksch]

I suspect the same thing could happen if we were on SVN. If SF does
plan on shutting down CVS we can move, but I don't see any benefit in
doing it before necessary.

git is decentralized, so it's not relying as much on one provider. We
could just sync the source with another server and point people (users
and developers) there in the meantime, and later sync back.

A proper transition to a new VCS takes a bit of time, for proper
migration of all the history / revisions. If they warn now that it's
going to be taken down, it's a good idea to start the migration soon.

Ben

[Robert Eden]

Given a choice between GIT and SVN, I prefer SVN.

1. I know migration from CVS to SVN is trivial.
2. I already use SVN :)
3. Technology is similar to CVS.
4. We really don't need anything as radical as GIT.

Worst case we can host SVN someplace else (I know Schedules Direct could even do it), but I still don't think we need to do anything until we get more
news from Sourceforge...

I think an outage this long is unprecedented. I'll check out some of their forums and see what's up.

Robert

Post by Ben Bucksch

I suspect the same thing could happen if we were on SVN. If SF does
plan on shutting down CVS we can move, but I don't see any benefit in
doing it before necessary.

git is decentralized, so it's not relying as much on one provider. We
could just sync the source with another server and point people (users
and developers) there in the meantime, and later sync back.
A proper transition to a new VCS takes a bit of time, for proper
migration of all the history / revisions. If they warn now that it's
going to be taken down, it's a good idea to start the migration soon.
Ben
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
xmltv-devel mailing list
https://lists.sourceforge.net/lists/listinfo/xmltv-devel

[Robert Eden]

BTW... I do have a backup of the CVS tree from 1/24.

[Mattias Holmlund]

Post by Robert Eden
BTW... I do have a backup of the CVS tree from 1/24.

I have a git tree with complete history that was last updated 1/26. Last
commit was

commit 3154b5cb550b6e16a26e344b762aeaa709d45ae6
Author: dekarl <dekarl>
Date: Wed Jan 26 08:11:56 2011 +0000

test_grabbers: rewrite directory reading to handle unix and windows


It is no longer publicly available (my DSL line is down...), but I can
push it to github if anyone wants it.

/Mattias

[Robert Eden]

Post by Mattias Holmlund

Post by Robert Eden
BTW... I do have a backup of the CVS tree from 1/24.

I have a git tree with complete history that was last updated 1/26. Last
commit was
commit 3154b5cb550b6e16a26e344b762aeaa709d45ae6
Author: dekarl<dekarl>
Date: Wed Jan 26 08:11:56 2011 +0000
test_grabbers: rewrite directory reading to handle unix and windows
It is no longer publicly available (my DSL line is down...), but I can
push it to github if anyone wants it.

How does your Git tree make it to CVS (the official repository)? Or do
you have something that propigates CVS commits to your local Git tree???

Robert

[Mattias Holmlund]

Post by Robert Eden

Post by Mattias Holmlund

Post by Robert Eden
BTW... I do have a backup of the CVS tree from 1/24.

I have a git tree with complete history that was last updated 1/26. Last
commit was
commit 3154b5cb550b6e16a26e344b762aeaa709d45ae6
Author: dekarl<dekarl>
Date: Wed Jan 26 08:11:56 2011 +0000
test_grabbers: rewrite directory reading to handle unix and windows
It is no longer publicly available (my DSL line is down...), but I can
push it to github if anyone wants it.

How does your Git tree make it to CVS (the official repository)? Or do
you have something that propigates CVS commits to your local Git tree???

I have a cronjob that imports CVS into git. I never commit to git directly.

/Mattias

[Karl Dietz]

Post by Mattias Holmlund

Post by Robert Eden
BTW... I do have a backup of the CVS tree from 1/24.

I have a git tree with complete history that was last updated 1/26. Last
commit was

With my complete TV related software stack being developed in GIT
repositories (now that MythTV moved from SVN to GIT) I'd rather not add
SVN back to the list of SCM tools.

But with the simple use cases in active use it doesn't really matter.

Regards,
Karl

[Ben Bucksch]

Post by Mattias Holmlund
I have a git tree with complete history that was last updated 1/26.

Great! Seems like the migration is not such a big problem.

Post by Mattias Holmlund
I can push it to github if anyone wants it.

That would be nice, if it's not much work.

One advantage of git is that its distributed nature makes injecting
false changes into the older history of the repo a lot harder, so
hacking should be easy to catch.

Robert, SF is going down since many years already. I was not surprised
at all to read that they've been hacked again. They have served well,
and you could leave some non-code services there, but I recommend to
move the official repository elsewhere, just to be no longer dependent
on SF.

Ben

[Mattias Holmlund]

Post by Ben Bucksch

Post by Mattias Holmlund
I have a git tree with complete history that was last updated 1/26.

Great! Seems like the migration is not such a big problem.

Post by Mattias Holmlund
I can push it to github if anyone wants it.

That would be nice, if it's not much work.

I'll try to do it tomorrow.

/Mattias

[Mattias Holmlund]

Post by Ben Bucksch

Post by Mattias Holmlund
I have a git tree with complete history that was last updated 1/26.

Great! Seems like the migration is not such a big problem.

Post by Mattias Holmlund
I can push it to github if anyone wants it.

That would be nice, if it's not much work.

My git repository is now available on github:

https://github.com/mattiash/xmltv

The conversion from cvs to git is done with git cvsimport. It has been
running on one of my machines in a cronjob for several years. I haven't
looked at it recently, so it would be good if someone with a recent CVS
checkout could compare the most recent commit to CVS.

The committer names in the repository only uses sourceforge usernames
and not real names and email-addresses.

/Mattias

[Francois Gouget]

Post by Robert Eden
Given a choice between GIT and SVN, I prefer SVN.

And I'd prefer Git :-) Preferences<g>.
So here's my take on this, not that it necessarily deserves much weight.

Post by Robert Eden
1. I know migration from CVS to SVN is trivial.

Not sure if it's trivial but I know that a lot of projects have migrated
from CVS to Git. So it's doable.

Post by Robert Eden
2. I already use SVN :)

I already use Git :)

Post by Robert Eden
3. Technology is similar to CVS.

Technology is much better than CVS.

Post by Robert Eden
4. We really don't need anything as radical as GIT.

With Git there is no longer any need to get commits right the first time
around. You can rework a series of patches at leisure until you're
entirely happy with it, and then push them online. So it's a big plus
whenever a piece of code needs to be refactored.


Also personally I'm not convinced SVN has much of a future: I can't
imagine new projects picking SVN instead of Git or Mercurial so I
suspect they are slowly losing market share. Given that I would be
afraid that SF would remove SVN support a few years down the line
meaning we'd have to switch again.