Re: [OE-core] [PATCH] pseudo: Remove mismatched inodes from the db

On Tue, 2020-09-22 at 12:52 -0500, Seebs wrote: > On Tue, 22 Sep 2020 18:22:18 +0100 > "Richard Purdie" wrote: > > > The "fun" here is that "make install" is rewriting Makefiles within > > the source code tree. The install step runs under pseudo, earlier > > ones do not. > > If we rerun earlier

Re: [OE-core] [PATCH] pseudo: Remove mismatched inodes from the db

On Tue, 22 Sep 2020 18:22:18 +0100 "Richard Purdie" wrote: > The "fun" here is that "make install" is rewriting Makefiles within > the source code tree. The install step runs under pseudo, earlier > ones do not. > If we rerun earlier non-pseudo steps, the Makefiles get reset to their > original

Re: [OE-core] [PATCH] pseudo: Remove mismatched inodes from the db

On Tue, 2020-09-22 at 11:06 -0500, Seebs wrote: > On Tue, 22 Sep 2020 14:18:24 +0100 > "Richard Purdie" wrote: > > > This can happen when files are deleted outside of pseudo context and > > the inode is reused by a new file which pseduo then "sees". > > In terms of the original design: This

Re: [OE-core] [PATCH] pseudo: Remove mismatched inodes from the db

On Tue, 22 Sep 2020 14:18:24 +0100 "Richard Purdie" wrote: > This can happen when files are deleted outside of pseudo context and > the inode is reused by a new file which pseduo then "sees". In terms of the original design: This would be considered a usage bug, and pseudo issues diagnostics

[OE-core] [RFC PATCH 0/4] fix externalsrc task dependency issues

This is all entirely untested, hence RFC. But if this doesn't work for some reason, I think externalsrc.bbclass should grow some comments as to why deltask is used instead of the noexec flag. Patch 4 is a revert of patch 1, but I did it that way to facilitate backporting, in case patch 2 is too

[OE-core] [RFC PATCH 4/4] Revert "kernel.bbclass: ensure symlink_kernsrc task gets run even with externalsrc"

With the changes to externalsrc.bbclass to make tasks noexec instead of deleting them, we no longer need to explicitly make do_symlink_kernsrc a dependency of do_configure. Signed-off-by: Rasmus Villemoes --- meta/classes/kernel.bbclass | 5 + 1 file changed, 1 insertion(+), 4 deletions(-)

[OE-core] [RFC PATCH 2/4] externalsrc.bbclass: make SRCTREECOVEREDTASKS noexec instead of deleting them

The preferred way to prevent a task from running is not to deltask it, but setting the noexec flag. That way various implicit dependencies through the task in question are preserved, avoiding ad hoc workarounds, such as the one right here. Signed-off-by: Rasmus Villemoes ---

[OE-core] [RFC PATCH 3/4] kernel-yocto.bbclass: remove now unnecessary externalsrc workaround

Now that SRCTREECOVEREDTASKS gets marked as noexec rather than being deltask'ed, do_kernel_configme is still ordered after do_patch (and recursively, after do_unpack), so this workaround is no longer needed. Signed-off-by: Rasmus Villemoes --- meta/classes/kernel-yocto.bbclass | 6 -- 1

[OE-core] [RFC PATCH 1/4] kernel.bbclass: ensure symlink_kernsrc task gets run even with externalsrc

Commit c5dfc2586b41 (kernel.bbclass: run do_symlink_kernsrc before do_patch) fixed a race between do_symlink_kernsrc and do_populate_lic. However, I missed the fact that when externalsrc.bbclass is in use, the do_patch task doesn't exist, meaning that do_symlink_kernsrc now doesn't get run at all,

