Bug 4735 - cannot create a layer using Yocto BSP
Summary: cannot create a layer using Yocto BSP
Status: CLOSED OBSOLETE
Alias: None
Product: Eclipse Plugin
Classification: Yocto Project Subprojects
Component: eclipse-plugin (show other bugs)
Version: 1.4.1
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.4.1
Assignee: Tom Zanussi
QA Contact: Alexandru Georgescu
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-06-17 09:14 UTC by Alexandru Georgescu
Modified: 2019-08-29 15:17 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
print screen (177.59 KB, image/png)
2013-06-17 09:14 UTC, Alexandru Georgescu 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Georgescu 2013-06-17 09:14:23 UTC 
Created attachment 1279 [details]
print screen

HOST: Fedora 18 64bit
eclipse-poky:dc9a609c68fe4a6bbbf34d418fd6611489c1d6f7


STEPS TO REPRODUCE
1. Clone poky 1.4.1 and checkout the 1.4.1 RC1 commit.
2. Perform an headless builg for eclipse-poky and install the plugin.
3. Select yocto-bsp from "YoctoProjectTools" and fill in all the needed data: "metadata location, build location, BSP name, BSP output location".
4. Select "layer" from the Kernel architecture dropdown list.
5. Press Next
6. Press Finish

EXPECTED RESULTS
6. Layer can be created.

ACTUAL RESULTS
6. The user cannot finish creating the layer because a message is displayed, asking to select a kernel and a specific branch (see attached). The two fields are read-only so the user cannot modify them.
Comment 1 Jessica 2013-06-20 02:08:00 UTC 
This is due to underneath yocto-bsp script change in 1.4.1 that eclipse plug-in is depends on.  The command that we are using to get valid karch list is:
yocto-bsp list karch

The returning list now is adding the layer as an entry but when we passing layer to further inqury the matching kernel options, there's none.  Thus cause this bug.
Comment 2 Tom Zanussi 2013-06-21 22:24:43 UTC 
Fix sent to poky mailing list.
Comment 3 Tom Zanussi 2013-07-03 20:17:53 UTC 
Pinged and reposted to poky mailing list.
Comment 4 Tom Zanussi 2013-07-09 15:19:30 UTC 
Fixed in poky/master:

04b36b14b6867f7b3495844ead4d3e569c61e6d6

Fixed in poky/dylan:

0d5380fd3f3fa08e1cbade8582c8fc4ece3cceeb
Comment 5 Alexandru Georgescu 2013-11-18 09:07:09 UTC 
verified
Comment 6 Armin Kuster 2019-08-29 15:17:21 UTC 
closing