Re: [Mono-dev] SVN upgraded to subversion 1.5.x
On Tue, 2009-02-24 at 17:15 +, Jonathan Pryor wrote: Alas, = 1.5 is insufficient, as OpenOffice.org has seen -- file movements have been *lost* during merges. See [0] and [1]. [2] mentions: The version we're running is 1.5.5 compiled from source. -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] SVN upgraded to subversion 1.5.x
On Tue, 2009-02-24 at 20:14 +, Alan McGovern wrote: Hey, SVN commits have been taking well over 60 seconds to complete all day. Is this just a temporary thing or is there an issue with the upgrade? The CIA bot in the post-commit hook was taking its time because the server it connects to was not responding. I've modified the hook so that we run the CIA bot asynchronously. -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] SVN upgraded to subversion 1.5.x
Hi Gonzalo,
Gonzalo Paniagua Javier wrote:
The Mono SVN server at mono-cvs.ximian.com has been upgraded to
Subversion 1.5.x.
That means that if you have a 1.5.x client you will finally be able to
enjoy merge tracking, sparse checkouts, changelists...
See http://subversion.tigris.org/svn_1.5_releasenotes.html for the
complete list of new features.
If you have an older client, this should not affect you in any way.
Since older clients are not updating svn:mergeinfo, merge tracking
could be easily broken if an old client is allowed to commit to
/branches.
You may want to block those clients with a start-commit hook:
---8---
#!/bin/bash
svnpath=$1
capabilities=$3
if [ ${svnpath:0:9} = /branches ]; then
if [ ${capabilities/mergeinfo//} = ${capabilities} ]; then
echo Please update to SVN = 1.5 /dev/stderr
exit 1
fi
fi
exit 0
---8---
Robert
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] SVN upgraded to subversion 1.5.x
On Tue, 2009-02-24 at 11:36 +0100, Robert Jordan wrote: Since older clients are not updating svn:mergeinfo, merge tracking could be easily broken if an old client is allowed to commit to /branches. You may want to block those clients with a start-commit hook: Thanks! -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] SVN upgraded to subversion 1.5.x
On Tue, 2009-02-24 at 11:36 +0100, Robert Jordan wrote:
Since older clients are not updating svn:mergeinfo, merge tracking
could be easily broken if an old client is allowed to commit to
/branches.
You may want to block those clients with a start-commit hook:
---8---
#!/bin/bash
svnpath=$1
capabilities=$3
if [ ${svnpath:0:9} = /branches ]; then
if [ ${capabilities/mergeinfo//} = ${capabilities} ]; then
echo Please update to SVN = 1.5 /dev/stderr
exit 1
fi
fi
exit 0
---8---
Alas, = 1.5 is insufficient, as OpenOffice.org has seen -- file
movements have been *lost* during merges. See [0] and [1]. [2]
mentions:
Please note, subversion-1.5.1 is known to break things in the
Openoffice.org context and subversion-1.5.3 has been hastily
replaced by the subversion developers because it can break
mergetracking.
So from the OpenOffice.org's perspective, 1.5.4 is the minimum version
that should be considered...which is unfortunate, as openSUSE only
provides 1.5.2.
I'm not sure if or how this would impact Mono, but it is something to
keep in mind...
- Jon
[0] http://www.openoffice.org/issues/show_bug.cgi?id=97012
[1] http://www.openoffice.org/servlets/ReadMsg?list=devmsgNo=23807
[2] http://wiki.services.openoffice.org/wiki/SVNMigration
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] SVN upgraded to subversion 1.5.x
Hey,
SVN commits have been taking well over 60 seconds to complete all day. Is
this just a temporary thing or is there an issue with the upgrade?
Thanks,
Alan.
On Tue, Feb 24, 2009 at 5:15 PM, Jonathan Pryor jonpr...@vt.edu wrote:
On Tue, 2009-02-24 at 11:36 +0100, Robert Jordan wrote:
Since older clients are not updating svn:mergeinfo, merge tracking
could be easily broken if an old client is allowed to commit to
/branches.
You may want to block those clients with a start-commit hook:
---8---
#!/bin/bash
svnpath=$1
capabilities=$3
if [ ${svnpath:0:9} = /branches ]; then
if [ ${capabilities/mergeinfo//} = ${capabilities} ]; then
echo Please update to SVN = 1.5 /dev/stderr
exit 1
fi
fi
exit 0
---8---
Alas, = 1.5 is insufficient, as OpenOffice.org has seen -- file
movements have been *lost* during merges. See [0] and [1]. [2]
mentions:
Please note, subversion-1.5.1 is known to break things in the
Openoffice.org context and subversion-1.5.3 has been hastily
replaced by the subversion developers because it can break
mergetracking.
So from the OpenOffice.org's perspective, 1.5.4 is the minimum version
that should be considered...which is unfortunate, as openSUSE only
provides 1.5.2.
I'm not sure if or how this would impact Mono, but it is something to
keep in mind...
- Jon
[0] http://www.openoffice.org/issues/show_bug.cgi?id=97012
[1] http://www.openoffice.org/servlets/ReadMsg?list=devmsgNo=23807
[2] http://wiki.services.openoffice.org/wiki/SVNMigration
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
___
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] SVN upgraded to subversion 1.5.x
The Mono SVN server at mono-cvs.ximian.com has been upgraded to Subversion 1.5.x. That means that if you have a 1.5.x client you will finally be able to enjoy merge tracking, sparse checkouts, changelists... See http://subversion.tigris.org/svn_1.5_releasenotes.html for the complete list of new features. If you have an older client, this should not affect you in any way. Enjoy! -Gonzalo ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
