Thanks Ross, for the clear explanation.. It did solved my issue and a new
learning of the oe-pkgdata-util …
Once again Thanks.
From: Burton, Ross [mailto:ross.bur...@intel.com]
Sent: Wednesday, November 7, 2018 6:19 PM
To: Mohammad, Jamal M
Cc: ChenQi ; Yocto-mailing-list
Subject: Re: [yocto]
Hi Anibal,
On Wed, 2018-11-07 at 16:25 -0600, Anibal Limon wrote:
> We know the need to execute OE testimage over real HW not only QEMU,
>
> I'm aware that currently there is an implementation on the Yocto
> Autobuilder Helper
> , this initial implementation looks pretty well separating parts f
Hi,
We know the need to execute OE testimage over real HW not only QEMU,
I'm aware that currently there is an implementation on the Yocto
Autobuilder Helper
, this initial implementation looks pretty well separating parts for
template generation [1] and the script to send jobs to LAVA [2].
There
On Wed, 2018-11-07 at 11:15 -0800, akuster wrote:
> On 11/7/18 10:33 AM, Michael Halstead wrote:
> > We add workers to the nightly-bringup pool to test them in a
> > production like
> > enviroment. Include one completely emulated target and one to test
> > virtualization extentions.
>
>
> Would t
On 11/7/18 10:33 AM, Michael Halstead wrote:
> We add workers to the nightly-bringup pool to test them in a production like
> enviroment. Include one completely emulated target and one to test
> virtualization extentions.
Would this be a good indicator to add a new host to the sanity checker
or
We add workers to the nightly-bringup pool to test them in a production like
enviroment. Include one completely emulated target and one to test
virtualization extentions.
Signed-off-by: Michael Halstead
---
config.json | 13 +
1 file changed, 13 insertions(+)
diff --git a/config.jso
Multiple build clusters use the same prefix so we match a more distinctive
string anywhere in the submitter name.
Signed-off-by: Michael Halstead
---
Post/feed.py | 2 +-
Post/views.py | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Post/feed.py b/Post/feed.py
index 745ee
On 11/7/18 6:07 AM, Stefan Agner wrote:
> Hi Alejandro,
>
> On 22.10.2018 16:45, Alejandro Del Castillo wrote:
>> makes sense, sounds like this is going to fix a bunch of nasty
>> intermittent failures, thanks!
>>
>> merged
>
> Thanks for merging!
np
> With the merge in opkg-utils this is no
On Wed, Nov 07, 2018 at 08:33:51AM +0100, Heiko Schocher wrote:
> Hello Kevin, Robert,
>
> Am 06.11.2018 um 09:10 schrieb Heiko Schocher:
> > Hello Kevin, Robert,
> >
> > Am 05.11.2018 um 06:26 schrieb Kevin Hao:
> > > On Sun, Nov 04, 2018 at 12:10:00PM +0200, Robert Berger wrote:
> > > > Hi,
> >
Probably, I'm learning ;-)
On Wed, 7 Nov 2018 at 12:59, Outback Dingo wrote:
> couldnt this have been a udev_append.bb
>
> instead of writing your own my-rules
> On Wed, Nov 7, 2018 at 6:46 PM Markus W wrote:
> >
> > This my bb file and than I have added the following to local.conf
> IMAGE_INST
The curses libraries are split up further, have a look at what else is in
packages-split, or even better use oe-pkgdata-util:
$ oe-pkgdata-util list-pkg-files -p lib32-ncurses
...
lib32-ncurses-libncurses:
/lib/libncurses.so.5
/lib/libncurses.so.5.9
lib32-ncurses-libncursesw:
Hi Alejandro,
On 22.10.2018 16:45, Alejandro Del Castillo wrote:
> makes sense, sounds like this is going to fix a bunch of nasty
> intermittent failures, thanks!
>
> merged
Thanks for merging!
With the merge in opkg-utils this is not yet actively used in OE of
course. So my question: Is there
couldnt this have been a udev_append.bb
instead of writing your own my-rules
On Wed, Nov 7, 2018 at 6:46 PM Markus W wrote:
>
> This my bb file and than I have added the following to local.conf
> IMAGE_INSTALL_append = " my-rules ...".
>
> SUMMARY = "My rules"
> LICENSE = "CLOSED"
> PR = "r1"
>
This my bb file and than I have added the following to local.conf
IMAGE_INSTALL_append = " my-rules ...".
SUMMARY = "My rules"
LICENSE = "CLOSED"
PR = "r1"
SRC_URI = "file://90-interfaces.rules"
do_install[nostamp] = "1"
do_unpack[nostamp] = "1"
do_install () {
install -d ${D}${sysconfdir}/
Thank you for your answer.
My system is produced only from Yoctk Krogoth with deb package, and
package-management turned on into EXTRAS_DISTRO_FEATURES.
The server repository is only my server and there are only the debs
built with yocto.
So I think the dependecies are always ok, because non oth
Hi,
looking for a way to inspect the appearance of the final recipe
after all the .bbappend files have been applied.
Example:
meta-openembedded/meta-oe/recipes-extended/rsyslog/rsyslog_8.29.0.bb
gets appended with:
meta-mylayer/recipes-extended/rsyslog/rsyslog_8.29.0.bbappend
I'm concept
Hi!
*Background:*
In my raspberry project I am developing a nodejs app that needs access to
bluetooth/ble device. I want to run the node application as non root user
for security reasons. In order to get access from within the app, the node
binary need to have the following capability *cap_net_raw
I see libncurses.so file in ncurses-dev folder in packages-split folder.. Do I
need to add lib32-ncurses-dev in local.conf
From: Mohammad, Jamal M
Sent: Wednesday, November 7, 2018 3:08 PM
To: 'ChenQi' ; Yocto-mailing-list
Subject: RE: [yocto] lib32-ncurses not installing in rootfs
There are m
On Fri, 2018-11-02 at 14:03 +0800, Chen Qi wrote:
> The current logic for checking cve tag is not correct. It errors
> out if and only if the patch contains a line which begins with
> CVE-- and contains nothing else.
>
> It will not error out if the patch contains no CVE information, nor
>
Thanks, I didn't know that I could point SRC_URI to a ipk just like a
regullar tar file.
I did that, pointed to our ipk server and it could download the ipk file.
However during the do_rootfs task i got the following error:
ERROR: kelvin-base-image-2.8b4-r0 do_rootfs: Error executing a python
func
On Wed, Nov 7, 2018, 16:44 Markus W I have resolved this issue. My problem was that in my layer I have a
> recipe-core and within that I had the following structure
> udev/udev-extra-rules and udev-extra-rules.bb file and a files dir on
> the same level.
>
> By renaming udev/udev-extra-rules to my
I have resolved this issue. My problem was that in my layer I have a
recipe-core and within that I had the following structure
udev/udev-extra-rules and udev-extra-rules.bb file and a files dir on
the same level.
By renaming udev/udev-extra-rules to my-udev/my-udev-extra-rules it
suddenly worked.
There are many directories inside packages-split folder , lib32-ncurses,
lib32-ncurses-dbg, lib32-ncurses-dev, lib32-ncurses-doc
Looking into lib32-ncurses,
lib32-ncurses
└── usr
├── bin
│ ├── tput
│ └── tset
└── share
└── tabset
├── std
├── st
Check the packages-split/ directory to see how files are put in each
package.
I guess these files are packages into other packages derived from the
ncurses recipe.
Best Regards,
Chen Qi
On 11/07/2018 05:21 PM, Mohammad, Jamal M wrote:
Hi Guys,
I am trying to add 32-bit ncurses into my root
Hi Guys,
I am trying to add 32-bit ncurses into my root file system
I am using intel yocto bsp sumo branch
Here is my local.conf:
require conf/multilib.conf
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"
IMAGE_INSTALL_append = " dpkg gnutls lib32-glibc lib32-libgcc lib32-libstdc++
lib32-gnutls lib3
Hi Anuj,
thanks for the reply. First I need to say that it was insightful from your
side to use virtual/grub-bootconf
and this made things much easier. I only had to add `BBCLASSEXTEND =
"native"` in the grub-efi in
order to get `grub-editconf` for the host and create environment files on
the fly.
On Fri, 2018-11-02 at 14:03 +0800, Chen Qi wrote:
> The current logic for checking cve tag is not correct. It errors
> out if and only if the patch contains a line which begins with
> CVE-- and contains nothing else.
>
> It will not error out if the patch contains no CVE information, nor
>
27 matches
Mail list logo
