This is a question about patch, not about python-ogre, but just to give some context to my question : I'm following some instructions on some wiki about how to install python-ogre and at some point patch needs to run and do something, and fails. So undaunted, I run the command again, and look at the .patch file it's running, and the files that should be getting patched and everything looks sensible to me - I can see the line in the .h file that needs commenting out according to the patch file, and I can see what it should be replaced with, and patch has found the files, but it just won't do it, and all it says is:
patching file ogre/Samples/Common/include/ExampleFrameListener.h
Hunk #1 FAILED at 41.
1 out of 1 hunk FAILED -- saving rejects to file ogre/Samples/Common/include/ExampleFrameListener.h.rej
which isn't very useful. So I add the --verbose flag, and the only difference now is that it says:
Hmm... Looks like a unified diff to me... :confused:
Patching file ogre/Samples/Common/include/ExampleFrameListener.h using Plan A... (Am I supposed to know what Plan A is, or how this is any better / worse than Plans B, C or D, and whether this is related to it not working?)
So for my particular python-ogre problem I'm just going to do the patch by hand using a text editor since I can see exactly what the .patch file is trying to do and where, and it looks perfectly sensible to me, and then I'll see what happens, BUT my question about patch in general is:
When patch fails, is there any way of finding out why it fails? If the patch file is there, and I look inside it and can find the file it's trying to patch, and the line in the file, and I can't see any reason for it not working, then what do I do next? Just patch the files by hand?