I just ran into this bug in runme script from patchomatic - I was writing a patch file called linux-2.6.16.29.patch but there was a BACKUP file called linux-2.6.16.29.patch~ and another one called linux-2.6.patch~ and it seems to be finding the BACKUP files and using them in favor of the actual patch files I am developing. Since the output doesn't tell me which file it is reading, I couldn't tell what was wrong, and wasted quite a lot of time looking at a file that wasn't even being read by runme.