Bug 6014 - meta-openembedded/../fuse_2.9.3.bb by default doesn't add fusermount to image
Summary: meta-openembedded/../fuse_2.9.3.bb by default doesn't add fusermount to image
Status: RESOLVED INVALID
Alias: None
Product: Other YP Layers
Classification: Build System, Metadata & Runtime
Component: layers (show other bugs)
Version: unspecified
Hardware: Other ppc
: Undecided normal
Target Milestone: ---
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-03-20 10:50 UTC by George Nita
Modified: 2014-03-20 14:58 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
Proposed fix (934 bytes, patch)
2014-03-20 10:50 UTC, George Nita 		no flags Details | Diff
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 George Nita 2014-03-20 10:50:37 UTC 
Created attachment 1843 [details]
Proposed fix

The PACKAGES line is currently:
PACKAGES =+ "fuse-utils-dbg fuse-utils libulockmgr libulockmgr-dev libulockmgr-dbg"
and no fusermount. Without fusermount the '/etc/init.d/fuse status' command exits with error.
Comment 1 Paul Eggleton 2014-03-20 14:58:24 UTC 
We don't track the meta-openembedded layer within the Yocto Project bugzilla, so I'm marking this as invalid. However, if you could send your patch to the openembedded-devel mailing list (with the prefix [meta-filesystems] since that's the layer the fuse recipe appears in, and also CC the layer maintainer hongxu.jia@windriver.com) that would be much appreciated.

(Also, you don't need "Upstream Status" for patches to recipes themselves, only patches to source code where the patch is next to the recipe and referred to in SRC_URI.)
Comment 2 Paul Eggleton 2014-03-20 14:58:57 UTC 
Sorry, I meant the meta-openembedded repository above, rather than meta-openembedded layer.