This mail was sent out by Recipe reporting system.
This message list those recipes which need to be upgraded. If maintainers
believe some of them needn't to upgrade at this time, they can fill
RECIPE_NO_UPDATE_REASON in respective recipe file to ignore this remainder
until newer upstream version w
On 2016-06-12 9:40 PM, Kunihiko Hayashi wrote:
Hello, all
Now I'm trying to build my own kernel with linux-yocto recipe,
and I make kernel configuration fragments (".cfg" file) according to
"Linux Kernel Development Manual", and my fragments can't be applied
to the kernel at all.
I find that li
Hello, all
Now I'm trying to build my own kernel with linux-yocto recipe,
and I make kernel configuration fragments (".cfg" file) according to
"Linux Kernel Development Manual", and my fragments can't be applied
to the kernel at all.
I find that linux-yocto recipe uses "allnoconfig" as default, a
more nitpicky pedantry, but is there any value in removing obviously
dated references from some of the YP web pages? i just googled on
"openembedded smart package manager", and the very first hit took me
here:
https://www.yoctoproject.org/blogs/khem/2013/get-smart-smart-package-manager
which t
Fixed:
sepolgen-1.2.3: sepolgen: Files/directories were installed but not shipped in
any package:
/usr
/usr/lib
/usr/lib/python
/usr/lib/python/site-packages
/usr/lib/python/site-packages/sepolgen
/usr/lib/python/site-packages/sepolgen/lex.py
/usr/lib/python/site-packages/sepolgen/ma
Fixed:
semanageswig_wrap.c:147:21: fatal error: Python.h: No such file or directory
Signed-off-by: Robert Yang
---
recipes-security/selinux/libsemanage.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-security/selinux/libsemanage.inc
b/recipes-security/selinux/lib