Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-08-07 Thread reviewboard
Comment #14 on issue 2898 by trowb...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 Can you look at the reviewboard.wsgi file generated by rb-site and attach it here? -- You received this message because this

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-08-07 Thread reviewboard
Comment #15 on issue 2898 by rewilli...@thesba.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 This issue was fixed for me in the subsequent 1.7.6 release that came out a few days after I added the above comment. The release

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-08-07 Thread reviewboard
Updates: Status: Fixed Comment #16 on issue 2898 by trowb...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 Glad to hear it. -- You received this message because this project is configured to send all issue

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-18 Thread reviewboard
Comment #12 on issue 2898 by rewilli...@thesba.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 I'm seeing nearly the exact same symptoms, with the exception that in comment 7, my error.log contains just this: Unable to

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-18 Thread reviewboard
Comment #13 on issue 2898 by rewilli...@thesba.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 I'm seeing nearly the exact same symptoms, with the exception that in comment 7, my error.log contains just this: Unable to

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-14 Thread reviewboard
Comment #5 on issue 2898 by andreasf...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 The Exception listed above was achieved by logging in as www-data user and calling rbssh directly. When I do the raise the debug

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-14 Thread reviewboard
Comment #6 on issue 2898 by chip...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 There's absolutely nothing after that? Can you look in the Apache error log and reviewboard.log and see if there's an exception

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-14 Thread reviewboard
Comment #7 on issue 2898 by andreasf...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 Ok, I think the apache/error.log show some more useful information: [Thu Feb 14 08:30:00 2013] [error]

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-14 Thread reviewboard
Comment #8 on issue 2898 by chip...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 Okay, so the red flag is the failure to find setings_local. The Python path *should* inherit this. So a few questions about your setup:

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-14 Thread reviewboard
Comment #9 on issue 2898 by andreasf...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 1) I am using mod_wsgi 2) The current test setup is a debian wheezy 64 Bit machine, but I had the same problem on my Ubuntu 12.04

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-14 Thread reviewboard
Comment #10 on issue 2898 by chip...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 We've seen SELinux interfere with process spawning before. If it's active, try turning it off and see if the problem goes away. If

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-14 Thread reviewboard
Comment #11 on issue 2898 by andreasf...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 Switching off the SELinux does not solve the problem. Indeed the PYTHONPATH does not contain the path to my site. How does the

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-13 Thread reviewboard
Updates: Status: NeedInfo Comment #4 on issue 2898 by chip...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 In your exception that you listed, are you get thing this from a log file, or running rbssh directly?

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-12 Thread reviewboard
Comment #1 on issue 2898 by andreasf...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 This is the output of the rbssh command: Traceback (most recent call last): File /usr/local/bin/rbssh, line 9, in module

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-12 Thread reviewboard
Comment #2 on issue 2898 by rajas...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 Looks very similar to Christian's blog post at http://blog.chipx86.com/2013/01/26/weird-bugs-django-timezones-and-importing-from-eggs/.

Re: Issue 2898 in reviewboard: ssh+svn access no more possible in version 1.7.5

2013-02-12 Thread reviewboard
Comment #3 on issue 2898 by andreasf...@gmail.com: ssh+svn access no more possible in version 1.7.5 http://code.google.com/p/reviewboard/issues/detail?id=2898 Timezones on server and client are both CET. So this seems not to be the problem... -- You received this message because you are