Of *Christian Hammond
*Sent:* Wednesday, August 12, 2015 3:20 PM
*To:* reviewboard@googlegroups.com
*Subject:* Re: Diff currently unavailable
With custom-generated git diffs, the biggest problem people run into is
the revision range not quite being correct. For instance, in this case
troubleshooting thoughts?
Thanks,
Terry
*From:* reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com]
*On Behalf Of *Christian Hammond
*Sent:* Thursday, August 13, 2015 3:49 AM
*To:* reviewboard@googlegroups.com
*Subject:* Re: Diff currently unavailable
That diff
:* reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com]
*On Behalf Of *Christian Hammond
*Sent:* Wednesday, August 12, 2015 2:58 PM
*To:* reviewboard@googlegroups.com
*Subject:* Re: Diff currently unavailable
Hi Terry,
Is this with Git, or something else? How is the diff being
@googlegroups.com] On
Behalf Of Christian Hammond
Sent: Wednesday, August 12, 2015 3:20 PM
To: reviewboard@googlegroups.com
Subject: Re: Diff currently unavailable
With custom-generated git diffs, the biggest problem people run into is the
revision range not quite being correct. For instance, in this case
with a -), with one new line. I
don’t see any odd characters.
Thanks,
Terry
From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On
Behalf Of Christian Hammond
Sent: Wednesday, August 12, 2015 2:58 PM
To: reviewboard@googlegroups.com
Subject: Re: Diff currently unavailable
Hi Terry
Hi Terry,
Is this with Git, or something else? How is the diff being generated?
What's in the .rej file? Any chance there's some whitespace
inconsistencies, form feed characters, etc.?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - https://www.reviewboard.org
Beanbag,
According to the file it downloaded, it's fetching an index page from
gitweb and not a raw copy of the file.
This may be unrelated, but that last ; shouldn't be needed.
Open your reviewboard.log and look for the Fetching file from line with
that URL, when it's broken. See what it is. Then open
Removing last “;” fixed most ‘diff unavailbale’, so far so good, except I still
had one file named ‘index.html’ failed to diff. I didn’t find any ‘fetching
file from’ string in reviewboard.log
--
Qi LUO
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Thursday, 22 August, 2013 at
Hi,
I don't know why that's happening, but just to help with narrowing it down
a bit, I can say that encoding issues for diff content isn't a problem. We
base64-encode all diff content and store it in the database that way in
order to prevent any encoding issues. So what was in the original
I am awaiting for reply.
-Dev
On Feb 12, 2:54 pm, Dev devmeg...@gmail.com wrote:
Hi Christian,
Below is my clear scenario:
1.I have installed ReviewBoard in say 'Server1'
2.SVN server is running in say 'Server2'
3.When i try to view 'View Diff', SVN server is giving me an error
Feb 12
Hi,
Since SSH requires either a password or, in this case, an authorized key,
you have to have a key for the apache user. It's trying to use the apache
user because it's using SSH. Regardless of the user it's trying to log in
as, it's going to use the running user's keys.
If that's a security
No christian.Apache is in 'nologin' mode.So as a apache user i won't
be able to check-out.
On Feb 12, 11:52 am, Christian Hammond chip...@chipx86.com wrote:
So doing a checkout as Apache/lighttpd's user using svn+ssh is working
without a password on that server? What did you do to enable that?
Below is the Log message i got from the SVN server.
Feb 12 14:07:40 XXX sshd[27074]: Failed password for apache
from :::XXX.XXX.XXX.XXX port 39183 ssh2
I guess if i enable apache as password less in the server,there may be
security violence.Is it possible to point out the
Apache's no-login, but you should (as root) be able to sudo as Apache's
user, and you should be able to generate public/private keys for that user
and put it on the SVN server's authorized_keys for the user that Review
Board is trying to connect as.
If you sudo as Apache, you'll need to make sure
Hi Christian,
Below is my clear scenario:
1.I have installed ReviewBoard in say 'Server1'
2.SVN server is running in say 'Server2'
3.When i try to view 'View Diff', SVN server is giving me an error
Feb 12 14:07:40 XXX sshd[27074]: Failed password for apache
from :::XXX.XXX.XXX.XXX
This sounds like an issue between your Review Board server and your SVN
server. Are you having any of these problems from your local box?
Try a checkout from the Review Board server using the same configuration
specified in Review Board. See if you can duplicate it, and if you can get
any debug
Diff generation isn't a problem. In SVN, diffs are generated locally without
talking to the server.
Review Board needs to actually fetch each file in the diff in order to
generate a full side-by-side diff, so it talks to the SVN server before even
taking your generated diff into account.
Can you pl let me know what will be my next step to attack this
problem?
-Dev
On Feb 11, 3:50 pm, Christian Hammond chip...@chipx86.com wrote:
Diff generation isn't a problem. In SVN, diffs are generated locally without
talking to the server.
Review Board needs to actually fetch each file
You should try a checkout from both your local box and from the server
running Review Board, using the same settings (SVN URL, username, password)
that Review Board is using.
This doesn't sound like it's a Review Board issue specifically. It sounds
like a connection issue with SVN.
Did this used
SVN check-out successfull in my client m/c.But when i tried to check-
out from the RB server,it was asking my unix user's password.
I guess when i hit the 'view diff' button,it is looking for unix user
password? Pl correct me if i am wrong.
I am using URL svn+ssh://URL/subversion/data/project/
It probably was.
If you can at all access the server through HTTP, that would be best.
Otherwise, you'll need to configure the web server user's ssh and svn
configuration to allow it to access files without prompting for a password.
Same way you would any other user.
Christian
--
Christian
Cool ..!Let me try now and let you know ..
-Dev
On Feb 11, 4:55 pm, Christian Hammond chip...@chipx86.com wrote:
It probably was.
If you can at all access the server through HTTP, that would be best.
Otherwise, you'll need to configure the web server user's ssh and svn
configuration to
So doing a checkout as Apache/lighttpd's user using svn+ssh is working
without a password on that server? What did you do to enable that?
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com
On Wed, Feb 11, 2009
23 matches
Mail list logo
