Thanks!  That solved the problem.

On Wed, Feb 4, 2009 at 3:20 PM, Christian Hammond <[email protected]> wrote:
> You need p4 to be in the Apache user's path somewhere.
>
> This is a common problem. I'm hoping to provide better error docs for this
> before 1.0.
>
> Christian
>
> --
> Christian Hammond - [email protected]
> VMware, Inc.
>
>
> On Wed, Feb 4, 2009 at 11:51 AM, Isaac Wagner <[email protected]> wrote:
>>
>> Thanks.  My perforce authentication was incorrect.  Now my next
>> problem:
>>
>> The post-review submission happens OK with no error messages.
>> However, when I go to review the diff in ReviewBoard it says "diff
>> unavailable" and then gives this stack trace when I click details.
>>
>> Traceback (most recent call last):
>>  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.0alpha2-
>> py2.5.egg/reviewboard/diffviewer/views.py", line 183, in
>> view_diff_fragment
>>    file = get_requested_diff_file()
>>  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.0alpha2-
>> py2.5.egg/reviewboard/diffviewer/views.py", line 159, in
>> get_requested_diff_file
>>    get_chunks)
>>  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.0alpha2-
>> py2.5.egg/reviewboard/diffviewer/diffutils.py", line 613, in
>> get_diff_files
>>    large_data=True)
>>  File "/usr/lib/python2.5/site-packages/Djblets-0.5alpha2-py2.5.egg/
>> djblets/util/misc.py", line 143, in cache_memoize
>>    data = lookup_callable()
>>  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.0alpha2-
>> py2.5.egg/reviewboard/diffviewer/diffutils.py", line 612, in <lambda>
>>    enable_syntax_highlighting),
>>  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.0alpha2-
>> py2.5.egg/reviewboard/diffviewer/diffutils.py", line 341, in
>> get_chunks
>>    old = get_original_file(filediff)
>>  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.0alpha2-
>> py2.5.egg/reviewboard/diffviewer/diffutils.py", line 248, in
>> get_original_file
>>    large_data=True)[0]
>>  File "/usr/lib/python2.5/site-packages/Djblets-0.5alpha2-py2.5.egg/
>> djblets/util/misc.py", line 143, in cache_memoize
>>    data = lookup_callable()
>>  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.0alpha2-
>> py2.5.egg/reviewboard/diffviewer/diffutils.py", line 247, in <lambda>
>>    data = cache_memoize(key, lambda: [fetch_file(file, revision)],
>>  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.0alpha2-
>> py2.5.egg/reviewboard/diffviewer/diffutils.py", line 227, in
>> fetch_file
>>    data = tool.get_file(file, revision)
>>  File "/usr/lib/python2.5/site-packages/ReviewBoard-1.0alpha2-
>> py2.5.egg/reviewboard/scmtools/perforce.py", line 92, in get_file
>>    p = subprocess.Popen(cmdline, stdout=subprocess.PIPE,
>> stderr=subprocess.PIPE)
>>  File "/usr/lib/python2.5/subprocess.py", line 594, in __init__
>>    errread, errwrite)
>>  File "/usr/lib/python2.5/subprocess.py", line 1153, in
>> _execute_child
>>    raise child_exception
>> OSError: [Errno 2] No such file or directory
>>
>>
>>
>> On Feb 4, 2:18 pm, Joshua Slominski <[email protected]> wrote:
>> > When i was setting up review bard with perforce i had this problem alot.
>> >  If
>> > you run "post-review <changenum> -d > output.html", you will get a nice
>> > HTML
>> > doc that will have a stack trace in it.  I normally get the error 500
>> > page
>> > when i need to update my perforce ticket number. I don't use my password
>> > i
>> > use the actual ticket in the repository admin page.  You can get your
>> > ticket
>> > by running "p4 login -a -p".
>> >
>> > On Wed, Feb 4, 2009 at 2:07 PM, Isaac Wagner <[email protected]>
>> > wrote:
>> >
>> > > OK, I solved that problem.  It had to do with a CNAME entry in DNS.
>> >
>> > > Next problem: I get this error message when I try to submit a change:
>> >
>> > > $ post-review 106210
>> > > Unable to access
>> > >http://codereview.mydomain.com/api/json/reviewrequests/new/.
>> > > The host path may be invalid
>> > > HTTP Error 500: Internal Server Error
>> >
>> > > On Feb 4, 1:18 pm, Isaac Wagner <[email protected]> wrote:
>> > > > I've gone through the online documents and believe I followed
>> > > > everything correctly.  When I set up my perforce repository in the
>> > > > admin section of ReviewBoard I set the "path" to the output of
>> > > > "server
>> > > > address" from doing a p4 info.  In my case this looks something like
>> > > > "perforce.mydomain.com:1666".  When I do a post-review CHANGENUM I
>> > > > get
>> > > > the output:
>> >
>> > > > Error creating review request: The repository path specified is not
>> > > > in
>> > > > the list of known repositories (code 206)
>> >
>> > > > Does anyone have any ideas or know what this problem is?
>>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to