From: Frederic Martinsons
Without that, the possible git urls that are in SRC_URI of a recipe
are removed from SRC_URI during devtool process and so the
cargo_common_do_patch_paths in cargo_common.bbclass cannot
patch these packages to fetch them locally.
I use a generic type name because I
From: Frederic Martinsons
This recipe is for showing a "real world" example of
a crate that depends on some git repositories.
Usually, this kind of crate is built within a global
workspace (here it is the zbus project) and so
doesn't need a Cargo.lock on its own.
For the sake of the
From: Frederic Martinsons
A project can have multiple Cargo.lock (provides
multiple binaries for example) and each one can
depends on differenct version of the same crates.
Even within the same Cargo.lock file, it is possible
to have different version of same crates.
To avoid conflicts,
From: Frederic Martinsons
This is for a specific case where:
- A recipe use a subpath on a git repo (e.g.
git://repo.git/projects;subpath=subproject)
- The recipe contains a patch to apply
- a devtool modify is used on this recipe
With these conditions, the patch cannot be applied at
From: Frederic Martinsons
To handle url like git://git@repo/project
Signed-off-by: Frederic Martinsons
---
meta/classes-recipe/cargo_common.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/cargo_common.bbclass
From: Alex Kiernan
Since disable network was added cargo configurations which reference git
repos fail as they attempt to fetch across the network as part of
do_compile, even if EXTRA_OECARGO_PATHS to add them as part of `paths`
is used, as this is documented as only working for packages which
From: Frederic Martinsons
This series brings the support of local git repository inside
a cargo based recipe.
It also enables devtool capacity to such a recipe along with
an example of recipe and a new selftest case.
The following changes since commit c3fe173d5196506d89aa464ba56aabcf581a60db:
Hi Nikhil,
is this any different than
https://lists.openembedded.org/g/openembedded-core/message/179335 ?
upon checking i didn't find any difference. However, if there is any difference
or you feel that previously sent patch was wrong, please re-name the patch you
sent as v2.
Regards,
Hello,
The multiple Cargo.lock seems totally valid, a project can have multiple
binaries provided (which is the case for Solana cli suite) so I'll submit a
new v6 of my series to reflect that, I just have to ignored specify dirs
like .git (no use to walk inside it) or .pc (can contains a patched
DESCRIPTION is optional for now; writing good component descriptions
is not easy (but appreciated).
Signed-off-by: Alexander Kanavin
---
meta/recipes-connectivity/inetutils/inetutils_2.4.bb| 1 +
meta/recipes-core/images/core-image-ptest-all.bb| 2 +-
Rebase patches; one of the vendored crossbeam versions
has been removed upstream, and so crossbeam_atomic.patch
is adjusted accordingly.
Replace getrandom-open64.patch with a backport.
Signed-off-by: Alexander Kanavin
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
Absent maintainer entries are as well a frequent source of friction, as they
are checked
only in selftest, and so aren revealed until autobuilder runs.
The selftest is retained as it also checks for obsolete entries in
maintainers.inc
(not possible to do in insane class).
The insane check also
This was done in a selftest, but that is too late and creates
friction in integration as errors are not seen until autobuilder fails.
Bonus fix: SUMMARY check wasn't even working, as in the absence
of one set in the recipe there is a default value set from bitbake.conf.
I left DESCRIPTION check
Upstream does not actually use or test it this way; if the goal
is to install items, then install target should be executed directly.
In particular, in latest rust release building stage 2 items has regressed
altogether (incorrect dependencies between rust-analyze tool and the
libs it needs) and
Otherwise it triggers a rebuild of llvm-dependent rust pieces every time
rust_runx is called,
lengthening the builds without need.
Signed-off-by: Alexander Kanavin
---
meta/recipes-devtools/rust/rust_1.67.1.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Add a patch to gstreamer1.0-libav to address an API compatibility fail.
Signed-off-by: Alexander Kanavin
---
...c-stop-accessing-out-of-bounds-frame.patch | 89 ---
...c-stop-accessing-out-of-bounds-frame.patch | 108 --
.../ffmpeg/ffmpeg/ffmpeg-fix-vulkan.patch
On Fri, Mar 31, 2023 at 1:28 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Fri, 2023-03-31 at 01:16 +0200, Martin Jansa wrote:
> > I've similar one locally, but this one works for me as well.
> >
> > Acked-by: Martin Jansa
>
> I did check your public branches and didn't see
On Fri, 2023-03-31 at 01:16 +0200, Martin Jansa wrote:
> I've similar one locally, but this one works for me as well.
>
> Acked-by: Martin Jansa
I did check your public branches and didn't see it and wanted to get
the other patch in so I quickly put it together!
Cheers,
Richard
* when searching for qemuboot.conf
* don't assume that IMAGE_LINK_NAME is always
- (with -.qemuboot.conf)
* runqemu: use IMAGE_LINK_NAME set by testimage.bbclass or query with bitbake -e
* testimage.bbclass was setting DEPLOY_DIR which I don't see used
anywhere else, so I assume it was
* It was showing whole log and that the runqemu command failed, but not
where the log file is, nor why it thinks the runqemu failed
[YOCTO #12937]
Signed-off-by: Martin Jansa
---
meta/lib/oeqa/selftest/cases/runqemu.py | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff
* it was searching for line like this:
ROOTFS:
[/OE/build/poky/build/build-st-2023-03-20-esdk-runqemu-patch1/runqemu.RunqemuTests.test_boot_machine_ext4/build-st/tmp/deploy/images/qemux86-64/core-image-minimal-qemux86-64-20230320081121.rootfs.ext4]
but with IMAGE_NAME_SUFFIX changed to
* introduced in:
https://git.openembedded.org/openembedded-core/commit/?id=96d4486df6d870ef19e2055b026729e66bc118f3
Signed-off-by: Martin Jansa
---
meta/lib/oeqa/selftest/cases/imagefeatures.py | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
I've similar one locally, but this one works for me as well.
Acked-by: Martin Jansa
On Fri, Mar 31, 2023 at 12:44 AM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> Python modules aren't supposed to have uppercase characters in their names
> according to python conventions. We
Python modules aren't supposed to have uppercase characters in their names
according to python conventions. We have regexs in the code which work
on that assumption too. Rather than showing errors under some filtering
situations, make it clear and error if a problematic name is seen.
I've added the updated .inc files to meta-webosose fork if it's easier to
see there:
https://github.com/shr-project/meta-webosose/commits/master-2023-03-30 (top
2 commits)
this checksum mismatch is also the reason for that ugly exception as
explained in top commit, it's race-condition between
From: Ross Burton
If we try to parse a buildstats directory which was either aborted or
is still being built then the top-level build_stats file doesn't
contain an elapsed value which causes an exception:
UnboundLocalError: local variable 'elapsed' referenced before assignment
Default both
From: Peter Marko
This function is referencing '${S}/..'.
It uses ${S} only as good known directory path to start
traversing from, and it does not need it to exist or be populated.
If ${S} does not exist yet, the function will fail because
it cannot evaluate path .. from non-existing directory.
From: Wang Mingyu
Error: Transaction test error:
file /usr/share/pkgconfig/xcb-proto.pc conflicts between attempted installs
of lib32-xcb-proto-dev-1.15.2-r0.armv7ahf_neon and
xcb-proto-dev-1.15.2-r0.cortexa57
The differences between the two files are as follows:
@@ -2,7 +2,7 @@
From: Martin Jansa
* master branch was removed upstream:
downloads/git2/github.com.intel.bmap-tools $ git remote prune origin
Pruning origin
URL: https://github.com/intel/bmap-tools
* [pruned] refs/heads/master
* [pruned] refs/pull/73/merge
*
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
8020ae3c051d Linux 5.15.103
10a72c677bce Makefile: use -gdwarf-{4|5} for assembler for
DEBUG_INFO_DWARF{4|5}
6e7bc50f97c9 KVM: VMX: Fix crash due to uninitialized current_vmcs
From: Martin Jansa
* with my build/conf/local.conf:
SSTATE_DIR = "/OE/build/poky/build/sstate-cache"
these devtool tests will first set own SSTATE_DIR and the original one set as
SSTATE_MIRROR:
2023-03-11 11:51:46,837 - oe-selftest - INFO -
test_devtool_update_recipe_append
From: Bruce Ashfield
When building a module on target, we use the native compiler
(always "gcc") versus the same compiler, but named in a cross
compiler manner, for the kernel build.
The kernel captures the compiler string in several places,
some of which we are already fixing, but others we
From: Randy MacLeod
Fixes: CVE-2023-1127, CVE-2023-1170, CVE-2023-1175,
CVE-2023-1264, CVE-2023-1355
Signed-off-by: Randy MacLeod
Signed-off-by: Alexandre Belloni
(cherry picked from commit 2415072c3800feb164dd4d1fa0b56bd141a5cbd8)
Signed-off-by: Steve Sakoman
---
From: Bruce Ashfield
Bumping lttng-modules to version v2.13.9-4-g12f43cab, which comprises the
following commits:
da1f5a26 Version 2.13.9
dc2d1294 fix: jbd2: use the correct print format (v5.4.229)
d04c1211 fix: jbd2 upper bound for v5.10.163
4b8864fc fix: jbd2: use the correct
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
d9b4a0c83a2d Linux 5.15.98
937c15e27a63 io_uring: ensure that io_init_req() passes in the right
issue_flags
bf7123dd26a0 Linux 5.15.97
cf7f9cd50013 io_uring: add missing lock
From: Geoffrey GIRY
NVD DB store version and update in the same value, separated by '_'.
The proposed patch check if the version from NVD DB contains a "_",
ie 9.2.0_p1 is convert to 9.2.0p1 before version comparison.
[YOCTO #14127]
Reviewed-by: Yoann CONGAL
Signed-off-by: Geoffrey GIRY
From: Geoffrey GIRY
Multiple CVE are patched in kernel but appears as active because the NVD
database is not up to date
In common file cve-extra-exclusion.inc, CVE are ignored if and only if
all versions of kernel used by langdale are patched
Also ignore CVEs with wrong CPE (applied to kernel
From: Siddharth Doshi
Upstream-Status:
- CVE-2023-0464: Backport from
[https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=959c59c7a0164117e7f8366466a32bb1f8d77ff1]
- CVE-2023-0465: Backport from
Please review this set of patches for langdale and have comments back by
end of day Monday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/5122
With the exception of a known intermittent autobuilder issue on
oe-selftest-armhost:
From: Narpat Mali
Python Packaging Authority (PyPA) setuptools before 65.5.1 allows remote
attackers
to cause a denial of service via HTML in a crafted package or custom
PackageIndex
page. There is a Regular Expression Denial of Service (ReDoS) in
package_index.py.
CVE: CVE-2022-40897
On Thu, Mar 30, 2023 at 10:07 PM Frédéric Martinsons <
frederic.martins...@gmail.com> wrote:
> By the way, about this "chickens and eggs" problem, isn't it the same for
> a regular recipe you just upgraded?
>
I don't know, I haven't upgraded a recipe with crates yet :)
It's just this time I was
Oh my word... I wonder if we need to introspect what cargo does (a la
cargo bitbake) to get this kind of thing right?
On Thu, Mar 30, 2023 at 8:23 PM Martin Jansa wrote:
>
> I don't remember the exact details now, but when I was working on updating
> solana recipes to use this
>
echo > recipes-upstreamable/sugar/sugar-crates.inc
before running "bitbake -c update_crates"
seems like easiest solution to let it regenerate the .inc file (or remove
"require" and then add it back after refresh).
But there is still something strange in this solana, after refreshing the
.inc
By the way, about this "chickens and eggs" problem, isn't it the same for a
regular recipe you just upgraded?
Personnaly, when I update a recipe, I let bitbake tell me what is the new
checksum expected and put it the recipe (as the error message says).
But I'm aware this is not exactly the same,
The patch for CVE-2021-3929 applied on dunfell returns a value for a
void function. This results in the following compiler warning/error:
hw/block/nvme.c:77:6: error: void function
'nvme_addr_read' should not return a value [-Wreturn-type]
return NVME_DATA_TRAS_ERROR;
^
Well I see what you mean, I'll take a look at your example to try to find
out if multiple Cargo.lock could be expected.
And for your second remark, yes, there is a chicken and eggs issue for
updating crates checksum from scratch.
You didn't miss anything, I came across this when updating crates
I don't remember the exact details now, but when I was working on updating
solana recipes to use this
https://github.com/webosose/meta-webosose/commit/9bdfae7988077d021179cc339d0770cd86b4
the S was pointing to just some subdirectory and multiple Cargo.locks files
were parsed in other
Nevermind, I'll submit a new v6 series tomorrow.
Your comment is totally accurate and follow the PEP20 which I should follow
too ("readability counts" and "explicit is better than implicit" at most )
Le jeu. 30 mars 2023, 19:10, Frederic Martinsons via lists.openembedded.org
a écrit :
> Pretty
This recipe uses the cmake class, so there's no need to set the Ninja
backend, or tell it where Python is, or that we're cross-compiling.
Signed-off-by: Ross Burton
---
meta/recipes-devtools/llvm/llvm_git.bb | 3 +--
meta/recipes-devtools/rust/rust-llvm_1.67.1.bb | 2 --
2 files
The cmake bbclass already sets the path to the correct Python for us,
and there appears to be no more scripts in the build which use 'python'
explicitly.
Signed-off-by: Ross Burton
---
meta/recipes-sato/webkit/webkitgtk_2.38.5.bb | 9 -
1 file changed, 9 deletions(-)
diff --git
LIB_INSTALL_DIR was removed in libgit2 1.0 when they moved to using
GNUInstallDirs.
BUILD_CLAR is now BUILD_TESTS as of libgit2 1.4.
Signed-off-by: Ross Burton
---
meta/recipes-support/libgit2/libgit2_1.6.3.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Signed-off-by: Ross Burton
---
meta/lib/oeqa/runtime/cases/apt.py | 4 ++--
meta/lib/oeqa/runtime/cases/buildcpio.py | 7 +--
meta/lib/oeqa/runtime/cases/systemd.py | 2 +-
3 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/meta/lib/oeqa/runtime/cases/apt.py
Pretty much indeed, except for the exception catching part (which allows a
better error message)
Do I need to submit another whole series (PATCH V6) or can I submit just
this change ?
On Thu, 30 Mar 2023 at 18:34, Alex Kiernan wrote:
> On Thu, Mar 30, 2023 at 4:45 PM wrote:
> >
> > From:
On Thu, 2023-03-30 at 16:10 +0200, Alexander Kanavin wrote:
> On Thu, 30 Mar 2023 at 16:08, Zoltan Boszormenyi wrote:
> > Please see the MR:
> > https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/431
> >
> > udev (provided by systemd) -> libgudev -> libfprint
> > also:
> >
On Thu, Mar 30, 2023 at 4:45 PM wrote:
>
> From: Frederic Martinsons
>
> There is no need to do such things, Cargo.lock file
> has to be at the root of CARGO_LOCK_SRC_DIR.
> This avoid finding other possible Cargo.lock that
> would be in subdir (for example if a patch is applied
> on the recipe,
From: Frederic Martinsons
There is no need to do such things, Cargo.lock file
has to be at the root of CARGO_LOCK_SRC_DIR.
This avoid finding other possible Cargo.lock that
would be in subdir (for example if a patch is applied
on the recipe, we can have .pc subdir in S and a Cargo.lock
can be
From: Frederic Martinsons
This recipe is for showing a "real world" example of
a crate that depends on some git repositories.
Usually, this kind of crate is built within a global
workspace (here it is the zbus project) and so
doesn't need a Cargo.lock on its own.
For the sake of the
From: Frederic Martinsons
This is for a specific case where:
- A recipe use a subpath on a git repo (e.g.
git://repo.git/projects;subpath=subproject)
- The recipe contains a patch to apply
- a devtool modify is used on this recipe
With these conditions, the patch cannot be applied at
From: Frederic Martinsons
Without that, the possible git urls that are in SRC_URI of a recipe
are removed from SRC_URI during devtool process and so the
cargo_common_do_patch_paths in cargo_common.bbclass cannot
patch these packages to fetch them locally.
I use a generic type name because I
From: Frederic Martinsons
To handle url like git://git@repo/project
Signed-off-by: Frederic Martinsons
---
meta/classes-recipe/cargo_common.bbclass | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/classes-recipe/cargo_common.bbclass
From: Frederic Martinsons
This series brings the support of local git repository inside
a cargo based recipe.
It also enables devtool capacity to such a recipe along with
an example of recipe and a new selftest case.
The following changes since commit c3fe173d5196506d89aa464ba56aabcf581a60db:
From: Alex Kiernan
Since disable network was added cargo configurations which reference git
repos fail as they attempt to fetch across the network as part of
do_compile, even if EXTRA_OECARGO_PATHS to add them as part of `paths`
is used, as this is documented as only working for packages which
From: Tobias Hagelborn
Move the signature file into place only after it is successfully signed.
This to avoid race and corrupted .sig files in cases multiple onging
builds write to a shared sstate-cache dir.
Signed-off-by: Tobias Hagelborn
Signed-off-by: Peter Kjellerstedt
---
PATCHv2: Use
From: Siddharth Doshi
Upstream-Status:
- CVE-2023-0464: Backport from
[https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=879f7080d7e141f415c79eaa3a8ac4a3dad0348b]
- CVE-2023-0465: Backport from
On Thu, 30 Mar 2023 at 16:51, Böszörményi Zoltán wrote:
> >>> TODO? The new natively built systemctl binary may replace
> >>> the script in systemd-systemctl-native, as it supports
> >>> more options and works better than the script. For example,
> >>> the current script does not create the
2023. 03. 30. 16:41 keltezéssel, Alexander Kanavin írta:
On Thu, 30 Mar 2023 at 16:31, Böszörményi Zoltán wrote:
The mariadb change to use CROSSCOMPILING_EMULATOR
instead of building mariadb-native was reverted because
qemu is not ominpotent. The same applies to meson
running executables via
2023. 03. 30. 16:31 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org
írta:
2023. 03. 30. 16:10 keltezéssel, Alexander Kanavin írta:
On Thu, 30 Mar 2023 at 16:08, Zoltan Boszormenyi wrote:
Please see the MR:
https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/431
On Thu, 30 Mar 2023 at 16:31, Böszörményi Zoltán wrote:
> The mariadb change to use CROSSCOMPILING_EMULATOR
> instead of building mariadb-native was reverted because
> qemu is not ominpotent. The same applies to meson
> running executables via qemu. No custom wrapper would help.
Mariadb's
2023. 03. 30. 16:10 keltezéssel, Alexander Kanavin írta:
On Thu, 30 Mar 2023 at 16:08, Zoltan Boszormenyi wrote:
Please see the MR:
https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/431
udev (provided by systemd) -> libgudev -> libfprint
also:
udev-native -> libgudev-native
On Thu, 30 Mar 2023 at 16:08, Zoltan Boszormenyi wrote:
> Please see the MR:
> https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/431
>
> udev (provided by systemd) -> libgudev -> libfprint
> also:
> udev-native -> libgudev-native -> libfprint-native -> libfprint
>
> Also, please
2023. 03. 30. 15:50 keltezéssel, Richard Purdie írta:
On Thu, 2023-03-30 at 15:42 +0200, Zoltan Boszormenyi wrote:
systemd-native is a dependency for libgudev-native, which
in turn is a dependency for libfprint-native, which is needed
to build libfprint.
The native systemctl binary is removed
2023. 03. 30. 15:46 keltezéssel, Alexander Kanavin írta:
Can you please point to what piece of libgudev actually requires systemd?
It's this line:
DEPENDS = "glib-2.0 udev"
udev is in systemd:
PROVIDES = "udev"
Alex
On Thu, 30 Mar 2023 at 15:42, Zoltan Boszormenyi wrote:
2023. 03. 30. 15:47 keltezéssel, Alexander Kanavin írta:
Can you look into specific details of why libgudev is needed, and
whether it can be made optional? Also, what is it from
libfprint-native that libfprint needs?
I would really like to know these details before we conclude that
adding
On Thu, 2023-03-30 at 15:42 +0200, Zoltan Boszormenyi wrote:
> systemd-native is a dependency for libgudev-native, which
> in turn is a dependency for libfprint-native, which is needed
> to build libfprint.
>
> The native systemctl binary is removed so it doesn't conflict
> with the script from
Can you look into specific details of why libgudev is needed, and
whether it can be made optional? Also, what is it from
libfprint-native that libfprint needs?
I would really like to know these details before we conclude that
adding native variants for tricky, brittle items like all of systemd
is
Can you please point to what piece of libgudev actually requires systemd?
Alex
On Thu, 30 Mar 2023 at 15:42, Zoltan Boszormenyi wrote:
>
> systemd-native is a dependency for libgudev-native, which
> in turn is a dependency for libfprint-native, which is needed
> to build libfprint.
>
> The
systemd-native is a dependency for libgudev-native, which
in turn is a dependency for libfprint-native, which is needed
to build libfprint.
The native systemctl binary is removed so it doesn't conflict
with the script from systemd-systemctl-native.
TODO? The new natively built systemctl binary
libgudev-native is a dependency of libfprint-native, which
is needed to build libfprint.
Signed-off-by: Zoltán Böszörményi
---
meta/recipes-gnome/libgudev/libgudev_237.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-gnome/libgudev/libgudev_237.bb
Drop a backport patch as it is now integrated.
Signed-off-by: Ross Burton
---
meta/recipes-extended/timezone/timezone.inc | 6 +-
.../timezone/tzcode-native.bb | 2 -
...0001-Fix-C23-related-conformance-bug.patch | 301 --
3 files changed, 3 insertions(+),
On 30/03/2023 10:10:21+0100, Richard Purdie wrote:
> On Wed, 2023-03-29 at 23:33 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Thu, 2023-03-23 at 11:08 +0100, Tobias Hagelborn wrote:
> > > Move the signature file into place only after it is successfully signed.
> > > This to
Ah, when trying to update the checksum, I encounter an issue in
do_update_crates (specific to the zvariant recipe structure), I'll add
another patch for that.
Le jeu. 30 mars 2023, 14:26, Frederic Martinsons via lists.openembedded.org
a écrit :
> Ok, I'll do this rebase in the coming hours.
>
Thanks for the test feedback Richard!
I have not run the oe selftest properly on this one and will look in to the
self-test results.
(We have not used the signed rpm part for instance)
Cheers
Tobias
From: Richard Purdie
Sent: Thursday, March 30, 2023 11:10 AM
Ok, I'll do this rebase in the coming hours.
On Thu, 30 Mar 2023 at 13:35, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Thu, 2023-03-30 at 11:47 +0200, Frederic Martinsons wrote:
> > What version of bitbake you had pulled ?
> > Because "mandatory checksum on crates" is a
On Thu, 2023-03-30 at 11:47 +0200, Frederic Martinsons wrote:
> What version of bitbake you had pulled ?
> Because "mandatory checksum on crates" is a patch I submitted two
> weeks ago
> (https://patchwork.yoctoproject.org/project/bitbake/patch/20230317081
>
This reverts commit 66575e31b76894e217350350307b30d3684ba4fa.
Revert CVE-2021-3507 for qemu as it is not applicable for qemu6.2
Link: https://nvd.nist.gov/vuln/detail/CVE-2021-3507
Conflicts:
meta/recipes-devtools/qemu/qemu.inc
Signed-off-by: pawan
---
On Thu, 30 Mar 2023 at 00:34, Khem Raj wrote:
> +From: Khem Raj
> +Date: Wed, 29 Mar 2023 15:31:20 -0700
> +Subject: [PATCH] Ensure 64bit off_t is used
> +
> +This ensures that consistent off_t is used across python modules and
> +main gpgme
> +
> +Fixes
> +| swig -python -threads -py3
On Wed, 29 Mar 2023 at 21:11, Khem Raj wrote:
> > I did - upstream suggested a workaround that was submitted here (in an
> > already closed merge request), but they didn't definitively say
> > whether they would reject a ticket (or a patch) to solve the problem
> > properly, so I think it's worth
On 30/03/2023 11:03:25+0200, Alexandre Belloni wrote:
> Hello,
>
> Because I4m carrying your other series, this fails with:
>
> ERROR: zvariant-3.12.0-r0 do_fetch: No checksum specified for
> '/srv/autobuilder/autobuilder.yocto.io/current_sources/anes-0.1.6.crate',
> please add at least one to
On Thu, 2023-03-30 at 10:10 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Wed, 2023-03-29 at 23:33 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Thu, 2023-03-23 at 11:08 +0100, Tobias Hagelborn wrote:
> > > Move the signature file into place only after it is
On Wed, 2023-03-29 at 23:33 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Thu, 2023-03-23 at 11:08 +0100, Tobias Hagelborn wrote:
> > Move the signature file into place only after it is successfully signed.
> > This to avoid race and corrupted .sig files in cases multiple onging
> >
Hello,
Because I4m carrying your other series, this fails with:
ERROR: zvariant-3.12.0-r0 do_fetch: No checksum specified for
'/srv/autobuilder/autobuilder.yocto.io/current_sources/anes-0.1.6.crate',
please add at least one to the recipe:
SRC_URI[anes.sha256sum] =
Hi Nikhil,
On 29.03.23 at 08:47, nikhil wrote:
Currently busybox utilty "ls" fails to display filenames contains
UTF-8 characters and replaces with "?".
Steps to reproduce:
bin/busybox touch utf_test-Ü
bin/busybox ls utf_test-* > sample.log
bin/busybox cat sample.log
utf_test-??
bin/busybox
Hi,
Please ignore this.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#179305):
https://lists.openembedded.org/g/openembedded-core/message/179305
Mute This Topic: https://lists.openembedded.org/mt/97945083/21656
Group Owner:
From: Khem Raj
This helps in building rsync without autoconf patch, since it will be a
while that the round trip is made, better to apply this patch here until
next release of autoconf.
(From OE-Core rev: 11522b98697befcf13076a90cec4f8ade1fa0645)
Signed-off-by: Khem Raj
Signed-off-by:
From: Khem Raj
(From OE-Core rev: c53d465865d4a9c109322074c2653a3a8b665238)
Signed-off-by: Khem Raj
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 51d8e0e20e2965517a64e954d51a23be52e5f4f3)
Signed-off-by: pawan
---
From: Khem Raj
This helps in building rsync without autoconf patch, since it will be a
while that the round trip is made, better to apply this patch here until
next release of autoconf.
(From OE-Core rev: 11522b98697befcf13076a90cec4f8ade1fa0645)
Signed-off-by: Khem Raj
Signed-off-by:
96 matches
Mail list logo
