Changes from V1:
openscap: Clean up DEPENDS. Remove autoconf-archive and dpkg-native from
DEPENDS because we are using CMake/Ninjia now
scap-security-guide: Fix typo: RDEPNEDS_${PN} -> RDEPENDS_${PN}
Yi Zhao (2):
openscap: update recipe
scap-security-guide: update recipe
.../openscap/files
* Add PACKAGECONFIG for gcrypt, nss3 and selinux
* Use EXTRA_OECMAKE rather than EXTRA_OECONF
* Set CMAKE_SKIP_RPATH and CMAKE_SKIP_INSTALL_RPATH instead of chrpath
* Remove ptest since there are many host contamination issues on target.
We will add it back when these issues are solved.
* Drop th
* Set B="${S}/build" to fix the build failure for out of source
directory
* Remove do_complile and do_install. Use the default functions from
cmake.bbclass.
* Install the artifacts to /usr/share rather than /usr/local/share
Signed-off-by: Yi Zhao
---
.../scap-security-guide/scap-security-gui
I see Jean-Marie made this commit
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a34d0d539e5fdf341541fb628652d22289e80512
I'm experiencing problems building and installing more then one node
modules into image:
https://pastebin.com/CXPkqD8j
It says, /usr/lib/node is a FILE and is is
Hello All,
I am trying to create a base image for raspberry-pi cm3(compute module 3)
I am using warrior-21.0.1
I downloaded meta-raspberry-pi from
https://git.yoctoproject.org/git/meta-raspberrypi
I added the layer in bblayer.conf and I have changed the machine variable
in local.conf
to *raspberr
A build flagged for QA (yocto-2.8_M2.rc1) was completed on the autobuilder and
is available at:
https://autobuilder.yocto.io/pub/releases/yocto-2.8_M2.rc1
Build hash information:
bitbake: f5ea06fc2b6713c9f8e85ecf7cb981ae9a84d896
meta-gplv2: 1e2480e50f34e55bdfd5e06f98441e03a3752d5a
meta
It's fully understandable for me, that gcc handling is more complex and harder
to maintain, than other -native recipes.
Nevertheless I am feeling inconsistency, because all native tools can be
delivered in container and native recipes would be not needed at all.
Best regards,
Krzysztof Taborsk
On Wed, Jul 24, 2019 at 02:23:24PM +0300, Dmitry Eremin-Solenikov wrote:
> ima-evm-utils recipe depends on keyutils recipe which is a part of
> meta-security layer.
>
> Signed-off-by: Dmitry Eremin-Solenikov
> ---
> meta-integrity/conf/layer.conf | 2 ++
> 1 file changed, 2 insertions(+)
>
> di
пн, 29 июл. 2019 г. в 12:49, Martin Jansa :
>
> On Wed, Jul 24, 2019 at 02:23:24PM +0300, Dmitry Eremin-Solenikov wrote:
> > ima-evm-utils recipe depends on keyutils recipe which is a part of
> > meta-security layer.
> >
> > Signed-off-by: Dmitry Eremin-Solenikov
> > ---
> > meta-integrity/conf/l
From: Dmitry Eremin-Solenikov
As pointer by Martin Jansa, keyutils package is now a part of meta-oe,
so switch to using keyutils from that layer.
Signed-off-by: Dmitry Eremin-Solenikov
---
meta-integrity/conf/layer.conf | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/me
From: Dmitry Eremin-Solenikov
keyutils are now part of meta-oe, so remove them from meta-security.
Signed-off-by: Dmitry Eremin-Solenikov
---
.../files/fix_library_install_path.patch | 28 --
...ror-report-by-adding-default-message.patch | 42 ---
.../keyutils-test-fix
On Mon, Jul 29, 2019 at 2:15 AM Shravan Singh wrote:
>
> Hello All,
>
> I am trying to create a base image for raspberry-pi cm3(compute module 3)
>
> I am using warrior-21.0.1
> I downloaded meta-raspberry-pi from
> https://git.yoctoproject.org/git/meta-raspberrypi
> I added the layer in bblayer
Did that get your attention? :-)
I am trying to understand why eudev gets pulled into my build, where
it wasn't part of it before. I recently added an initramfs to my
build by setting:
INITRAMFS_IMAGE_BUNDLE="1"
in my machine.conf file. I have a custom, very minimal initramfs.bb
recipe that do
Hi Shravan,
You need to checkout warrior from your meta-raspberrypi repo that you
cloned. It looks as it is on the latest master.
:rjs
On 7/22/19 3:07 PM, Shravan Singh wrote:
> Hello All,
>
> I am trying to create a base image for raspberry-pi cm3(compute module 3)
>
> I am using warrior-21.0.1
All,
The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:
https://wiki.yoctoproject.org/wiki/Bug_Triage#N
On 7/29/19 9:12 AM, Mittal, Anuj wrote:
Hi Hongxu
I have merged these changes but could you send these to meta-intel list
in future please?
OK, I got it
//Hongxu
On Wed, 2019-07-24 at 18:11 +0800, Hongxu Jia wrote:
Since comit [a78c420 libva: check for "opengl" feature] applied in
oe-core,
16 matches
Mail list logo
