On Wed, 29 Mar 2023, 12:03 Marta Rybczynska via lists.openembedded.org,
wrote:
> Add new fetcher for the NVD database using the 2.0 API [1].
> The implementation changes as little as possible, keeping the current
> database format (but using a different database file for the transition
>
Yes, testing the build right now, will post the patch.
Thanks,
Gaurav
From: Steve Sakoman
Date: Wednesday, March 29, 2023 at 12:18 PM
To: Gaurav Gupta (gauragup)
Cc: openembedded-core@lists.openembedded.org
, Khem Raj
Subject: Re: [OE-core] Build error with dunfell release "yocto-3.1.24"
On
swig needs this defined as well
Signed-off-by: Khem Raj
---
.../0001-Ensure-64bit-off_t-is-used.patch | 35 +++
meta/recipes-support/gpgme/gpgme_1.18.0.bb| 1 +
2 files changed, 36 insertions(+)
create mode 100644
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
> builds write to a shared sstate-cache dir.
>
> Signed-off-by: Tobias Hagelborn
> ---
>
On Wed, Mar 29, 2023 at 8:03 AM Khem Raj wrote:
>
> On Wed, Mar 29, 2023 at 9:51 AM Gaurav Gupta (gauragup) via
> lists.openembedded.org
> wrote:
> >
> > Hello,
> >
> >
> >
> > On latest “dunfell” branch, there’s a compiler warning/error when building
> > QEMU.
> >
> >
> >
> > The patch for
On 3/29/23 12:04 PM, Alexander Kanavin wrote:
On Wed, 29 Mar 2023 at 17:07, Khem Raj wrote:
32-bit specificity is not in itself inappropriate for upstream
submission, can you please either submit upstream or open a ticket and
refer to it in the patch?
did you read the message trail on the
On Wed, 29 Mar 2023 at 17:07, Khem Raj wrote:
> > 32-bit specificity is not in itself inappropriate for upstream
> > submission, can you please either submit upstream or open a ticket and
> > refer to it in the patch?
>
> did you read the message trail on the gerrit review I added to commit ?
I
On Wed, Mar 29, 2023 at 12:20 AM Richard Purdie
wrote:
>
> On Wed, 2023-03-29 at 12:17 +0530, 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-Ü
> >
On Wed, Mar 29, 2023 at 9:51 AM Gaurav Gupta (gauragup) via
lists.openembedded.org
wrote:
>
> Hello,
>
>
>
> On latest “dunfell” branch, there’s a compiler warning/error when building
> QEMU.
>
>
>
> The patch for CVE-2021-3929 applied on dunfell returns a value for a void
> function:
>
Hello,
On latest “dunfell” branch, there’s a compiler warning/error when building QEMU.
The patch for CVE-2021-3929 applied on dunfell returns a value for a void
function:
https://github.com/openembedded/openembedded-core/blob/dunfell/meta/recipes-devtools/qemu/qemu/CVE-2021-3929.patch#L58
On Wed, 2023-03-22 at 16:54 +0100, dit.koz...@kynetics.com wrote:
> From: Dit Kozmaj
>
> So far part.label has been used to define GPT partition label even if
> part.part_name was defined.
> Fix the code to use part.part_name whenever available, as it makes sense
> to have a GPT partition label
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 fd70a564d6946fa460638dd04ce2daecf4566cf3:
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
On Wed, Mar 29, 2023 at 1:38 AM Alexander Kanavin
wrote:
>
> On Tue, 28 Mar 2023 at 23:43, Khem Raj wrote:
> > +Subject: [PATCH] ANGLE: Remove static_assert for 64bit atomics
> > +
> > +This will make sure that it can be built on 32bit platforms e.g.
> > +mips32/ppc32
> > +
> > +This partially
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
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
Thanks! I've cherry-picked this into langdale and it will appear in
kirkstone shortly too.
Steve
On Wed, Mar 29, 2023 at 3:30 AM Martin Jansa wrote:
>
> * master branch was removed upstream:
> downloads/git2/github.com.intel.bmap-tools $ git remote prune origin
> Pruning origin
> URL:
On Tue, Mar 28, 2023 at 9:38 PM Pawan Badganchi wrote:
>
> Hello steve,
> Could you please build this patch with below patch. This is the latest
> version and please ignore previous sent patches.
>
> https://lists.openembedded.org/g/openembedded-core/message/179015
We have the following patch
Hello Marta,
We only tested core-image-minimal and some recipes that use the update
and release candidate formats (pX and -rcX)
Geoffrey GIRY
SMILE ECS - R Engineer
Le mer. 29 mars 2023 à 06:45, Marta Rybczynska a écrit :
>
> On Tue, Mar 28, 2023 at 12:24 PM Geoffrey GIRY wrote:
>>
>> Fixes
* 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
* downloads/git2/github.com.intel.bmap-tools $ git branch -a
* 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
* downloads/git2/github.com.intel.bmap-tools $ git branch -a
Just run this up locally and rebuilt our world - looks good to me.
On Mon, Mar 27, 2023 at 11:13 PM Alexander Kanavin
wrote:
>
> I think I have meanwhile resolved the 1.68 upgrade issues:
> https://git.yoctoproject.org/poky-contrib/log/?h=akanavin/package-version-updates
>
> So that leaves the
Remove a patch which has been applied upstream and rebase
another patch on top of v2.9.10
Signed-off-by: Sudip Mukherjee
---
...port-dictionary-byte-order-dependent.patch | 28 +-
...aklib-fix-testnum-and-teststr-failed.patch | 53 ---
.../{cracklib_2.9.8.bb =>
Over night I got one failure in kirkstone with new uninative:
Exception: subprocess.CalledProcessError: Command '('patchelf-uninative',
'--set-interpreter',
'TOPDIR/BUILD/sysroots-uninative/x86_64-linux/lib/ld-linux-x86-64.so.2',
On Fri, 2023-03-03 at 10:01 +0100, Louis Rannou wrote:
> The actual serial runner has a different usage compare to the ssh runner. The
> return status is different and failure are not raised as exceptions.
>
> Initially, I wanted to create a new run_serial_socket and modify the old
> run_serial
Add new fetcher for the NVD database using the 2.0 API [1].
The implementation changes as little as possible, keeping the current
database format (but using a different database file for the transition
period), with a notable exception of not using the META table.
Minor changes that could be
It is possible to rename packages with the macro PKG:${PN} and result in
a package name conflict if the target name exists already.
Add a fatal check to prevent this issue to go unnoticed.
Fix [Yocto #12060]
Reviewed-by: Yoann CONGAL
Signed-off-by: Fawzi KHABER
---
This Unittest tries to rename a package, using an already used name and
fails on do_package.
Reviewed-by: Yoann CONGAL
Signed-off-by: Fawzi KHABER
---
.../packagenameconflict/packagenameconflict.bb | 10 ++
meta/lib/oeqa/selftest/cases/package.py| 7 +++
2
When building gobject-introspection for aarch64, the generated giscanner
python module has the wrong "x86_64" suffix:
./usr/lib/gobject-introspection/giscanner/_giscanner.cpython-311-x86_64-linux-gnu.so
The EXT_SUFFIX used by meson to generate the python module is taken
from the native python3
On Tue, 28 Mar 2023 at 23:43, Khem Raj wrote:
> +Subject: [PATCH] ANGLE: Remove static_assert for 64bit atomics
> +
> +This will make sure that it can be built on 32bit platforms e.g.
> +mips32/ppc32
> +
> +This partially reverts
> https://chromium-review.googlesource.com/c/angle/angle/+/4205892
From: Loc Nguyen
Packages that install Python modules shouldn't be installing Eggs,
as distro-managed modules should be "bare"
Added a sanity check to verify if python modules will install Eggs.
If yes, display a warning message to user.
See [YOCTO #5725] for more details
Signed-off-by: Loc
From: Loc Nguyen
I'm a new comer, please help to review and feedback.
We are planning to contribute to yocto prj, beginning with fixing newcomer's
bug at: https://bugzilla.yoctoproject.org/show_bug.cgi?id=5725
The following changes since commit 23212c8c44315ed6612009e0e667d14ad26459b0:
rpm:
Hello steve,
Could you please build this patch with below patch. This is the latest version
and please ignore previous sent patches.
https://lists.openembedded.org/g/openembedded-core/message/179015
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online
On Wed, 2023-03-29 at 12:17 +0530, 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-??
Thanks, after having "fixed" /tmp, I managed to play
test_devtool_modify_git successfully.
Le mar. 28 mars 2023, 22:04, Alexander Kanavin a
écrit :
> Not devtool's fault. The selftest is written so that devtool is
> instructed to use /tmp/... to extract sources, and not a workspace in
> a
39 matches
Mail list logo