Re: [OE-core] [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename

Can you please update the documentation to reflect this bbclass rename? Patrick Vacek maintainer of meta-updater mentioned in one PR that the documentation doesn't mention features_check.bbclass: https://github.com/advancedtelematic/meta-updater/pull/771#issuecomment-683618949 It's mentioned in

[OE-core] Yocto Project Status WW38'20

Current Dev Position: YP 3.2 M4 Next Deadline: YP 3.2 M4 Feature Freeze - Now Next Team Meetings: * Bug Triage meeting Thursday Sept. 24th at 7:30am PDT ( https://zoom.us/j/454367603) * Monthly Project Meeting Tuesday Oct. 6th at 8am PDT (

[OE-core] [PATCH] meta: add/fix invalid Upstream-Status tags

Signed-off-by: Ross Burton --- .../systemd/systemd/0001-Use-PREFIX-ROOTPREFIX-correctly.patch | 2 +- ...1-setup.py-pass-missing-libraries-to-Extension-for-mul.patch | 2 +- .../qemu/qemu/0001-qemu-Do-not-include-file-if-not-exists.patch | 2 +-

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

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:

Re: [OE-core] [PATCH 1/2] dropbear/openssh: Lower priority of key generation

Met vriendelijke groet / kind regards, Mike Looijmans System Expert TOPIC Embedded Products B.V. Materiaalweg 4, 5681 RJ Best The Netherlands T: +31 (0) 499 33 69 69 E: mike.looijm...@topicproducts.com W: www.topicproducts.com Please consider the environment before printing this e-mail On

[OE-core] [PATCH] pseudo: Remove mismatched inodes from the db

Currently, where pseudo finds a database entry for an inode but the path doesn't match, it reuses that database entry metadata. This is causing real world "corruption" of file attributes. See [YOCTO #14057] for an example of this. This can happen when files are deleted outside of pseudo context

[OE-core] [PATCH] linux-yocto/beaglebone: Switch to sdhci-omap driver

From: Bruce Ashfield Integrating the following commit(s) to linux-yocto/.: 541066c5b1e beaglebone: Switch to sdhci-omap driver Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-rt_5.8.bb | 2 +- meta/recipes-kernel/linux/linux-yocto-tiny_5.8.bb | 2 +-

Re: [OE-core][RFC] openssh: Start key generation in multi-user mode

On Tue, Sep 22, 2020, 12:14 AM Khem Raj wrote: > On Mon, Sep 21, 2020 at 5:45 PM Joshua Watt wrote: > > > > The sshkeygen uses a lot of CPU time which delays booting (especially in > > the case where no SSH connection is going to happen), but we also want > > to be proactive about generating it

Re: [OE-core] QA notification for completed autobuilder build (yocto-3.2_M3.rc1)

Hello all, This is the full report for yocto-3.2_M3.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary Beaglebone can not boot up, hence all beaglebone test case are blocked in this release. No high milestone

Re: [OE-core] [PATCH 0/3] Import two python recipes from meta-oe/meta-python

On Mon, 2020-09-21 at 23:57 -0700, Khem Raj wrote: > > On 9/21/20 5:12 AM, Richard Purdie wrote: > > We have a slightly pressing situation where the performance test builds > > are failing after we cleaned up the system installs on those machines > > and tried to switch over to buildtools

[OE-core] [PATCH 1/2] systemd: disable xdg-autostart generator by default

From: Kai Kang xdg-autostart generator is an opt-in feature which is imported by commit: 470c58ba45 systemd: Upgrade v245.6 -> v246 The generator outputs unexpect log info on terminal when log in a image which includes an X desktop such as Xfce. So add an package config and disable it by

[OE-core] [PATCH 2/2] kea: fix conflict between multilibs

From: Kai Kang There are conflict of config files between kea and lib32-kea: | Error: Transaction test error: | file /etc/kea/kea-ctrl-agent.conf conflicts between attempted installs of lib32-kea-1.7.10-r0.core2_32 and kea-1.7.10-r0.core2_64 | file /etc/kea/kea-dhcp4.conf conflicts

Re: [OE-core] [PATCH 0/3] Import two python recipes from meta-oe/meta-python

On 9/21/20 5:12 AM, Richard Purdie wrote: We have a slightly pressing situation where the performance test builds are failing after we cleaned up the system installs on those machines and tried to switch over to buildtools entirely. The issue is the need for jinja2, complicated by the