Does anyone has any clue about why this is happening?

On Thursday, 10 April 2014 17:11:51 UTC+5:30, neel roy wrote:
>
> Hi,
>
> I am using revieweboard and when I create diff using either post-review or 
> rbt, and upload that diff in reviewboard server I get following error:
>
> *Error:* The patch to '<filename>' didn't apply cleanly. The temporary 
> files have been left in '/tmp/reviewboard.PIc4WJ' for debugging purposes. 
> `patch` returned: patching file /tmp/reviewboard.PIc4WJ/tmp7AAVW9 patch: 
> **** malformed patch at line 10:
>
> When I looked at the patch I found that it really is malformed. So I 
> created a dummy file checked it in, modified it and created a patch. As you 
> can see below the entry near "@@ -20,6 +29,14 @@ See these resources for 
> further informat" will make it malformed (I have marked that section bold 
> but not sure whether it will show up as bold in every editor\browser). I 
> have tried with latest version of RBTools (rbt), one version prior to that 
> (post-review and rbt), and 0.4.1 (post-review). I have tried with 32 bit 
> python and setup tools as well as 64 bit. I have diffutils-2.8.7-1. The 
> only difference that I see is that other machines that I use where I have 
> my code and generate diff are 32 bit machines while this one is 64 bit 
> machine. Have you come across this issue before? How do I solve it?
>
> @@ -9,6 +9,15 @@ New unittest features including test ski
>
>  A much faster io module
>
>  Automatic numbering of fields in the str.format() method
>
>  Float repr improvements backported from 3.x
>
> +
>
> +
>
> +Note: A newer bugfix release, 2.7.4, is currently available. Its use is 
> recommended over previous versions of 2.7.
>
> +
>
> +Python 2.7.3 was released on April 9, 2012. 2.7.3 includes fixes for 
> several reported security issues in 2.7.2: issue 13703 (oCERT-2011-003, 
> hash collision denial of service), issue 14234 (CVE-2012-0876, hash table 
> collisions CPU usage DoS in the expat library), issue 14001 (CVE-2012-0845, 
> SimpleXMLRPCServer denial of service), and issue 13885 (CVE-2011-3389, 
> disabling of the CBC IV attack countermeasure in the _ssl module).
>
> +
>
> +The Python 2.7 series is scheduled to be the last major version in the 
> 2.x series before 2.x moves into an extended maintenance period. The 2.7 
> series contains many of the features that were first released in Python 
> 3.1. Improvements in this release include:
>
> +
>
> +
>
> * Tile support for Tkinter*
>
> * A backport of the memoryview object from 3.x*
>
> * Set literals*
>
> *@@ -20,6 +29,14 @@ See these resources for further informat*
>
>  
>
>  What's new in 2.7?
>
>  Change log for this release.
>
> +
>
> +Note: A newer bugfix release, 2.7.4, is currently available. Its use is 
> recommended over previous versions of 2.7.
>
> +
>
> +Python 2.7.3 was released on April 9, 2012. 2.7.3 includes fixes for 
> several reported security issues in 2.7.2: issue 13703 (oCERT-2011-003, 
> hash collision denial of service), issue 14234 (CVE-2012-0876, hash table 
> collisions CPU usage DoS in the expat library), issue 14001 (CVE-2012-0845, 
> SimpleXMLRPCServer denial of service), and issue 13885 (CVE-2011-3389, 
> disabling of the CBC IV attack countermeasure in the _ssl module).
>
> +
>
> +The Python 2.7 series is scheduled to be the last major version in the 
> 2.x series before 2.x moves into an extended maintenance period. The 2.7 
> series contains many of the features that were first released in Python 
> 3.1. Improvements in this release include:
>
> +
>
> +
>
>  Online Documentation
>
>  Report bugs at http://bugs.python.org.
>
>  Help fund Python and its community.
>
> \ No newline at end of file
>
>

-- 
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to