On 1/21/15 7:47 AM, Tran Ngoc Lieu, Ms wrote:
> Dear Mr/Ms,
>
> I meet the problem with svn as the following:
> "In file
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.6\ext\subversion\subversion\libsvn_wc\wc_db_update_move.c'
> line 1039: assertion failed (move_dst_revision == expected_move_
On Tue, Jan 27, 2015 at 7:43 PM, Alfredo De Luca
wrote:
> Hi all.
> I have apache2 + svn 1.6. If I use SVN with local user it's all ok but
> when I try to integrated with Active Directory I have weird issue.
> With my account (with AD username and password) I have access with no prob.
> Others can
Hi Ryan Schmidt,
I don't know why the problem occurred, one day I just updated code and it
occurred, then I updated again, it occurred again
I remembered it occurred 2 or 3 times like this. After I rebooted my laptop, it
doesn't happen anymore.
Best regards,
Ngoc Lieu.
-Original Message--
On Jan 21, 2015, at 9:47 AM, Tran Ngoc Lieu, Ms wrote:
> I meet the problem with svn as the following:
> "In file
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.8.6\ext\subversion\subversion\libsvn_wc\wc_db_update_move.c'
> line 1039: assertion failed (move_dst_revision == expected_move_dst_re
Hi all.
I have apache2 + svn 1.6. If I use SVN with local user it's all ok but
when I try to integrated with Active Directory I have weird issue.
With my account (with AD username and password) I have access with no prob.
Others can't access it at all. Below is the subversion.conf that I am using.
Hi Ben,
Thanks, you've answered all my questions before I could even ask them.
I wrote a perl function to find those calls, and pull usage out of the
runtime errors.
But now, perldoc ftw.
By the way, these aren't too bad for docs:
http://search.cpan.org/~mschwern/Alien-SVN-v1.8.11.0/
On Tue, J
On 1/27/15 9:07 AM, Lathan Bidwell wrote:
> By the way, the SWIG definitions are different enough that they could use
> their
> own documentation page.
They actually do have a fair amount of documentation. It's just not on a web
page on the website.
Use the perldoc command against the modules e
On 1/27/15 9:24 AM, Lathan Bidwell wrote:
> In the Perl SWIG bindings:
>
> $ctx->url_from_path
>
> I believe calls the svn_uri_canonicalize in 1.8.8, but I believe that its a
> secondary effect (in 1.6, it doesn't cleanse the url)
$ctx->url_from_path is calling svn_client_url_from_path():
http:/
On 1/27/15 10:52 AM, Stefan Sperling wrote:
> I suppose _Core (with leading underscore) is a private namespace.
> I don't know why this isn't part of the public SVN::Core:: namespace.
> It probably should be.
It is. SVN:Core::uri_canonicalize();
_Core is the raw SWIG wrapped interfaces.
Core cut
On 27.01.2015 20:30, Stefan Sperling wrote:
> On Tue, Jan 27, 2015 at 07:52:49PM +0100, Stefan Sperling wrote:
>> prints "http:///svn.example.com/foo/bar";
>> (Why 3 slashes after "http:" instead of 2? I don't know. It seems our test
>> suite doesn't cover this case. I'm not sure what's expected.)
On Tue, Jan 27, 2015 at 07:52:49PM +0100, Stefan Sperling wrote:
> prints "http:///svn.example.com/foo/bar";
> (Why 3 slashes after "http:" instead of 2? I don't know. It seems our test
> suite doesn't cover this case. I'm not sure what's expected.)
This turns out to be expected. Whether or not su
On Tue, Jan 27, 2015 at 12:24:47PM -0500, Lathan Bidwell wrote:
> In the Perl SWIG bindings:
>
> $ctx->url_from_path
>
> I believe calls the svn_uri_canonicalize in 1.8.8, but I believe that its a
> secondary effect (in 1.6, it doesn't cleanse the url)
>
> Is there a perl SWIG binding for svn_ur
In the Perl SWIG bindings:
$ctx->url_from_path
I believe calls the svn_uri_canonicalize in 1.8.8, but I believe that its a
secondary effect (in 1.6, it doesn't cleanse the url)
Is there a perl SWIG binding for svn_uri_canonicalize?
Lathan
On Tue, Jan 27, 2015 at 12:07 PM, Lathan Bidwell wrote
> svn_uri_canonicalize(). Else you'll get undefined behaviour,
>
> I think I have found the SWIG perl binding for one of these cleansing
functions, I will test that out and put it in.
By the way, the SWIG definitions are different enough that they could use
their own documentation page. svn_uri_ca
On 27.01.2015 17:41, Stefan Sperling wrote:
> On Tue, Jan 27, 2015 at 11:30:55AM -0500, Lathan Bidwell wrote:
>> I fully agree, the error is correct and deserved.
>> It is happening on both my 1.6 prod servers and my 1.8.8 test servers.
>>
>> And I fully understand, and will do more to sanitize my
On Tue, Jan 27, 2015 at 11:30:55AM -0500, Lathan Bidwell wrote:
> I fully agree, the error is correct and deserved.
> It is happening on both my 1.6 prod servers and my 1.8.8 test servers.
>
> And I fully understand, and will do more to sanitize my inputs.
>
> But the fact that warnings cause a s
I fully agree, the error is correct and deserved.
It is happening on both my 1.6 prod servers and my 1.8.8 test servers.
And I fully understand, and will do more to sanitize my inputs.
But the fact that warnings cause a seg fault / core fault of the whole
apache process makes my error reporting v
On Tue, Jan 27, 2015 at 10:38:31AM -0500, Lathan Bidwell wrote:
> I am running SVN 1.6 (will be upgrading to 1.8.8) through apache 2.4 /
> mod_perl.
>
> I'm trying to get email notifications of errors, but whenever libsvn fails
> one of its assertions, it dies, and causes the whole apache process
I am running SVN 1.6 (will be upgrading to 1.8.8) through apache 2.4 /
mod_perl.
I'm trying to get email notifications of errors, but whenever libsvn fails
one of its assertions, it dies, and causes the whole apache process to core
dump / seg fault.
Is there some way to either check for these ass
On 27.01.2015 16:16, Wang, John wrote:
> I am going to upgrade a Subversion on RHEL 5 from 1.5.6 to 1.7.19. I
> have questions about the upgrade.
I'm assuming you're upgrading the server; upgrading clients is a
different issue.
> 1. Do I have to upgrade Subversion binary from 1.5.6. to 1.6 and t
I am going to upgrade a Subversion on RHEL 5 from 1.5.6 to 1.7.19. I have
questions about the upgrade.
1. Do I have to upgrade Subversion binary from 1.5.6. to 1.6 and then
further to 1.7.19?
2. If #1 is true, do I have to update Subversion repositories after the
Subversion binaries have
21 matches
Mail list logo