You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by David Moxon <dm...@gmail.com> on 2008/07/28 18:49:34 UTC
can mod_dav_svn 1.5 deny access from earlier clients?
Hello,
I manage a large subversion repository, and I am interested in upgrading to
1.5. However, it will not be possible for me to upgrade all our user's svn
clients at the same time, since they are managed indvidually by the users
themselves.
My concern is this:
1. We begin using subversion 1.5's merge tracking feature throughout the
repository.
2. A user with an older subversion client does some (legacy-style) merge
operations on the repository.
3. The svn:mergeinfo on the server is then incomplete/corrupt?
I tried to look for how subversion 1.5 handles this mixed client server
version situation, but it is unclear. The documentation states that merge
tracking is only supported if both server and client are version 1.5, but
does not state what happens if an earlier client attempts to perform
(legacy-style) merges against a 1.5 server and repository with merge
tracking information in use by others.
If this scenario is not supported, is it possible to deny access to a
repository from clients earlier than 1.5?
Thanks,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: can mod_dav_svn 1.5 deny access from earlier clients?
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
david.x.grierson@jpmorgan.com wrote:
> (copied to dev@... as I think this one's a defect).
>
> Except that this appears to be broken if you're using mod_dav_svn 1.5.0.
>
> As previously posted by Jacky-10:
> http://svn.haxx.se/users/archive-2008-07/0730.shtml
>
>> I notice the commit action in mod_dav_svn involves a few steps. The
>> first step uses OPTIONS which includes DAV: .../mergeinfo in the http
>> header. But the following steps (PROPFIND, MKACTIVITY) don't include
>> this header which seems to make svn server calling start-commit script
>> without mergeinfo capability."
>
> I've confirmed this in an ethereal session (attached) - the capabilities
> parameters are listed in the DAV: parameters passed to the HTTP request
> but are not being passed through to the start-commit script.
>
> OPTIONS /svn/repos/david.x.grierson/trunk/src HTTP/1.1
> Host: 192.168.56.128
> User-Agent: SVN/1.5.0
> Keep-Alive:
> Connect: TE, Keep-Alive
> TE: trailers
> DAV: http://subversion.tigris.org/xmlns/dav/svn/depth
> DAV: http://subversion.tigris.org/xmlns/dav/svn/mergeinfo
> DAV: http://subversion.tigris.org/xmlns/dav/svn/log-revprops
> Accept-Encoding: gzip
>
> Whereas the the start-commit output is:
>
> svn: Commit failed (details follow):
> svn: Commit blocked by start-commit hook (exit code 1) with output:
> Repo path: [/opt/svnroot/david.x.grierson]
> Username: []
> Capabilities: []
>
> Sorry - you are using a pre-1.5.x Subversion client - exiting!
>
> start-commit hook script and ethereal session attached.
>
>
>
> I'll raise this as a defect against 1.5.0 - I don't have a build of 1.5.1
> yet so can't confirm whether it's still present in that.
We would much prefer if you (or someone else) could see if the bug is still
present in 1.5.1 before filing an issue. It really helps to keep the issue
tracker clean. I know we did fix a few things related to authz over dav in
1.5.1, and wonder if this is one of them.
Thanks,
-Hyrum
RE: can mod_dav_svn 1.5 deny access from earlier clients?
Posted by da...@jpmorgan.com.
(copied to dev@... as I think this one's a defect).
Except that this appears to be broken if you're using mod_dav_svn 1.5.0.
As previously posted by Jacky-10:
http://svn.haxx.se/users/archive-2008-07/0730.shtml
> I notice the commit action in mod_dav_svn involves a few steps. The
> first step uses OPTIONS which includes DAV: .../mergeinfo in the http
> header. But the following steps (PROPFIND, MKACTIVITY) don't include
> this header which seems to make svn server calling start-commit script
> without mergeinfo capability."
I've confirmed this in an ethereal session (attached) - the capabilities
parameters are listed in the DAV: parameters passed to the HTTP request
but are not being passed through to the start-commit script.
OPTIONS /svn/repos/david.x.grierson/trunk/src HTTP/1.1
Host: 192.168.56.128
User-Agent: SVN/1.5.0
Keep-Alive:
Connect: TE, Keep-Alive
TE: trailers
DAV: http://subversion.tigris.org/xmlns/dav/svn/depth
DAV: http://subversion.tigris.org/xmlns/dav/svn/mergeinfo
DAV: http://subversion.tigris.org/xmlns/dav/svn/log-revprops
Accept-Encoding: gzip
Whereas the the start-commit output is:
svn: Commit failed (details follow):
svn: Commit blocked by start-commit hook (exit code 1) with output:
Repo path: [/opt/svnroot/david.x.grierson]
Username: []
Capabilities: []
Sorry - you are using a pre-1.5.x Subversion client - exiting!
start-commit hook script and ethereal session attached.
I'll raise this as a defect against 1.5.0 - I don't have a build of 1.5.1
yet so can't confirm whether it's still present in that.
Dg.
--
David Grierson
JPMorgan - IB Architecture - Source Code Management Consultant
GDP 228-5574 / DDI +44 141 228 5574 / Email david.x.grierson@jpmorgan.com
Alhambra House 6th floor, 45 Waterloo Street, Glasgow G2 6HS
"David Moxon" <dm...@gmail.com>
28/07/2008 20:01
To
<us...@subversion.tigris.org>
cc
Subject
RE: can mod_dav_svn 1.5 deny access from earlier clients?
Ah perfect, I must have missed that. Thanks!
-----Original Message-----
From: Mark Phippard [mailto:markphip@gmail.com]
Sent: Monday, July 28, 2008 11:55 AM
To: David Moxon
Cc: users@subversion.tigris.org
Subject: Re: can mod_dav_svn 1.5 deny access from earlier clients?
On Mon, Jul 28, 2008 at 2:49 PM, David Moxon <dm...@gmail.com> wrote:
> I tried to look for how subversion 1.5 handles this mixed client server
> version situation, but it is unclear. The documentation states that
merge
> tracking is only supported if both server and client are version 1.5,
but
> does not state what happens if an earlier client attempts to perform
> (legacy-style) merges against a 1.5 server and repository with merge
> tracking information in use by others.
>
> If this scenario is not supported, is it possible to deny access to a
> repository from clients earlier than 1.5?
This is addressed in the book:
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.bra
nchmerge.advanced.pre1.5clients
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Generally, this communication is for informational purposes only
and it is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation
of any transaction. In the event you are receiving the offering
materials attached below related to your interest in hedge funds or
private equity, this communication may be intended as an offer or
solicitation for the purchase or sale of such fund(s). All market
prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice.
Any comments or statements made herein do not necessarily reflect
those of JPMorgan Chase & Co., its subsidiaries and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.
RE: can mod_dav_svn 1.5 deny access from earlier clients?
Posted by da...@jpmorgan.com.
(copied to dev@... as I think this one's a defect).
Except that this appears to be broken if you're using mod_dav_svn 1.5.0.
As previously posted by Jacky-10:
http://svn.haxx.se/users/archive-2008-07/0730.shtml
> I notice the commit action in mod_dav_svn involves a few steps. The
> first step uses OPTIONS which includes DAV: .../mergeinfo in the http
> header. But the following steps (PROPFIND, MKACTIVITY) don't include
> this header which seems to make svn server calling start-commit script
> without mergeinfo capability."
I've confirmed this in an ethereal session (attached) - the capabilities
parameters are listed in the DAV: parameters passed to the HTTP request
but are not being passed through to the start-commit script.
OPTIONS /svn/repos/david.x.grierson/trunk/src HTTP/1.1
Host: 192.168.56.128
User-Agent: SVN/1.5.0
Keep-Alive:
Connect: TE, Keep-Alive
TE: trailers
DAV: http://subversion.tigris.org/xmlns/dav/svn/depth
DAV: http://subversion.tigris.org/xmlns/dav/svn/mergeinfo
DAV: http://subversion.tigris.org/xmlns/dav/svn/log-revprops
Accept-Encoding: gzip
Whereas the the start-commit output is:
svn: Commit failed (details follow):
svn: Commit blocked by start-commit hook (exit code 1) with output:
Repo path: [/opt/svnroot/david.x.grierson]
Username: []
Capabilities: []
Sorry - you are using a pre-1.5.x Subversion client - exiting!
start-commit hook script and ethereal session attached.
I'll raise this as a defect against 1.5.0 - I don't have a build of 1.5.1
yet so can't confirm whether it's still present in that.
Dg.
--
David Grierson
JPMorgan - IB Architecture - Source Code Management Consultant
GDP 228-5574 / DDI +44 141 228 5574 / Email david.x.grierson@jpmorgan.com
Alhambra House 6th floor, 45 Waterloo Street, Glasgow G2 6HS
"David Moxon" <dm...@gmail.com>
28/07/2008 20:01
To
<us...@subversion.tigris.org>
cc
Subject
RE: can mod_dav_svn 1.5 deny access from earlier clients?
Ah perfect, I must have missed that. Thanks!
-----Original Message-----
From: Mark Phippard [mailto:markphip@gmail.com]
Sent: Monday, July 28, 2008 11:55 AM
To: David Moxon
Cc: users@subversion.tigris.org
Subject: Re: can mod_dav_svn 1.5 deny access from earlier clients?
On Mon, Jul 28, 2008 at 2:49 PM, David Moxon <dm...@gmail.com> wrote:
> I tried to look for how subversion 1.5 handles this mixed client server
> version situation, but it is unclear. The documentation states that
merge
> tracking is only supported if both server and client are version 1.5,
but
> does not state what happens if an earlier client attempts to perform
> (legacy-style) merges against a 1.5 server and repository with merge
> tracking information in use by others.
>
> If this scenario is not supported, is it possible to deny access to a
> repository from clients earlier than 1.5?
This is addressed in the book:
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.bra
nchmerge.advanced.pre1.5clients
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Generally, this communication is for informational purposes only
and it is not intended as an offer or solicitation for the purchase
or sale of any financial instrument or as an official confirmation
of any transaction. In the event you are receiving the offering
materials attached below related to your interest in hedge funds or
private equity, this communication may be intended as an offer or
solicitation for the purchase or sale of such fund(s). All market
prices, data and other information are not warranted as to
completeness or accuracy and are subject to change without notice.
Any comments or statements made herein do not necessarily reflect
those of JPMorgan Chase & Co., its subsidiaries and affiliates.
This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.
Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.
RE: can mod_dav_svn 1.5 deny access from earlier clients?
Posted by David Moxon <dm...@gmail.com>.
Ah perfect, I must have missed that. Thanks!
-----Original Message-----
From: Mark Phippard [mailto:markphip@gmail.com]
Sent: Monday, July 28, 2008 11:55 AM
To: David Moxon
Cc: users@subversion.tigris.org
Subject: Re: can mod_dav_svn 1.5 deny access from earlier clients?
On Mon, Jul 28, 2008 at 2:49 PM, David Moxon <dm...@gmail.com> wrote:
> I tried to look for how subversion 1.5 handles this mixed client server
> version situation, but it is unclear. The documentation states that merge
> tracking is only supported if both server and client are version 1.5, but
> does not state what happens if an earlier client attempts to perform
> (legacy-style) merges against a 1.5 server and repository with merge
> tracking information in use by others.
>
> If this scenario is not supported, is it possible to deny access to a
> repository from clients earlier than 1.5?
This is addressed in the book:
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.bra
nchmerge.advanced.pre1.5clients
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: can mod_dav_svn 1.5 deny access from earlier clients?
Posted by Mark Phippard <ma...@gmail.com>.
On Mon, Jul 28, 2008 at 2:49 PM, David Moxon <dm...@gmail.com> wrote:
> I tried to look for how subversion 1.5 handles this mixed client server
> version situation, but it is unclear. The documentation states that merge
> tracking is only supported if both server and client are version 1.5, but
> does not state what happens if an earlier client attempts to perform
> (legacy-style) merges against a 1.5 server and repository with merge
> tracking information in use by others.
>
> If this scenario is not supported, is it possible to deny access to a
> repository from clients earlier than 1.5?
This is addressed in the book:
http://svnbook.red-bean.com/nightly/en/svn.branchmerge.advanced.html#svn.branchmerge.advanced.pre1.5clients
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org