Okay. Well, it sounds like for whatever reason, the STDIN or STDOUT pipe to
patch is failing.

What would be interesting is to take the source and dest file and manually
run:

    cat difffile | patch -o somenewfilename oldfile

There should be a /tmp/reviewboard.* directory containing a .diff file and a
file without "-new" that you'd put in the above command line. If there are
several /tmp/reviewboard.* directories, try deleting them all and then
reproduce this.

Also, you might want to look at the diff file and see if it looks sane.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com


On Fri, Oct 23, 2009 at 4:17 PM, Mike Gunderloy <larkw...@gmail.com> wrote:

> Debian 5.0. /usr/bin/patch exists.
>
> Mike
>
> On Oct 23, 2009, at 5:44 PM, Christian Hammond wrote:
>
> Hmm, this is a new one. /usr/bin/patch exists, right?
>
> What distro is this?
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Fri, Oct 23, 2009 at 4:52 AM, Mike Gunderloy <larkw...@gmail.com>wrote:
>
>> Setting up a new Review Board install (1.0.5.1) to experiment with.
>> Install seems to have worked and I've set up a single git repo and used
>> post-review to toss a review request in. But on trying to view the diff I
>> get:
>>
>> [Errno 32] Broken pipe
>>
>> Traceback (most recent call last):
>>   File 
>> "/usr/lib/python2.5/site-packages/ReviewBoard-1.0.5.1-py2.5.egg/reviewboard/diffviewer/views.py",
>>  line 153, in view_diff
>>     interdiffset, highlighting, True)
>>   File 
>> "/usr/lib/python2.5/site-packages/ReviewBoard-1.0.5.1-py2.5.egg/reviewboard/diffviewer/diffutils.py",
>>  line 623, in get_diff_files
>>     large_data=True)
>>   File 
>> "/usr/lib/python2.5/site-packages/Djblets-0.5.5-py2.5.egg/djblets/util/misc.py",
>>  line 162, in cache_memoize
>>     data = lookup_callable()
>>   File 
>> "/usr/lib/python2.5/site-packages/ReviewBoard-1.0.5.1-py2.5.egg/reviewboard/diffviewer/diffutils.py",
>>  line 622, in <lambda>
>>     enable_syntax_highlighting),
>>   File 
>> "/usr/lib/python2.5/site-packages/ReviewBoard-1.0.5.1-py2.5.egg/reviewboard/diffviewer/diffutils.py",
>>  line 345, in get_chunks
>>     new = get_patched_file(old, filediff)
>>   File 
>> "/usr/lib/python2.5/site-packages/ReviewBoard-1.0.5.1-py2.5.egg/reviewboard/diffviewer/diffutils.py",
>>  line 261, in get_patched_file
>>     return patch(filediff.diff, buffer, filediff.dest_file)
>>   File 
>> "/usr/lib/python2.5/site-packages/ReviewBoard-1.0.5.1-py2.5.egg/reviewboard/diffviewer/diffutils.py",
>>  line 110, in patch
>>     p.stdin.write(diff)
>> IOError: [Errno 32] Broken pipe
>>
>>
>> Any ideas?
>>
>>
>> Mike
>>
>>
>>
>> To unsubscribe from this group, send email to
>> reviewboard+unsubscr...@googlegroups.com<reviewboard%2bunsubscr...@googlegroups.com>
>> For more options, visit this group at
>> http://groups.google.com/group/reviewboard?hl=en
>> -~----------~----~----~----~------~----~------~--~---
>>
>>
>
>
> To unsubscribe from this group, send email to
> reviewboard+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/reviewboard?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
>
> > To unsubscribe from this group, send email to
> reviewboard+unsubscr...@googlegroups.com<reviewboard%2bunsubscr...@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/reviewboard?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>

--~--~---------~--~----~------------~-------~--~----~
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/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to