Yes, technically it would be the same. Thanks for the hint.
Vyacheslav
On 15.11.2021 21:56, Alexander Kanavin wrote:
Can't we achieve the same by abstracting the common part into a
function and defining the two tests explicitly?
Alex
On Mon, 15 Nov 2021 at 21:26, Vyacheslav Yurkov
wrote:
Hi There,
I am working on a yocto image for the imx8 board, for this I have created a
project with zeus layers for all layers(including meta-imx) using the below
manifest file.
repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b
imx-linux-zeus -m imx-5.4.47-2.2.0.xml
I am
On 11/16/21 04:24, Anuj Mittal wrote:
Please review these changes for hardknott. No issues seen while testing
on autobuilder.
Thanks,
Anuj
The following changes since commit 0ca080a23c2770a15138f702d4c879bbd90ca360:
build-appliance-image: Update to hardknott head revision (2021-11-04
Hi Anuj,
I'm sorry regarding the patch subject.
The patch is for the master branch. However, the same issue exists for
other branches as well.
I will check the comments from others and will post the patch to the
Hardknott branch once it's approved in the master branch.
Thanks,
Pgowda
On Tue,
llvm embeds the repository location in a header file. We just changed
the SRC_URI to fetch using https instead of git. This has started giving
errors in reproducibility testing when one of the RPMs to be compared is
fetched from sstate.
Bump HASHEQUIV_HASH_VERSION and PR so its rebuilt.
From: Alexander Kanavin
layout_libdir has not been defined for many years.
Signed-off-by: Alexander Kanavin
Signed-off-by: Richard Purdie
(cherry picked from commit 2c84fbed676a8e6717592c86c3742566ad0decac)
Signed-off-by: Anuj Mittal
---
meta/classes/cross-canadian.bbclass | 2 +-
1 file
From: Richard Purdie
Following the scripted conversion adding branches to git://
SRC_URI entries, add the remaining references, mainly in the selftests
and recipetool.
Signed-off-by: Richard Purdie
(cherry picked from commit 5340c0d688036c1be6c938f05d8a8c1e3b49ec38)
Signed-off-by: Anuj Mittal
Add branch name explicitly to SRC_URI where it's not defined and switch
to using https protocol for Github projects.
The change was made using convert-srcuri script in scripts/contrib.
Signed-off-by: Anuj Mittal
---
meta-selftest/recipes-test/devtool/devtool-upgrade-test2_git.bb | 2 +-
From: Richard Purdie
This script handles two emerging issues:
1. There is uncertainty about the default branch name in git going forward.
To try and cover the different possible outcomes, add branch names to all
git:// and gitsm:// SRC_URI entries.
2. Github are dropping support for git://
From: Chen Qi
CVE-2021-36217 is treated as a duplicate of CVE-2021-3502.
Update the local-ping.patch to mark it resolve both.
Signed-off-by: Chen Qi
Signed-off-by: Richard Purdie
(cherry picked from commit 4d75d6c39f1faeb38191b55f1fa9311b63fcfb29)
Signed-off-by: Anuj Mittal
---
From: Jose Quaresma
This patch is a fixup for 676757f "sstate: fix touching files inside pseudo"
running the 'id' command inside the sstate_unpack_package
function shows that this funcion run inside the pseudo:
uid=0(root) gid=0(root) groups=0(root)
The check for [ -w ${SSTATE_PKG} ] and [
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto-rt/5.10:
f01089784fd6 Linux 5.10.73-rt54
f34df8f3c666 Linux 5.10.65-rt53
271c5e6e4064 Linux 5.10.59-rt52
1a4bba4bc32c locking/rwsem-rt: Remove might_sleep() in __up_read()
ff591a2bdcfb Linux 5.10.59-rt51
From: Bruce Ashfield
Updating linux-yocto/5.10 to the latest korg -stable release that comprises
the following commits:
378e85d1aeb5 Linux 5.10.76
cfa79faf7e1f pinctrl: stm32: use valid pin identifier in
stm32_pinctrl_resume()
c56c801391c3 ARM: 9122/1: select HAVE_FUTEX_CMPXCHG
From: Alexander Kanavin
License-Update: additional firmwares listed
Signed-off-by: Alexander Kanavin
Signed-off-by: Richard Purdie
(cherry picked from commit 1ca3fb1c7f11e04bf8d8bf59901ddd60178cb13c)
Signed-off-by: Anuj Mittal
---
...{linux-firmware_20210919.bb =>
From: Manuel Leonhardt
Previously, when shortening sstate filenames, the reserved
characters for .siginfo were not considered, when siginfo=False,
resulting in differently shortend filenames for the sstate and siginfo
files. With this change, the filenames of the truncated sstate and
siginfo
From: Richard Purdie
Add fcntl64 wrapper which hopefully fixes issues seen in findutils and the find
command in the libtool removal code when built with LFS compile flags on Gentoo.
Signed-off-by: Richard Purdie
(cherry picked from commit f26867fe4daec7299f59a82ae4a0d70cceb3e082)
Please review these changes for hardknott. No issues seen while testing
on autobuilder.
Thanks,
Anuj
The following changes since commit 0ca080a23c2770a15138f702d4c879bbd90ca360:
build-appliance-image: Update to hardknott head revision (2021-11-04 11:58:28
+)
are available in the Git
From: Richard Purdie
Pulls in:
pseudo_db: Flush DB if there is a shutdown request
fcntl: Add support for fcntl F_GETPIPE_SZ and F_SETPIPE_SZ (test fix)
Signed-off-by: Richard Purdie
(cherry picked from commit 0882095d608ce3abbcc9814517434c21ea549063)
Signed-off-by: Anuj Mittal
---
From: Richard Purdie
Signed-off-by: Richard Purdie
(cherry picked from commit 73d3efbaeb2f412ab8d3491d2da3f3124fc009f3)
Signed-off-by: Anuj Mittal
---
meta/recipes-support/libunistring/libunistring_0.9.10.bb | 1 +
1 file changed, 1 insertion(+)
diff --git
This doesn't look hardknott related. Is this for master?
Thanks,
Anuj
On Mon, 2021-11-15 at 06:03 -0800, Pgowda wrote:
> rust-cross-* imported from meta-rust has incorrect signatures,
> depending on MACHINEOVERRIDES making it effectively MACHINE_ARCH
> as shown by sstate-diff-machines.sh:
>
>
On 11/15/21 17:44, Jim Wilson wrote:
This fixes an arch linux gdb configure error with liblzma installed.
Without the --with-liblzma-prefix option, when configuring the target
gdb, gdb configure may find the native liblzma (on a non-multiarch
system) and try to use it, which gives a configure
This fixes an arch linux gdb configure error with liblzma installed.
Without the --with-liblzma-prefix option, when configuring the target
gdb, gdb configure may find the native liblzma (on a non-multiarch
system) and try to use it, which gives a configure error. We already
use
0001-meson-use-partial_dependency-to-get-include-director.patch
removed since it is included in 249.6
Signed-off-by: Wang Mingyu
---
...md-boot_249.5.bb => systemd-boot_249.6.bb} | 0
meta/recipes-core/systemd/systemd.inc | 2 +-
...l_dependency-to-get-include-director.patch | 46
Signed-off-by: Wang Mingyu
---
.../recipes-extended/ethtool/ethtool/avoid_parallel_tests.patch | 2 +-
.../ethtool/{ethtool_5.14.bb => ethtool_5.15.bb}| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-extended/ethtool/{ethtool_5.14.bb =>
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:
On Tuesday, 9 November 2021 08:01:38 NZDT Saul Wold wrote:
> On 11/4/21 2:20 PM, Joshua Watt wrote:
> > On 11/4/21 3:50 PM, Richard Purdie wrote:
> >> On Thu, 2021-11-04 at 15:45 -0500, Joshua Watt wrote:
> >>> On 11/4/21 3:43 PM, Richard Purdie wrote:
> On Thu, 2021-11-04 at 20:00 +,
Can't we achieve the same by abstracting the common part into a function
and defining the two tests explicitly?
Alex
On Mon, 15 Nov 2021 at 21:26, Vyacheslav Yurkov wrote:
> It's substituted further down into
> def test_sbin_init(self, _, origInit):
>
> parameterized.expand generates two tests
seeing
WARNING: ethtool-5.15-r0 do_patch: Fuzz detected:
Applying patch avoid_parallel_tests.patch
patching file configure.ac
Hunk #1 succeeded at 2 with fuzz 1.
The context lines in the patches can be updated with devtool:
devtool modify ethtool
devtool finish --force-patch-refresh
It's substituted further down into
def test_sbin_init(self, _, origInit):
parameterized.expand generates two tests out of it. The string parameter
is used as a suffix for the test, the rest is used as input parameters,
i.e. the first test would be called with origInit=True, the second one
I can't understand what is supposed to happen, perhaps because it's
incomplete? There's
@parameterized.expand([
("original", True),
("preinit", False),
])
but where is that used?
Alex
On Mon, 15 Nov 2021 at 20:53, Vyacheslav Yurkov wrote:
> This is still work-in-progress, but I'm working on
This is still work-in-progress, but I'm working on overlayfs-etc class,
which would have different behavior depending on an input variable. You
can see the example here
It would be helpful to provide an example of improvements that can be
enabled with it.
Alex
On Mon, 15 Nov 2021 at 20:34, Vyacheslav Yurkov wrote:
> Hi guys,
> I have a suggestion to add https://pypi.org/project/parameterized/ as a
> required package for QA selftests. Together with python
Hi guys,
I have a suggestion to add https://pypi.org/project/parameterized/ as a
required package for QA selftests. Together with python unittest module
it can be useful to increase code coverage and reduce duplication in
case you want to do the same test with different input values.
On 11/15/21 6:03 AM, Pgowda wrote:
rust-cross-* imported from meta-rust has incorrect signatures,
depending on MACHINEOVERRIDES making it effectively MACHINE_ARCH
as shown by sstate-diff-machines.sh:
openembedded-core/scripts/sstate-diff-machines.sh --tmpdir=tmp-glibc \
--machines="qemuarm64
lgtm
On 11/15/21 3:18 AM, Pgowda wrote:
source : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102035
Upstream-Status:
Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=3929bca9ca95de9d35e82ae8828b188029e3eb70]
Upstream-Status:
lgtm
On 11/15/21 3:23 AM, Richard Purdie wrote:
I've tested without this and the ptest results for mips are the same with
and without it so the issue this was fixing in gcc 9 was likely resolved
by gcc 11.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/binutils/binutils_2.37.bb | 4
cmake-native can get pulled into the sysroot via dependencies, but it
is always needed:
| Program cmake found: NO
| ERROR: meson failed
Fixes,
...
File
Thanks, this needs to be updated together with systems itself. You can
squash the two updates together as they share the .inc.
Alex
On Mon 15. Nov 2021 at 16.39, wangmy wrote:
> Signed-off-by: Wang Mingyu
> ---
> .../systemd/{systemd-boot_249.5.bb => systemd-boot_249.6.bb}| 0
>
* Noteworthy changes in release 4.18.0 (2021-11-09) [stable]
- Improve GTK-DOC manual. Closes: #35.
- Improve --help and --version for tools with gnulib. Closes: #37.
- Update gnulib files and various maintenance fixes.
refresh dont-depend-on-help2man.patch
Signed-off-by: Wang Mingyu
---
Signed-off-by: Wang Mingyu
---
.../systemd/{systemd-boot_249.5.bb => systemd-boot_249.6.bb}| 0
meta/recipes-core/systemd/systemd.inc | 2 +-
2 files changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-core/systemd/{systemd-boot_249.5.bb =>
What's Changed
update requirements by @davidism in #1524
test Python 3.10 by @davidism in #1530
test Python 3.11 by @davidism in #1531
Tests: Adapt expected traceback regexes for Python 3.11.0a1 by @hroncok in #1527
simplify CodeType rewriting by @davidism in #1536
native: keep same behavior on
8.11.0:
New functions
The :func:`before_and_after`, :func:`sliding_window`, and :func:`triplewise`
recipes from the Python 3.10 docs were added
:func:`duplicates_everseen` and :func:`duplicates_justseen` (thanks to OrBin
and DavidPratt512)
:func:`minmax` (thanks to Ricocotam, MSeifert04, and
Signed-off-by: Wang Mingyu
---
...ib-metadata_4.8.1.bb => python3-importlib-metadata_4.8.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-importlib-metadata_4.8.1.bb =>
python3-importlib-metadata_4.8.2.bb} (88%)
diff --git
=
Version 1.5.0
=
- Introduce HdyStyleManager for managing color schemes (light/dark) and
high contrast mode.
- Support the cross-platform color scheme preference in the
settings portal.
- HdyPreferencesPage
- Remove adaptive margins to fix default window sizes
-
Signed-off-by: Wang Mingyu
---
.../drm/{libdrm_2.4.107.bb => libdrm_2.4.108.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/drm/{libdrm_2.4.107.bb => libdrm_2.4.108.bb} (97%)
diff --git a/meta/recipes-graphics/drm/libdrm_2.4.107.bb
determinism.patch removed since it is included in 1.12.0
Signed-off-by: Wang Mingyu
---
.../libevdev/libevdev/determinism.patch | 44 ---
...{libevdev_1.11.0.bb => libevdev_1.12.0.bb} | 5 +--
2 files changed, 2 insertions(+), 47 deletions(-)
delete mode 100644
Signed-off-by: Wang Mingyu
---
.../ethtool/{ethtool_5.14.bb => ethtool_5.15.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/ethtool/{ethtool_5.14.bb => ethtool_5.15.bb} (93%)
diff --git a/meta/recipes-extended/ethtool/ethtool_5.14.bb
Alexander Kanavin escreveu no dia segunda,
15/11/2021 à(s) 13:57:
> There is no 1.5.5 release or tag here:
> https://github.com/KhronosGroup/SPIRV-Headers
> so this breaks version checks and automated updates.
>
> If you want to bump SRCREV to a post-release commit, PV should be set like
> this:
As upstream hasn't actually tagged 1.5.5, we should
continue to use 1.5.4 until it does.
Signed-off-by: Alexander Kanavin
---
.../spir/{spirv-headers_1.5.5.bb => spirv-headers_1.5.4.bb} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename
rust-cross-* imported from meta-rust has incorrect signatures,
depending on MACHINEOVERRIDES making it effectively MACHINE_ARCH
as shown by sstate-diff-machines.sh:
openembedded-core/scripts/sstate-diff-machines.sh --tmpdir=tmp-glibc \
--machines="qemuarm64 qemuarm64copy"
There is no 1.5.5 release or tag here:
https://github.com/KhronosGroup/SPIRV-Headers
so this breaks version checks and automated updates.
If you want to bump SRCREV to a post-release commit, PV should be set like
this:
PV = "1.5.4+git${SRCPV}"
I'll send a patch to correct this.
Alex
On Sun, 14
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Will do! :)
This only affects the other patch series though, the recipe itself
should be fine now.
It seems the only question left open is this:
> > I think we can replace the patch 0001-Set-REPO_REV-to-v2.17.3.patch
> > with a post function
> >
Thanks, maybe you should write a test for offline builds as well then :)
Alex
On Mon, 15 Nov 2021 at 13:59, Jasper Orschulko <
jasper.orschu...@iris-sensing.com> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi Alexander,
>
> "[PATCH v3] fetch2/repo: Implement AUTOREV for repo
On Mon, 2021-11-15 at 04:58 -0800, Pgowda wrote:
> Source:- https://bugzilla.yoctoproject.org/show_bug.cgi?id=14613
>
> Adds TUNE_PKGARCH to PN so that it picks correct TUNE_FEATURES.
>
Also, the short log needs to be in the format matching our commit guidelines so
something like:
rust-cross:
On Mon, 2021-11-15 at 04:58 -0800, Pgowda wrote:
> Source:- https://bugzilla.yoctoproject.org/show_bug.cgi?id=14613
>
> Adds TUNE_PKGARCH to PN so that it picks correct TUNE_FEATURES.
>
> Signed-off-by: Pgowda
> ---
> meta/recipes-devtools/rust/rust-cross.inc | 2 +-
> 1 file changed, 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Alexander,
"[PATCH v3] fetch2/repo: Implement AUTOREV for repo fetcher" contains a
fix for this issue. Reproducing a build offline with only the DL_DIR
should work now.
We are currently still lacking the appropriate tests for the fetcher.
These
Source:- https://bugzilla.yoctoproject.org/show_bug.cgi?id=14613
Adds TUNE_PKGARCH to PN so that it picks correct TUNE_FEATURES.
Signed-off-by: Pgowda
---
meta/recipes-devtools/rust/rust-cross.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Martin Koppehel
- Implement AUTOINC and submodule support for REPO provider
- Implement full srcrev support
- Add comments and fixup empty DL_DIR initialization
- Distinguish between artificial and plain rev
- Comments/documentation
The previous implementation of the repo fetcher could
Signed-off-by: Ross Burton
---
...1-reading-character-past-end-of-line.patch | 62 ++
...eading-uninitialized-memory-when-giv.patch | 63 +++
meta/recipes-support/vim/vim.inc | 2 +
3 files changed, 127 insertions(+)
create mode 100644
source : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102035
Upstream-Status:
Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=3929bca9ca95de9d35e82ae8828b188029e3eb70]
Upstream-Status:
Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=574e7950bd6b34e9e2cacce18c802b45505d1d0a]
Backport the fix for CVE-2021-43396 ("C stack overflow with coroutines")
from upstream.
Signed-off-by: Richard Purdie
---
...9057a5146755e737c479850f87fd0e3b6868.patch | 43 +++
meta/recipes-devtools/lua/lua_5.4.3.bb| 1 +
2 files changed, 44 insertions(+)
create mode
Backport the fix for CVE-2021-43396. It is disputed that this is a security
issue
however the fix applies easily so we may as well.
Signed-off-by: Richard Purdie
---
.../glibc/glibc/CVE-2021-43396.patch | 184 ++
meta/recipes-core/glibc/glibc_2.34.bb | 1 +
2
I've tested without this and the ptest results for mips are the same with
and without it so the issue this was fixing in gcc 9 was likely resolved
by gcc 11.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/binutils/binutils_2.37.bb | 4
1 file changed, 4 deletions(-)
diff --git
source : https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102035
Upstream-Status:
Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=3929bca9ca95de9d35e82ae8828b188029e3eb70]
Upstream-Status:
Backport[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=574e7950bd6b34e9e2cacce18c802b45505d1d0a]
On Mon, 2021-11-15 at 07:15 +0100, Zoltan Boszormenyi via lists.openembedded.org
wrote:
> 2021. 11. 10. 20:39 keltezéssel, Alexander Kanavin írta:
> >
> > # Xorg requires a SHA1 implementation, pick one
> > XORG_CRYPTO ??= "openssl"
> > -PACKAGECONFIG[openssl] =
waffle currently requires cmake-native because it has the following lines
in git/src/waffle/meson.build.
if meson.version().version_compare('>= 0.50')
cmake = import('cmake')
In case of 'wayland' not being in DISTRO_FEATURES, we will get the
following error at do_configure.
|
66 matches
Mail list logo
