Bug 5756 - update-alternatives: symlinks are not created
Summary: update-alternatives: symlinks are not created
Status: RESOLVED INVALID
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Laurentiu Palcu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-01-24 09:47 UTC by Yevhen
Modified: 2014-02-24 08:43 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
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 Yevhen 2014-01-24 09:47:47 UTC 
I've built custom image with busybox included and noticed that symlinks for mkdir, ls, rm and other programs are not created.

In do_rootfs log I have the following error messages:
...
update-alternatives: error: alternative path /bin/busybox.suid doesn't exist
...
update-alternatives: error: alternative path /bin/busybox.nosuid doesn't exist
...
Comment 1 Jessica 2014-01-30 15:41:29 UTC 
Please provide version info for further triage the issue
Comment 2 Paul Eggleton 2014-02-06 15:36:46 UTC 
Yevhen, are you perhaps using a custom busybox config?

We really need some more information to go on here, if you could help us with that it would be much appreciated.
Comment 3 Yevhen 2014-02-06 16:36:18 UTC 
I use standard busybox config.
I'll do update to latest revision and check if problem persists.
Comment 4 Jessica 2014-02-20 15:40:36 UTC 
Any update?
Comment 5 Yevhen 2014-02-23 22:04:41 UTC 
Seems that on latest revision (5ff6cb920f8be9068a23f7bf0cb1b9a9ff1eda5b) everything works as expected.
So this bug can be closed.
Comment 6 Laurentiu Palcu 2014-02-24 08:43:21 UTC 
Closing this since it's been reported as working with latest master.