| 1 |
On Mon, Jul 29, 2013 at 9:45 PM, Mike Gilbert <floppym@g.o> wrote: |
| 2 |
> On Mon, Jul 29, 2013 at 9:41 PM, Mike Gilbert <floppym@g.o> wrote: |
| 3 |
>> On Mon, Jul 29, 2013 at 8:03 PM, Rich Freeman <rich0@g.o> wrote: |
| 4 |
>>> Final output is: |
| 5 |
>>> can't find file to patch at input line 17 |
| 6 |
>>> (messing with -p doesn't help, which will be obvious from a quick |
| 7 |
>>> inspection of the file vs the tree) |
| 8 |
>> |
| 9 |
>> Try applying the patches with patch -p1. |
| 10 |
> |
| 11 |
> I just noticed that you said you messed with patch -p, but somehow I |
| 12 |
> don't believe you. ;-) |
| 13 |
|
| 14 |
Hmm, the issue might be becoming less hazy. |
| 15 |
|
| 16 |
Does the file starting with 0001 in your case apply to the files: |
| 17 |
setup.py | 2 +- |
| 18 |
tmdb3/tmdb_api.py | 1 + |
| 19 |
tmdb3/util.py | 4 ++++ |
| 20 |
3 files changed, 6 insertions(+), 1 deletion(-) |
| 21 |
|
| 22 |
If not, then I suspect this behavior varies depending on the version |
| 23 |
of git installed, or perhaps even something else. |
| 24 |
|
| 25 |
I'm getting patches that purport to apply to README files and contain |
| 26 |
lines of code. I suspect there is a bug in the version of git I'm |
| 27 |
running (1.8.1.5)... |
| 28 |
|
| 29 |
Rich |
Archives