rb-site help

2012-06-28 Thread Daniel Laird
Hi, I am going to use rb-site to dump the data and then import onto a new webserver. Whilst trying to check out the options I noticed that when I do rb-site -h there is no help regarding the manage options. I am going to check the source code - but is this intentional or just an oversight?

Repository ERROR

2012-06-28 Thread Viktor Józsa
Hi! I need urgent assistance. After upgrading from 1.6.9 to the next message I receive any review request: *Something Broke! (Error 500) Something Broke It Appears When You Tried to go to here. Either this is a bug in Review Board or a server configuration error. Please report this to your

Re: rb-site help

2012-06-28 Thread Christian Hammond
Assuming you're not changing database types, the best option is to use your database's tools to perform an SQL dump and import, and copy over the site directory. We don't have any options that do the entire thing for you, as it's dependent on the database type. Christian -- Christian Hammond -

Re: Repository ERROR

2012-06-28 Thread Viktor Jozsa
Hi! The same problem occurs on a test server. What is the problem. Thank you in advance. Regards Viktor -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/

Re: Repository ERROR

2012-06-28 Thread Viktor Jozsa
At some pre-installed with a blank mysql database sqlite database, I spent over an existing data. I think this is the cause of the problem, but it was necessary. Yes, we have a daily backup. But size is 50 Mbytes of compressed.I have included in the scheme. Viktor On Thursday, June 28, 2012

Re: Repository ERROR

2012-06-28 Thread Christian Hammond
Sorry, I don't think I understand. What do you mean by a blank mysql database sqlite database? It sounds like the data in the database that represents the database schema (not the schema itself, but a serialized representation used to handle database migrations) didn't get copied into the new

Re: Repository ERROR

2012-06-28 Thread Viktor Jozsa
I had recently tested reviewboard data export and import in to new database. The old database is SqLite, while the new MySQL. I don't downgrade reviewboard. I will repair the schema and I'll try to update. Thank you very much. Viktor On Thursday, June 28, 2012 12:06:00 PM UTC+2, Christian

Re: Repository ERROR

2012-06-28 Thread Viktor Jozsa
Hi! The database problem is solved. The new scheme is based on re-spent in the database and tested ReviewBoard and site upgrade. All right, no error. But I found other problem in DiffViewer. When I select DiffViewer, get this error. * * *Traceback (most recent call last): File

Fwd: Having trouble with post-review.

2012-06-28 Thread Peter Konneker
Seen several threads on this but no resolution. We set up reviweboard on a server and are trying to post from a different one with an svn server from a post-commit hook, but it's not authenticating in when we try to post. Here's the output when running on debug. Any help is much appreciated.

Re: Having trouble with post-review.

2012-06-28 Thread Peter Konneker
Reviewboard is running on it's own server. So I basically just replaced the default apache config with reviewboard. Looks like it's downloading an xml file? ?xml version=1.0 encoding=utf-8? rsp statok/stat uri_templates

Re: Having trouble with post-review.

2012-06-28 Thread Christian Hammond
That's what I'd expect. I'm surprised by the response from post-review, though. Can you check your Apache log files to look up the entry for that 404? I'm curious what URL post-review is actually accessing. Christian -- Christian Hammond - chip...@chipx86.com Review Board -

Issue 2652 in reviewboard: File not found when uploading DIFF using POST-REVIEW and mercurial repository

2012-06-28 Thread reviewboard
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2652 by xepe...@gmail.com: File not found when uploading DIFF using POST-REVIEW and mercurial repository http://code.google.com/p/reviewboard/issues/detail?id=2652 * NOTE: Do not post confidential information in this bug