Re: ReviewBoard 2.5.2 and SVN 1.8.8 - No diffs, no logs.

2016-02-01 Thread Warren Postma
I gave up on installing manually via apt-get on Linux and got it working with BITNAMI installer, and whatever was blocking diff functionality is now gone. W -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check

Re: ReviewBoard 2.5.2 and SVN 1.8.8 - No diffs, no logs.

2016-02-01 Thread Warren Postma
has anyone else seen any reason other than a front-end error why patch output with reviewboard is blank/empty? Warren Postma > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons:

ReviewBoard 2.5.2 and SVN 1.8.8 - No diffs, no logs.

2016-01-26 Thread Warren Postma
I have ReviewBoard 2.5.2 installed on Debian Linux (jessie), the repository configuration seemed to go well, as did the site setup. However when I create a review I can not see any diff content on the Diff page of a review, and downloading a diff gets me an empty 0 byte rb1.patch file. The

Re: ReviewBoard 2.5.2 and SVN 1.8.8 - No diffs, no logs.

2016-01-26 Thread David Trowbridge
First of all, DEBUG is meant for development and having it set to True for production will break things. Can you clarify how you're uploading your diff? Are you using rbtools? Posting a patch by hand? Creating a review request for a committed change from /r/new ? Can you look in the browser's

Re: ReviewBoard 2.5.2 and SVN 1.8.8 - No diffs, no logs.

2016-01-26 Thread Warren Postma
I turned off DEBUG, no change in diff generation problem. I am creating a review request by clicking New Review Request, then using the Create from existing commit on [combobox showing branches and trunk, I selected trunk]. I single-click in the list of changes for the selected branch. I

Re: ReviewBoard 2.5.2 and SVN 1.8.8 - No diffs, no logs.

2016-01-26 Thread Warren Postma
I have GNU Patch 2.7.5 installed on Debian Jessie. (apt-get install patch got that version). That is apparently KEY to patch generation. I wonder if there's any regression in Debian's patches to patch. patch 2.7.5 was released circa 2012, so that seems pretty stable. I checked my command