Provider encountered an error while streaming a REPORT response. [400, #0]

2010-03-09 Thread Sledz, Steffen
We're running an SVN-HTTPS-Server at a CentOS 5.4 server with 

 subversion-1.6.6-0.1.el5.rf
 httpd-2.2.14-jason.1
 apr-1.3.8-1.jason.1

One of the repositories is a copy of the openembedded git repo,
which contains a few thousand files and a big history.

When calling

 git svn clone -s https://ourserver/repos/openembedded

this results in an 

 W: Ignoring error from SVN, path probably does not exist: (175002):
 RA layer request failed: Server sent unexpected return value (504 Gateway 
Time-out) in response to REPORT request for '/repos/openembedded/!svn/bc/14'

The gateway timeout comes from a squid transparent proxy which
acts as an auth gatekeeper. The original error comes from the
SVN-Server itself and is this one:

 Provider encountered an error while streaming a REPORT response.  [400, #0]

Any hints how we can fix the problem?

Steffen


Re: Provider encountered an error while streaming a REPORT response. [400, #0]

2010-03-09 Thread Ulrich Eckhardt
On Tuesday 09 March 2010, Sledz, Steffen wrote:
> One of the repositories is a copy of the openembedded git repo,
> which contains a few thousand files and a big history.
>
> When calling
>
>  git svn clone -s https://ourserver/repos/openembedded

What does 'git svn clone...' do? Can you reproduce the problem with just svn?

> this results in an
>
>  W: Ignoring error from SVN, path probably does not exist: (175002):
>  RA layer request failed: Server sent unexpected return value (504
>  Gateway Time-out) in response to REPORT request
>  for '/repos/openembedded/!svn/bc/14' 
>
> The gateway timeout comes from a squid transparent proxy which
> acts as an auth gatekeeper.

I seem to remember that squid does not work out of the box for Subversion's 
use of HTTP, you have to enable a few extra commands.

> The original error comes from the SVN-Server itself and is this one:
>
>  Provider encountered an error while streaming a REPORT
>  response.  [400, #0]

Smells like a proxy/firewall that refuses to let something pass.

Try
 - with plain svn instead of git
 - via HTTP instead of HTTPS
 - from a non-firewalled machine
 - on a different repository

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932

**
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**
   Visit our website at 
**
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten 
bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen 
Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein 
sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, 
weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte 
Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht 
verantwortlich.
**



Re: svn 1.6x and apache compression - mod_deflate

2010-03-09 Thread Stefan Sperling
On Tue, Mar 09, 2010 at 04:03:33AM +0100, Leszek Szarlej wrote:
> Hi
> 
> In svn book ver. 1.0 there is written:
> "Deflate compression places a small burden on the client and server to
> compress and decompress network transmissions as a way to minimize the size
> of the actual transmission. In cases where network bandwidth is in short
> supply, this kind of compression can greatly increase the speed at which
> communications between server and client can be sent. In extreme cases, this
> minimized network transmission could be the difference between an operation
> timing out or completing successfully."
> In the same book in version 1.5 there is no word about why/why not. Is it
> mean that mod_deflate is not recomended for current versions of svn? I did
> tests on svn 1.6.9 and compression rate is about 30-40 percent and checkout
> times are ~30%  less

I don't know why that paragraph was dropped from the book.

But there's an unrelated problem with using mod_deflate together with
mod_dav_svn. It can cause memory leaks.
See http://svn.haxx.se/dev/archive-2009-08/0274.shtml

Stefan


Re: Provider encountered an error while streaming a REPORT response. [400, #0]

2010-03-09 Thread Steffen Sledz
Ulrich Eckhardt wrote:
>>  git svn clone -s https://ourserver/repos/openembedded
> 
> What does 'git svn clone...' do? Can you reproduce the problem with just svn?

Until the point the error occurs it's just a sequence of
a few OPTIONS, PROPFIND, and REPORT requests.

I'm not sure if i can reproduce it with plain svn but i'll
try.

> I seem to remember that squid does not work out of the box for Subversion's 
> use of HTTP, you have to enable a few extra commands.

The squid works fine for a long time on all other requests
including git-svn on smaller repositories.

>>  Provider encountered an error while streaming a REPORT
>>  response.  [400, #0]
> 
> Smells like a proxy/firewall that refuses to let something pass.

H? I don't think so. As mentioned before the procedure
works fine on smaller repos. It looks like a size/timeout
problem.

Steffen



In CVS I had a %Log% directive I could insert into my source code.

2010-03-09 Thread Strickland, Larry
In CVS I had a %Log% directive I could insert into my source code. Is
there a similar option in SVN?

 

Larry Strickland

Senior Systems Administrator || Infocrossing Inc., a Wipro Company ||
11800 Ridge Parkway, Suite 200 Broomfield, CO 80021 || P:  (720)
566-1239 || || |larry.strickl...@infocrossing.com|**Think Green  -
Please print responsibly**

 

 



Confidentiality Note: This e-mail, including any attachment to it, may contain 
material that is confidential, proprietary, privileged and/or "Protected Health 
Information," within the meaning of the regulations under the Health Insurance 
Portability & Accountability Act as amended.  If it is not clear that you are 
the intended recipient, you are hereby notified that you have received this 
transmittal in error, and any review, dissemination, distribution or copying of 
this e-mail, including any attachment to it, is strictly prohibited. If you 
have received this e-mail in error, please immediately return it to the sender 
and delete it from your system. Thank you.


Re: Provider encountered an error while streaming a REPORT response. [400, #0]

2010-03-09 Thread Johan Corveleyn
On Tue, Mar 9, 2010 at 11:47 AM, Steffen Sledz  wrote:
> Ulrich Eckhardt wrote:
>>>  git svn clone -s https://ourserver/repos/openembedded
>>
>> What does 'git svn clone...' do? Can you reproduce the problem with just svn?
>
> Until the point the error occurs it's just a sequence of
> a few OPTIONS, PROPFIND, and REPORT requests.
>
> I'm not sure if i can reproduce it with plain svn but i'll
> try.
>
>> I seem to remember that squid does not work out of the box for Subversion's
>> use of HTTP, you have to enable a few extra commands.
>
> The squid works fine for a long time on all other requests
> including git-svn on smaller repositories.
>
>>>  Provider encountered an error while streaming a REPORT
>>>  response.  [400, #0]
>>
>> Smells like a proxy/firewall that refuses to let something pass.
>
> H? I don't think so. As mentioned before the procedure
> works fine on smaller repos. It looks like a size/timeout
> problem.

You could be experiencing a client-side timeout. Svn with neon (which
is the default client-side http access library) has a default timeout
of 30 seconds. If the client doesn't get something within those 30
seconds, it terminates the connection.

You can specify a higher timeout value in the "runtime configuration
area"[1] on the client, in the servers file[2]. E.g. put a line
"http-timeout = 60" in the global section, or in the group that
matches with your server.

[1] http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html
[2] 
http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html#svn.advanced.confarea.opts.servers

Johan


Re: Provider encountered an error while streaming a REPORT response. [400, #0]

2010-03-09 Thread Johan Corveleyn
On Tue, Mar 9, 2010 at 2:37 PM, Steffen Sledz  wrote:
> Johan Corveleyn wrote:
>> You could be experiencing a client-side timeout. Svn with neon (which
>> is the default client-side http access library) has a default timeout
>> of 30 seconds. If the client doesn't get something within those 30
>> seconds, it terminates the connection.
>>
>> You can specify a higher timeout value in the "runtime configuration
>> area"[1] on the client, in the servers file[2]. E.g. put a line
>> "http-timeout = 60" in the global section, or in the group that
>> matches with your server.
>>
>> [1] http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html
>> [2] 
>> http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html#svn.advanced.confarea.opts.servers
>
> I tried this without success.
>
> But i did not expect success here, because the error occurred after
> about 15 minutes what is much longer than the http-timeout.

[ Remember to put the list in cc as well, so the reply goes not only to me ]

It could be a timeout on the server as well. Look into the SVN
server's Apache config for a TimeOut directive ...

That the total operation took more than 15 minutes doesn't mean
anything for this kind of timeout, because during the entire operation
a lot of different http requests/responses are exchanged (you can see
which if you analyze your Apache's access logs). The entire sequence
of requests/responses can take hours. As long as no single request has
to wait more than 30 seconds for its response you'll be fine. If a
single http request doesn't get a response in 30 seconds (or whatever
custom value you've configured) you'll get a timeout ...

Alternatively, in your setup (with squid proxy and firewalls etc in
between), it could also be one of those components in the middle that
decides to terminate the connection.

Johan


Re: Provider encountered an error while streaming a REPORT response. [400, #0]

2010-03-09 Thread Steffen Sledz
Johan Corveleyn wrote:
>> But i did not expect success here, because the error occurred after
>> about 15 minutes what is much longer than the http-timeout.
> 
> [ Remember to put the list in cc as well, so the reply goes not only to me ]

Sorry for that.

> Alternatively, in your setup (with squid proxy and firewalls etc in
> between), it could also be one of those components in the middle that
> decides to terminate the connection.

Good hint. I found it. The default for the squid read_timeout is
15 minutes. After increasing this value to 60 minutes everything
works fine.

Thx,
Steffen




Re: Provider encountered an error while streaming a REPORT response. [400, #0]

2010-03-09 Thread Steffen Sledz
Johan Corveleyn wrote:
> You could be experiencing a client-side timeout. Svn with neon (which
> is the default client-side http access library) has a default timeout
> of 30 seconds. If the client doesn't get something within those 30
> seconds, it terminates the connection.
> 
> You can specify a higher timeout value in the "runtime configuration
> area"[1] on the client, in the servers file[2]. E.g. put a line
> "http-timeout = 60" in the global section, or in the group that
> matches with your server.
> 
> [1] http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html
> [2] 
> http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html#svn.advanced.confarea.opts.servers

I tried this without success.

But i did not expect success here, because the error occurred after
about 15 minutes what is much longer than the http-timeout.

Steffen





Re: In CVS I had a %Log% directive I could insert into my source code.

2010-03-09 Thread Erik Andersson
http://subversion.apache.org/faq.html#log-in-source

Cheers / Erik

On Tue, Mar 9, 2010 at 4:05 PM, Strickland, Larry <
larry.strickl...@infocrossing.com> wrote:

>  In CVS I had a %Log% directive I could insert into my source code. Is
> there a similar option in SVN?
>
>
>
> *Larry Strickland*
>
> Senior Systems Administrator || Infocrossing Inc., a Wipro Company || 11800
> Ridge Parkway, Suite 200 Broomfield, CO 80021 || P:  (720) 566-1239 || || |
> larry.strickl...@infocrossing.com|**Think Green  - Please print
> responsibly**
>
>
>
>
>
> Confidentiality Note: This e-mail, including any attachment to it, may
> contain material that is confidential, proprietary, privileged and/or
> "Protected Health Information," within the meaning of the regulations under
> the Health Insurance Portability & Accountability Act as amended. If it is
> not clear that you are the intended recipient, you are hereby notified that
> you have received this transmittal in error, and any review, dissemination,
> distribution or copying of this e-mail, including any attachment to it, is
> strictly prohibited. If you have received this e-mail in error, please
> immediately return it to the sender and delete it from your system. Thank
> you.
>


Re: Programming a Watcher File

2010-03-09 Thread Johan Corveleyn
On Tue, Mar 9, 2010 at 1:15 AM, David Weintraub  wrote:
> The idea is to allow users to specify exactly which they want to
> watch. It might be a few configuration files, images, etc.
>
> Hudson will notify if any files in the entire project are changed, and
> when you do a dozen builds each day, the developers start to ignore
> these build notices.
>
> This is something that most other version control systems allow and is
> usually built in. Third party clients like SVN Notifier and Commit
> Notifier is that they must be user installed and running on the user's
> machine. If you aren't on that machine, you don't get notified.
>
> Something like Fisheye is good because that allows users to set
> notifications and is not dependent upon the user's own system.
> However, we don't have Fisheye.
>
> Subversion comes with a post-commit notification script written in
> Perl, but this script requires a configuration file that sits on the
> server. That means developers have to ask the administrator to set and
> change notifications.  By putting the notification configurations
> inside the repository, I allow users to set their own notifications.
> Since it is the server that's running it, the notifications aren't
> machine dependent.

I think it's great functionality that you're building here. I for one
would be quite interested in something like this, so if you could
share it, that would be super (maybe even put it in "contrib" if it's
ready?). Having developers manage their own notifications (all within
the repos, and cross-platform, independent of client machine),
specifying which files/paths they are interested in, is very useful
functionality.

Just a thought: it would be nice if you could make the coupling with
the actual notification system a "loose coupling". To separate "how to
determine who is notified" (what you're building now) from the
"mechanism that sends the notifications". I'm currently using
commit-email.pl, but am also looking at mailer.py (once we upgrade our
server, including python bindings) and SVN::Notify
(http://search.cpan.org/dist/SVN-Notify/). It would be nice to still
be able to choose whichever notification system works best ...

Johan


[no subject]

2010-03-09 Thread tony




Re: svn 1.6x and apache compression - mod_deflate

2010-03-09 Thread Leszek Szarlej
Thanks for the info.
>See http://svn.haxx.se/dev/archive-2009-08/0274.shtml
In mentioned example apache runs on worker mpm. I've sent a message to this
group few days ago about users experience with svn and worker mpm. I didn't
get any answer. It concerns me if svn is thread-safe and if the said memory
problem would appear on prefork mpm. I will be doing some tests this week.
Regards
Leszek

On 9 March 2010 11:05, Stefan Sperling  wrote:

> On Tue, Mar 09, 2010 at 04:03:33AM +0100, Leszek Szarlej wrote:
> > Hi
> >
> > In svn book ver. 1.0 there is written:
> > "Deflate compression places a small burden on the client and server to
> > compress and decompress network transmissions as a way to minimize the
> size
> > of the actual transmission. In cases where network bandwidth is in short
> > supply, this kind of compression can greatly increase the speed at which
> > communications between server and client can be sent. In extreme cases,
> this
> > minimized network transmission could be the difference between an
> operation
> > timing out or completing successfully."
> > In the same book in version 1.5 there is no word about why/why not. Is it
> > mean that mod_deflate is not recomended for current versions of svn? I
> did
> > tests on svn 1.6.9 and compression rate is about 30-40 percent and
> checkout
> > times are ~30%  less
>
> I don't know why that paragraph was dropped from the book.
>
> But there's an unrelated problem with using mod_deflate together with
> mod_dav_svn. It can cause memory leaks.
> See http://svn.haxx.se/dev/archive-2009-08/0274.shtml
>
> Stefan
>


Locking in Subversion

2010-03-09 Thread Sanjay_Patil
Hi Guys,

Please can you advise me on below. 

I have been asked to configure Subv in a way that all word docs/newly 
added docs are configured for needs-lock in a particular projecy (say 
Project A) under a repository.

Initially I tried to implement this by adding below property to my Subv 
config file

*.doc = svn:needs-lock 

But this affects other projects under different repo as the settings is 
machine specific.

Is there a way, I can add a property to apply needs-lock to files under a 
specific project in a repo.  As there are 100 of such word docs, I wanted 
to avoid setting it at each file level.

Please let me know if you need any more information on this.

**
This email is confidential and may contain copyright material of the John Lewis 
Partnership. 
If you are not the intended recipient, please notify us immediately and delete 
all copies of this message. 
(Please note that it is your responsibility to scan this message for viruses). 
Email to and from the
John Lewis Partnership is automatically monitored for operational and lawful 
business reasons.
**

John Lewis plc
Registered in England 233462
Registered office 171 Victoria Street London SW1E 5NN
 
Websites: http://www.johnlewis.com 
http://www.waitrose.com 
http://www.greenbee.com
http://www.johnlewispartnership.co.uk
 
**
<>

Re: svn 1.6x and apache compression - mod_deflate

2010-03-09 Thread Stefan Sperling
On Tue, Mar 09, 2010 at 05:10:11PM +0100, Leszek Szarlej wrote:
> Thanks for the info.
> >See http://svn.haxx.se/dev/archive-2009-08/0274.shtml
> In mentioned example apache runs on worker mpm. I've sent a message to this
> group few days ago about users experience with svn and worker mpm. I didn't
> get any answer.

Can you provide a link to this message so it's easy to find it and to
reply to it?
The archives are at http://mail-archives.apache.org/mod_mbox/subversion-dev/

> It concerns me if svn is thread-safe and if the said memory
> problem would appear on prefork mpm. I will be doing some tests this week.

Thanks, tests always help and give insight.

Note that the problem is not specific to svn. If I understand correctly
it's a problem with mod_deflate. It's possible to work around it in
Subversion, but a proper fix would have to be made within mod_deflate.

I don't know what the status of this bug is with the httpd team,
whether it's known there, or if a fix is in sight.
The fix seems to be important to you, so maybe you could ask them?

Thanks,
Stefan


Re: svn 1.6x and apache compression - mod_deflate

2010-03-09 Thread Stefan Sperling
On Tue, Mar 09, 2010 at 05:33:34PM +0100, Stefan Sperling wrote:
> On Tue, Mar 09, 2010 at 05:10:11PM +0100, Leszek Szarlej wrote:
> > Thanks for the info.
> > >See http://svn.haxx.se/dev/archive-2009-08/0274.shtml
> > In mentioned example apache runs on worker mpm. I've sent a message to this
> > group few days ago about users experience with svn and worker mpm. I didn't
> > get any answer.
> 
> Can you provide a link to this message so it's easy to find it and to
> reply to it?
> The archives are at http://mail-archives.apache.org/mod_mbox/subversion-dev/

Sorry, I meant http://mail-archives.apache.org/mod_mbox/subversion-users/

Stefan


Re: Locking in Subversion

2010-03-09 Thread Ulrich Eckhardt
On Tuesday 09 March 2010, sanjay_pa...@johnlewis.co.uk wrote:
> I have been asked to configure Subv in a way that all word docs/newly
> added docs are configured for needs-lock in a particular projecy (say
> Project A) under a repository.
>
> Initially I tried to implement this by adding below property to my Subv
> config file
>
> *.doc = svn:needs-lock
>
> But this affects other projects under different repo as the settings is
> machine specific.

You'll also have to activate auto props in general, the above alone doesn't do 
anything. Further, it only affects newly added files. Concerning the problem 
that it also affects different repositories, I'm not sure there is anything 
you can do. IMHO that setting makes sense regardless of the repository.

> Is there a way, I can add a property to apply needs-lock to files under a
> specific project in a repo.  As there are 100 of such word docs, I wanted
> to avoid setting it at each file level.

Assume you're using TortoiseSVN (other clients might provide different ways to 
set properties recursively), go to the properties of the parent directory. 
There, add the needs-lock property and apply it recursively. Then, in the 
commit dialog, just sort the files by their type and revert the change on all 
non-doc files.

On a Unix shell, you could do something like

  find -name \*\.doc -exec ...


In any case, you could install a server-side hook script that makes sure the 
property is present on all *.doc files.

Uli

-- 
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/

Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932

**
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**
   Visit our website at 
**
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten 
bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen 
Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein 
sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, 
weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte 
Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht 
verantwortlich.
**



Re: Programming a Watcher File

2010-03-09 Thread David Weintraub
I'm looking at the SVN:Notify, and it appears to require sendmail. Is
that correct? I would rather use NET::SMTP which is more platform
neutral.

What does the NET::SMTP notification look like? Does it do a diff
between files? Does it tell you all the files modified, or just the
ones you're interested in?

I'll try to separate out the notification system and make it optional.
That's actually a nice idea. The question is how do I pass the
notification stuff. I can't use STDOUT because Subversion captures
that.

On Tue, Mar 9, 2010 at 5:42 AM, Johan Corveleyn  wrote:
> On Tue, Mar 9, 2010 at 1:15 AM, David Weintraub  wrote:
>> The idea is to allow users to specify exactly which they want to
>> watch. It might be a few configuration files, images, etc.
>>
>> Hudson will notify if any files in the entire project are changed, and
>> when you do a dozen builds each day, the developers start to ignore
>> these build notices.
>>
>> This is something that most other version control systems allow and is
>> usually built in. Third party clients like SVN Notifier and Commit
>> Notifier is that they must be user installed and running on the user's
>> machine. If you aren't on that machine, you don't get notified.
>>
>> Something like Fisheye is good because that allows users to set
>> notifications and is not dependent upon the user's own system.
>> However, we don't have Fisheye.
>>
>> Subversion comes with a post-commit notification script written in
>> Perl, but this script requires a configuration file that sits on the
>> server. That means developers have to ask the administrator to set and
>> change notifications.  By putting the notification configurations
>> inside the repository, I allow users to set their own notifications.
>> Since it is the server that's running it, the notifications aren't
>> machine dependent.
>
> I think it's great functionality that you're building here. I for one
> would be quite interested in something like this, so if you could
> share it, that would be super (maybe even put it in "contrib" if it's
> ready?). Having developers manage their own notifications (all within
> the repos, and cross-platform, independent of client machine),
> specifying which files/paths they are interested in, is very useful
> functionality.
>
> Just a thought: it would be nice if you could make the coupling with
> the actual notification system a "loose coupling". To separate "how to
> determine who is notified" (what you're building now) from the
> "mechanism that sends the notifications". I'm currently using
> commit-email.pl, but am also looking at mailer.py (once we upgrade our
> server, including python bindings) and SVN::Notify
> (http://search.cpan.org/dist/SVN-Notify/). It would be nice to still
> be able to choose whichever notification system works best ...
>
> Johan
>



-- 
David Weintraub
qazw...@gmail.com


Re: Programming a Watcher File

2010-03-09 Thread Larry Shatzer, Jr.
On Tue, Mar 9, 2010 at 10:27 AM, David Weintraub  wrote:

> I'm looking at the SVN:Notify, and it appears to require sendmail. Is
> that correct? I would rather use NET::SMTP which is more platform
> neutral.
>
> What does the NET::SMTP notification look like? Does it do a diff
> between files? Does it tell you all the files modified, or just the
> ones you're interested in?
>
> I'll try to separate out the notification system and make it optional.
> That's actually a nice idea. The question is how do I pass the
> notification stuff. I can't use STDOUT because Subversion captures
> that.
>

If you specify a smtp config, it will use that over sendmail. See
http://search.cpan.org/dist/SVN-Notify/lib/SVN/Notify.pm#smtp


-- Larry


Re: Programming a Watcher File

2010-03-09 Thread David Weintraub
After playing around with snvnotify, I notice all it does is use the
SNV::Notify class. I'll just add the option to use SNV::Notify if you
happen to have the module installed.

-- 
David Weintraub
qazw...@gmail.com


Problema with httpd server: (20014)Internal error: SQLite is required to be compiled and run in thread-safe mode

2010-03-09 Thread Érico Fusco
Hi guys, I'm trying using subversion 1.6.9 but there is a problem when ai
try to view the project by http server.

Here is the log of my apache server:

[Tue Mar 09 23:58:10 2010] [error] [client 192.168.1.1] (20014)Internal
error: SQLite is required to be compiled and run in thread-safe mode
[Tue Mar 09 23:58:10 2010] [error] [client 192.168.1.1] Could not fetch
resource information. [500, #0]
[Tue Mar 09 23:58:10 2010] [error] [client 192.168.1.1] Could not open the
requested SVN filesystem [500, #200030]
[Tue Mar 09 23:58:10 2010] [error] [client 192.168.1.1] Could not open the
requested SVN filesystem [500, #200030]

I compiled the sqlite with thread-safe, I can create a repository with the
command: svnadmin create but I can't view it with my apache server.

I tested the sqlite thread-safe with this code:

-
#include 

int main()
{
printf("%d",sqlite3_threadsafe());
return 0;
}
-
Normal, prints 1.

I compiled everything, here is the versions:

APR 1.3.9 (./configure)
APR iconv 1.2.1 (./configure --with-apr=/usr/local/apr)
APR-util 1.3.9 (./configure --with-apr=/usr/local/apr --with-dbm=db47
--with-berkeley-db=/usr/local/BerkeleyDB.4.7 --with-mysql=/usr/local/mysql
--with-sqlite3=/usr/local --with-expat=/usr/local --with-odbc=/usr)
HTTPD 2.2.14 (./configure --enable-so --enable-dav=shared
--enable-rewrite=shared --enable-ssl=shared --enable-proxy=shared
--with-apr=/usr/local/apr --with-apr-util=/usr/local/apr)
Subversion 1.6.9 (./configure --with-apr=/usr/local/apr
--with-apr-util=/usr/local/apr --with-apxs=/usr/local/apache2/bin/apxs
--with-berkeley-db=db.h:/usr/local/BerkeleyDB.4.7/include:/usr/local/BerkeleyDB.4.7/lib:db
--with-sqlite=/usr/local --with-ssl)

I'm using Fedora Core release 3 (Heidelberg), yes I know, too poor, but I
can't update this server right now. =(

I can't figure out what is it, somebody can help me with ?

Thanks a lot.

Érico Fusco