Not support the cm10.2 stable

[xxsunyxx]

log: http://codepad.org/P5mvwjHx.

rom: http://download.cyanogenmod.com/get/jenkins/49874/cm-10.2.0-maguro.zip

[mateor]

Actually. this log indicates something else. The auto_patcher unfortunately is not playing nice with NTFS partitions, as well as some other networked partitions, when using Cygwin.

If you can use fat32 you will likely have success. See these issues for more info if you want details.

[xxsunyxx]

THX, I will try it on a fat32 drive and feedback ASAP.

[mateor]

Closing due to presumed solution. reopen if necessary.

[viulian]

Hello,

I spend few hours trying to get the auto-patcher to work on Windows, either using the NTFS drive (C: drive) as well as a memory stick (imagine how slow it is) which I have formatted to FAT32.

For me it is clear that is NOT an NTFS/FAT32 problem. I also tried on a different laptop. However, I decided to give it one more try on an Ubuntu9 VM machine I have laying around, and magic, patching the latest CM11 for LG G2 worked perfect from the first try, no need to do anything else ...

I suspect you build / test auto-patcher on a Linux / *NIX machine :) since it was that easy ...

[mateor]

Yep, I have linux. The Cygwin support was added by a user who has left
the project. I do my best to maintain it without having access to a
Windows box ;-)

The problem is an execution of some of the bash commands through cygwin.
Without a box to test, injecting the proper debugging has been
challenging. I believe the problem is tied to the execution of the patch
commands, but it is merely strong conjecture.

Oftentimes, the error is reported as trouble patching the
"preloaded.patch". I tend to have pretty good feedback when I suggest
moving to a non-networked drive, formatted as fat32. Perhaps I should be
on the lookout for pen drives as well.

Your suspicions are based on real experiments while mine is just based
off a sampling of mostly non-technical feedback, so thanks for the report!