Bug 1587 - Patch resolution always fails
Summary: Patch resolution always fails
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium major
Target Milestone: 1.2
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-10-04 07:01 UTC by Gary Thomas
Modified: 2012-05-28 17:35 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments
Console log showing patch failure (4.00 KB, text/x-log)
2011-10-04 07:01 UTC, Gary Thomas
no flags Details
Patch for tested fix on PowerPC hardware (1.65 KB, patch)
2012-05-28 17:31 UTC, Gary Thomas
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Thomas 2011-10-04 07:01:19 UTC
Created attachment 268 [details]
Console log showing patch failure

When a patch fails, bitbake used to bring up a window+shell to let the user resolve it.
This is currently broken.  Here's an example where I purposefully damaged a patch to
make it fail.  In this case, local.conf contains these "terminal" setups:
  TERMCMD = "${XTERM_TERMCMD}"
  TERMCMDRUN = "${XTERM_TERMCMDRUN}"
  OE_TERMINAL = "XTerm"
and the DISPLAY environment variable is set.  Same error without these values
being explicitly set in local.conf

Failure log attached.
Comment 1 Saul Wold 2011-10-21 11:38:15 UTC
*** Bug 1689 has been marked as a duplicate of this bug. ***
Comment 3 Gary Thomas 2012-05-28 17:31:42 UTC
Created attachment 550 [details]
Patch for tested fix on PowerPC hardware
Comment 4 Gary Thomas 2012-05-28 17:35:40 UTC
(In reply to comment #3)
> Created attachment 550 [details]
> Patch for tested fix on PowerPC hardware

This attachment was made in error - I clicked on "add an attachment for #1570" and was taken to this bug thread.  I didn't notice the disconnect...