It was broken in rocko too. I added this to local.conf to workaround the
problem:
PREFERRED_VERSION_refpolicy-standard = "2.20170204"
-steve
Sinan Kaya wrote:
> Hi,
>
> We realized today that SELinux does not compile on sumo branch.
>
> Is it possible for someone to branch the last
Hi,
We realized today that SELinux does not compile on sumo branch.
Is it possible for someone to branch the last working version to a sumo branch?
http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/refs/
NOTE: Running task 352 of 2707
On Wed, Oct 17, 2018 at 5:12 AM, Dhanush K.S wrote:
> Hi Yocto,
>
> I have my bitbake environment set up on the host system CentOS 7 and
> building images for the target ARM cortex A8 with the following BUILD
> CONFIGURATION,
>
> Build Configuration:
> BB_VERSION = "1.37.0"
> BUILD_SYS
tpm2.0-tss package names changed, update accordingly
Signed-off-by: Armin Kuster
---
meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
On 10/17/18 8:55 AM, Mark Hatle wrote:
> On 10/17/18 9:33 AM, Joshua Watt wrote:
>> I was wondering if meta-oracle-java is still maintained? It looks like
>> there haven't been any release branches created since pyro.
>>
>> We are looking at using it to provide virtual/java-native for some
>>
On 10/17/18 9:33 AM, Joshua Watt wrote:
> I was wondering if meta-oracle-java is still maintained? It looks like
> there haven't been any release branches created since pyro.
>
> We are looking at using it to provide virtual/java-native for some
> build host tools we have that were written in
I was wondering if meta-oracle-java is still maintained? It looks like
there haven't been any release branches created since pyro.
We are looking at using it to provide virtual/java-native for some
build host tools we have that were written in Java, but I want to make
sure that it isn't going to
Please remember to CC the list.
On Wed, 17 Oct 2018 at 14:18, Alberto Eusebi wrote:
> On Monday 15 October 2018, alle 17:57, Burton, Ross wrote:
> > Add nativesdk-python-core and nativesdk-python-modules to
> > TOOLCHAIN_HOST_TASK (using _append).
>
> But the resulting script don't work, it
Hi Yocto,
I have my bitbake environment set up on the host system CentOS 7 and
building images for the target ARM cortex A8 with the following BUILD
CONFIGURATION,
Build Configuration:
BB_VERSION = "1.37.0"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal-4.8"
Alternatively if you're using RPMs, you can set PACKAGE_EXCLUDE =
"python3-core":
Error:
Problem 1: conflicting requests
- nothing provides python3-core needed by dnf-2.7.5-r0.corei7_64
Problem 2: conflicting requests
- nothing provides python3-core needed by rpm-1:4.14.2-r0.corei7_64
In
Easiest way to determine what is pulling it in is to try removing the
package on the target using the package manager. That will tell you
what dependencies are keeping it in.
Ross
On Wed, 17 Oct 2018 at 08:32, Marwen BRIKCHA wrote:
>
> Yes. I've seen compilation log and it does do_install in
I suggest trying other reference image.
For example, core-image-minimal.
If it does not help, then core-image-full-cmdline.
Let's get the working reference first with one of these images.
--- Kosta Z.
From: Zoran Stojsavljevic
Sent: Wednesday, 17 October
Hello Kosta and others,
I am a bit behind on a schedule on this one. Albeit I followed the
advise, This does work for compiling and adding all these packages to
the ROOTFS. I see that after I added all them, I see the
initramfs.tar.xz expanded in
...poky/build/tmp/deploy/image/beagleboneblack/
Yes. I've seen compilation log and it does do_install in final image.
It's installed in /usr/lib64/python3.5 on RootFS.
Le mer. 17 oct. 2018, à 00 h 48, Burton, Ross a
écrit :
> On Tue, 16 Oct 2018 at 14:06, Marwen BRIKCHA
> wrote:
> >
> > because, when i run :
> > :
> > $> bitbake -v opencv
>
Maybe update the documentation I think Andre McCurdy stated it clearly.
English is not my first language but maybe something like
"Depending on when a QA test is running it may or may not be disabled
per-package basis. For example "already-stripped" can only be applied on
INSANE_SKIP_${PN} while
We have already set the layer's compatible version info in the
layer.conf, but we lack this info in the layerindex database.
Add support to parse this info and set it in the corresponding tables.
We plan to use this to filter the layerindex results.
Signed-off-by: Kevin Hao
---
16 matches
Mail list logo
