Re: [M#73697383] Re: Disk-quota Request

[root <da...@axiom-developer.org>]

> * Saying 'svn isn't ready for primetime' is mildly amusing to me.  I'm
> one of subversion's original designers, and the system has been
> evolving for 6 years now.  Apache, GCC, KDE, Gnome, Samba, and nearly
> every project started within the last 3 years uses it.  Sourceforge
> and Google offer it to the public.  There are 6+ books written on it.
>  It's the 'new standard'.   If it were as unusable as your personal
> experiences, it never would have taken off.

moments ago:

svn commit 
....................................................
svn: MERGE request failed on '/svnroot/magnus/branches/daly'
svn: MERGE of '/svnroot/magnus/branches/daly': 500 Internal Server Error (https://svn.sourceforge.net)


Third failure of this type in 3 days. Sometimes it works, sometimes not.

You may be amused but I'm not. I hate redoing work. 
Especially when the WHOLE POINT of a code archive is to preserve work.

Perhaps sourceforge is badly configured or I just can't spell 'commit'.

And why don't I get enough information to actually debug why it failed?

Anyway, I'm off to preserve my changes, do a partially failing checkout 
followed by several updates to recover and get all the data, 
redo my changes, commit and pray.


Total number of ARCH commit failures for any reason over the past 3 years: 0
Total number of CVS  commit failures for any reason over the past 3 years: 0

>  I'm sure, though, that the negative experiences reported about svn
> aren't amusing to those experiencing them.  But I assure you that
> they're indicative of something configured incorrectly in specific
> environments.  Those experiences aren't the norm, they're some weird
> edge-case.  In other words, occam's razor says, "it's not that the
> public is crazy for widely adopting a buggy system, rather, there's
> just something buggy about your particular setups".  :-)  My
> recommendation is that you guys report your problems to the
> users@subversion.tigris.org list (which has thousands of subscribers)
> to help de-bug whatever gremlins are in your setup.  Quietly hating
> subversion isn't a useful strategy.

Vocally hating subversion isn't useful either :-)
I've copied the mailing list. 
Maybe they can fix sourceforge.


Tim, the loser who can't commit, Daly

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: [M#73697383] Re: Disk-quota Request

[Mark <ma...@mitsein.net>]

I'm guessing SF's problem is load on their web server.  I've had
issues of late just viewing a repository with viewvc on SF.  Don't
blame the subversion package for problems that may be a result of the
configuration/implementation at the site you are using.  The site that
is completely free to you.

On 10/1/06, root <da...@axiom-developer.org> wrote:
> > * Saying 'svn isn't ready for primetime' is mildly amusing to me.  I'm
> > one of subversion's original designers, and the system has been
> > evolving for 6 years now.  Apache, GCC, KDE, Gnome, Samba, and nearly
> > every project started within the last 3 years uses it.  Sourceforge
> > and Google offer it to the public.  There are 6+ books written on it.
> >  It's the 'new standard'.   If it were as unusable as your personal
> > experiences, it never would have taken off.
>
> moments ago:
>
> svn commit
> ....................................................
> svn: MERGE request failed on '/svnroot/magnus/branches/daly'
> svn: MERGE of '/svnroot/magnus/branches/daly': 500 Internal Server Error (https://svn.sourceforge.net)
>
>
> Third failure of this type in 3 days. Sometimes it works, sometimes not.
>
> You may be amused but I'm not. I hate redoing work.
> Especially when the WHOLE POINT of a code archive is to preserve work.
>
> Perhaps sourceforge is badly configured or I just can't spell 'commit'.
>
> And why don't I get enough information to actually debug why it failed?
>
> Anyway, I'm off to preserve my changes, do a partially failing checkout
> followed by several updates to recover and get all the data,
> redo my changes, commit and pray.
>
>
> Total number of ARCH commit failures for any reason over the past 3 years: 0
> Total number of CVS  commit failures for any reason over the past 3 years: 0
>
> >  I'm sure, though, that the negative experiences reported about svn
> > aren't amusing to those experiencing them.  But I assure you that
> > they're indicative of something configured incorrectly in specific
> > environments.  Those experiences aren't the norm, they're some weird
> > edge-case.  In other words, occam's razor says, "it's not that the
> > public is crazy for widely adopting a buggy system, rather, there's
> > just something buggy about your particular setups".  :-)  My
> > recommendation is that you guys report your problems to the
> > users@subversion.tigris.org list (which has thousands of subscribers)
> > to help de-bug whatever gremlins are in your setup.  Quietly hating
> > subversion isn't a useful strategy.
>
> Vocally hating subversion isn't useful either :-)
> I've copied the mailing list.
> Maybe they can fix sourceforge.
>
>
> Tim, the loser who can't commit, Daly
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>


-- 
Mark
"Blessed is he who finds happiness in his own foolishness, for he will
always be happy."

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org