2717 2012-07-07 22:30:31 +0000 python call tracing when a patch fails to apply 2012-07-09 11:33:06 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 1.1.2 x86 Multiple RESOLVED WONTFIX Undecided normal --- 1 laurentiu.serban richard.purdie poky.bs.watcher poky.watcher --- --- --- oldest_to_newest 22886 0 laurentiu.serban 2012-07-07 22:30:31 +0000 If a patch fails to apply there should not be a python call trace | Patch man-1.6e-security.patch does not apply (enforce with -f) | | ERROR: The stack trace of python calls that resulted in this exception/failure was: | ERROR: File "patch_do_patch", line 136, in <module> | ERROR: | ERROR: File "patch_do_patch", line 133, in patch_do_patch | ERROR: | ERROR: File "/home/lserban/work/edison/meta/lib/oe/patch.py", line 338, in Resolve | ERROR: raise sys.exc_value | ERROR: | ERROR: The code that was being executed was: | ERROR: 0132: raise bb.build.FuncFailed(str(sys.exc_value)) | ERROR: 0133: resolver.Resolve() | ERROR: 0134: | ERROR: 0135: | ERROR: *** 0136:patch_do_patch(d) | ERROR: 0137: | ERROR: (file: 'patch_do_patch', lineno: 136, function: <module>) | ERROR: 0129: patchset.Import({"file":local, "remote":url, "strippath": striplevel}, True) | ERROR: 0130: except Exception: | ERROR: 0131: import sys | ERROR: 0132: raise bb.build.FuncFailed(str(sys.exc_value)) | ERROR: *** 0133: resolver.Resolve() | ERROR: 0134: | ERROR: 0135: | ERROR: 0136:patch_do_patch(d) | ERROR: 0137: 22900 1 richard.purdie 2012-07-09 11:33:06 +0000 Fixing errors such as this was one of the objectives of the 1.2 release which predates 1.1.x. We've not had requests for this in 1.1 so I'm proposing we don't backport thse changes (which could be fairly invasive) unless someone requests it.