I just noticed that I'm getting one-second resolution on all my
timestamps. This is for both ext4 and vfat partitions, and shows up in ls
--full-time and the stat command. What could account for this? My uname -a
output is "Linux CHROMA1 4.10.17-yocto-preempt-rt #1 SMP PREEMPT Wed Oct
11 12:33:54
On 9/10/19 1:11 AM, Joe MacDonald wrote:
Hi Yi,
[[meta-selinux][PATCH] conf/layer.conf: use BBFILES_DYNAMIC for dynamic layers]
On 19.09.09 (Mon 14:01) Yi Zhao wrote:
From: Robert Yang
The previous code add all BBFILE_COLLECTIONS/recipes*/*/*.bbappend to BBFILES,
which causes the parsing
Current Dev Position: YP 2.8 M4 Feature Freeze
Next Deadline: YP 3.0 Final Release 25th Oct
SWAT Team Rotation:
* SWAT lead is currently: Paul
* SWAT team rotation: Paul -> Ross on Sept. 13, 2019
* SWAT team rotation: Ross -> Amanda on Sept. 20, 2019
*
On Tue, Sep 10, 2019 at 2:45 AM María del Mar Velasco AERTEC Solutions –
Aerospace & Aviation wrote:
> Hello all,
>
>
>
> I have found that if I write the image using the created *.wic file,
> kernel config is correctly updated (/proc/config.gz and .config are
> coherent). However if I use the
On Tue, Sep 10, 2019 at 08:49:35AM -0400, William Durocher wrote:
> Currently updating a sumo build to warrior. One of our recipe called config
> server uses nodejs which was updated from 8.9 in sumo to 10.5 in warrior.
> As an interim solution we decided to keep the version of nodejs to 8.90.
>
Currently updating a sumo build to warrior. One of our recipe called config
server uses nodejs which was updated from 8.9 in sumo to 10.5 in warrior.
As an interim solution we decided to keep the version of nodejs to 8.90.
However I am getting the following exception in the package_qa step:
Hello all,
I have found that if I write the image using the created *.wic file, kernel
config is correctly updated (/proc/config.gz and .config are coherent). However
if I use the created *.ext4 file to write a rootfs partition of target,
previous kernel config still remains (kernel config
On Fri, 2019-09-06 at 11:52 -0700, Kaz Kylheku wrote:
> Hi,
>
> I'm looking at meta/lib/oe/package.py, function strip_execs, under
> Yocto
> 2.5.
>
> It has this tidbit:
>
> if s.st_ino in inodes:
> os.unlink(file) # <---
> of
