I did a version check just now and it seems 1.7.2 did in fact install correctly
when I ran the make install with the new tar.
I didn't really do anything, but I'm running a VPS, so maybe some automated job
the tech guys on my host set up did something (recycle apache or something?)
Either way, I
Please forgive me but how do you install the v1.7 libraries on top of
v1.6. Is it basically performing the compilation of v1.7 and installing it
over the v1.6 directory location?
On Tue, Dec 20, 2011 at 6:11 PM, Daniel Shahaf wrote:
> please reply to all so so replies go to the list
>
> phillip.
Log file attached.
Karl
svn-crash-log20111220190155.log
Description: Binary data
Phil wrote on Tue, Dec 20, 2011 at 17:22:52 -0500:
> Whenever I use "svn://" protocol to checkout numerous files at one time, I
> get the error "svn: compression svndiff failed data" at some point.
(You either misquote the message or mistranslate it. In the latter
case, set LC_ALL=C in your envir
Whenever I use "svn://" protocol to checkout numerous files at one time, I
get the error "svn: compression svndiff failed data" at some point.
However, this doesn't occure when using "file://" protocol. Does anyone
know how to resolve this with svn v1.6? This doesn't occur with svn v1.7
but I prefe
Pinzone Gerard (DS-1) wrote on Tue, Dec 20, 2011 at 20:50:44 +:
> Designation: Non-SSA/Finmeccanica
>
> Daniel Shahaf wrote:
> > Yeah, but you do that in three round-trips rather than two:
> >
> > GET /foo//bar//baz
> > 301 Moved Permanently
> > Location: /foo/bar//baz
> > GET /foo/bar//baz
Designation: Non-SSA/Finmeccanica
Daniel Shahaf wrote:
> Yeah, but you do that in three round-trips rather than two:
>
> GET /foo//bar//baz
> 301 Moved Permanently
> Location: /foo/bar//baz
> GET /foo/bar//baz
> 301 Moved Permanently
> Location: /foo/bar//baz
> GET /foo/bar/baz
> 200 OK
Right,
On Tue, Dec 20, 2011, at 20:28, Pinzone Gerard (DS-1) wrote:
> Designation: Non-SSA/Finmeccanica
>
> Daniel Shahaf wrote:
> >> That's a solution much like cutting off a finger to get rid of a splinter.
> >> Yeah it works, but...
> >>
> > Disagree. Your description was that you added the Re
Designation: Non-SSA/Finmeccanica
Daniel Shahaf wrote:
> Sure, knowing exactly what build you used is relevant information.
>
> It's just the adjective "official" that caught my eye.
Thank you for clearing up that bit of minutia.
>> That's a solution much like cutting off a finger to get rid
Pinzone Gerard (DS-1) wrote on Tue, Dec 20, 2011 at 19:52:04 +:
> Designation: Non-SSA/Finmeccanica
>
> Daniel Shahaf wrote:
>
> > The Apache Subversion Project does not release binaries, official or
> > otherwise. CollabNet, Inc. is > one of several third parties who build and
> > rele
Designation: Non-SSA/Finmeccanica
Daniel Shahaf wrote:
> The Apache Subversion Project does not release binaries, official or
> otherwise. CollabNet, Inc. is > one of several third parties who build and
> release binaries of our software.
Just letting everyone know what binaries I was usin
On Mon, Dec 19, 2011 at 22:55, Andy Levy wrote:
> On Mon, Dec 19, 2011 at 22:45, Craig Burlock wrote:
>> Hello all,
>>
>> I need to create a new SVN Repository based on my existing SVN Repository
>> for another software development team. Due to security reasons, the new SVN
>> Repository must con
Pinzone Gerard (DS-1) wrote on Tue, Dec 20, 2011 at 19:09:16 +:
> Designation: Non-SSA/Finmeccanica
>
> I was having problems performing a commit on a slave server using
> a 1.6.17 client, but not when using the newer 1.7.x client. This
> started occurring when I upgraded from the latest 1.
Designation: Non-SSA/Finmeccanica
I was having problems performing a commit on a slave server using a 1.6.17
client, but not when using the newer 1.7.x client. This started occurring when
I upgraded from the latest 1.6.x server to the 1.7.1 using the official
Collabnet binaries on Linux. (I
Nico, that will be great.
I've also posted on stack overflow.
If you use it and want some rep, you can post there, also.
If you don't use it, I can post your answer there and reference you.
Ton
PS: I've read updating RPM can cause some nasty issues because it updates
everything to bleeding ed
On Tue, Dec 20, 2011 at 9:01 AM, Cooke, Mark wrote:
> > -Original Message-
> > From: Geoff Hoffman [mailto:ghoff...@cardinalpath.com]
> > Sent: 20 December 2011 15:59
> > To: Kuno Meyer
> > Cc: users@subversion.apache.org
> > Subject: Re: Create a new working copy by cloning a subtree
> >
Stefan Podskubka hcs.at> writes:
> On 20.12.2011 15:44, Kuno Meyer wrote:
> > With SVN 1.7, is there a way to create a new working copy by cloning a
> > subtree of an existing working copy?
> >
> One thing that comes to mind is cloning the existing working copy and
> then performing an svn switc
> -Original Message-
> From: Geoff Hoffman [mailto:ghoff...@cardinalpath.com]
> Sent: 20 December 2011 15:59
> To: Kuno Meyer
> Cc: users@subversion.apache.org
> Subject: Re: Create a new working copy by cloning a subtree
> of an existing working copy?
>
> On Tue, Dec 20, 2011 at 7:44 AM
On Tue, Dec 20, 2011 at 7:44 AM, Kuno Meyer wrote:
> With SVN 1.7, is there a way to create a new working copy by cloning a
> subtree
> of an existing working copy?
>
> For example:
> - Already checked out:
> wc1/
> wc1/.svn
> wc1/src
> wc1/data
> wc1/data/bin1
>
> - Desired: a new work
On 20.12.2011 15:44, Kuno Meyer wrote:
With SVN 1.7, is there a way to create a new working copy by cloning a subtree
of an existing working copy?
One thing that comes to mind is cloning the existing working copy and
then performing an svn switch to the subtree.
However, I don't know exactly ho
See:
http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/detach.py
On Tue, Dec 20, 2011 at 9:44 AM, Kuno Meyer wrote:
> With SVN 1.7, is there a way to create a new working copy by cloning a subtree
> of an existing working copy?
>
> For example:
> - Already checked out:
> wc1/
With SVN 1.7, is there a way to create a new working copy by cloning a subtree
of an existing working copy?
For example:
- Already checked out:
wc1/
wc1/.svn
wc1/src
wc1/data
wc1/data/bin1
- Desired: a new working copy of just the "data/" subtree:
wc2/
wc2/.svn
wc2/bin1
A
On Tue, Dec 20, 2011 at 2:38 AM, Ton Robin Duong wrote:
> I tried to upgrade by running a make install again with the new 1.7.2 tar.
> This should in theory replace the binaries right?
> I took that to mean:
>
> download new version (1.7.2)
> configure
> make
> make install
>
> Before the above pr
Hello,
I'm writing a script (also used as a cron job on the server) that
should work independent of whether or not a checkout has already been
done or not. I would like to do "repeated sparse checkout" as
explained below, but I'm not sure how to do it properly. (I have some
kind of a workaround fo
Mojca Miklavec writes:
> I first need
> to figure out how to use wireshark. Is there any chapter in SVN
> documentation explaining how to troubleshoot problems with subversion
> on a network level? And if not - would it be feasible to prepare one?
http://subversion.apache.org/docs/community-guid
Daniel Shahaf wrote on Tue, Dec 20, 2011 at 02:43:48 +0200:
> > I then added a new directory with a bunch of files and wanted to
> > commit, but it complained with:
> >
> > > svn ci -m "some comment"
> > svn: E175002: Commit failed (details follow):
> > svn: E175002: The POST request returned inva
Mojca Miklavec wrote on Tue, Dec 20, 2011 at 09:53:46 +0100:
> On Tue, Dec 20, 2011 at 01:43, Daniel Shahaf wrote:
> > Can you capture the XML response on the wire and share it here? (with
> > wireshark, or neon-debug-mask) If it contains sensitive stuff feel free
> > to share it by private mail.
On Tue, Dec 20, 2011 at 02:34, Philip Martin wrote:
> Mojca Miklavec writes:
>
>>> svn ci -m "some comment"
>> svn: E175002: Commit failed (details follow):
>> svn: E175002: The POST request returned invalid XML in the response:
>> XML parse error at line 3: not well-formed (invalid token)
>> (/sui
On Tue, Dec 20, 2011 at 01:43, Daniel Shahaf wrote:
> Mojca Miklavec wrote on Mon, Dec 19, 2011 at 16:56:05 +0100:
>>
>> May I ask for any hints of what could go wrong and how I could debug
>> the problem? I have seen various threads after searching with google,
>> but none of those that I checked
Am 20.12.2011 08:38, schrieb Ton Robin Duong:
I tried to upgrade by running a make install again with the new 1.7.2 tar.
This should in theory replace the binaries right?
Provided a similar configuration, yes. It does not aim to replace
anything, only if you configure it to install in the sam
30 matches
Mail list logo
