On Sun, Nov 03, 2013 at 09:46:14PM -0600, Ryan Schmidt wrote:
> $ svn di files/
> Assertion failed: (kind == svn_node_file && (status ==
> svn_wc__db_status_normal || status == svn_wc__db_status_added || (status ==
> svn_wc__db_status_deleted && diff_pristine))), function
> svn_wc__diff_local_on
On 11/3/13 4:02 PM, Erwin Hogeweg wrote:
> Thanks for the response. It looks like applying the patch solved the problem.
> I
> am able to connect to the repo again. Pfew.
Glad to help. Something roughly equivalent to that patch will be included in
the next release. So you shouldn't need that pa
I’m working on creating an openni2 port for MacPorts.
https://trac.macports.org/ticket/40107
To begin, I “svn copy”’d our existing openni port and then started making
changes. I’ve renamed one patchfile and modified it, then deleted two other
patchfiles. Now I wanted to see a diff, and svn cras
On 04.11.2013 01:02, Erwin Hogeweg wrote:
> Hi Ben,
>
> Thanks for the response. It looks like applying the patch solved the
> problem. I am able to connect to the repo again. Pfew.
>
> I had to disable this mod_sec rule in order to make it work though:
>
> # allow request methods
> #SecRule REQUES
Hi Ben,
Thanks for the response. It looks like applying the patch solved the problem. I
am able to connect to the repo again. Pfew.
I had to disable this mod_sec rule in order to make it work though:
# allow request methods
#SecRule REQUEST_METHOD "!^((?:(?:POS|GE)T|OPTIONS|HEAD))$" \
#"pha
On 03.11.2013 20:29, Nico Kadel-Garcia wrote:
> I'm going to give you my Red Hat/Fedora classic advice.
>
> Work From The RPM
That's not really helpful. People have legitimate reasons to build from
source, and you definitely won't find an (S)RPM with the latest trunk.
It really is mostly tri
Hi,
I just upgraded my system to Fedora 19 from Fedora 16 and what was working is
not working now. Specifically, the two versions of subversion I HAVE been
building successfully (subversion-1.8.4 and the latest development version).
Both are failing now and I'm not sure what to do. I have incl
> -Original Message-
> From: Ben Reser [mailto:b...@reser.org]
> Sent: zaterdag 2 november 2013 23:58
> To: d...@sent.com; users@subversion.apache.org
> Subject: Re: IPv6 URL support in SVN? v1.8.4 works with IPv4, not with IPv6
>
> On 11/2/13 10:48 AM, d...@sent.com wrote:
> > reading @
RHEL and thus CentOS don't publish Subversion 1.7 RPM's, so I see that
you're using a locally compiled package. You could try the Repoforge RPM's,
from the Repoforge "extras" repository: Unfortunately, that package is a
bit out of date and doesn't look like it will get updated soon. I urge you
to g
