Will have change for placing /usr/share/glvnd/egl_vendor.d/50_mesa.json into
FILES:libegl-mesa next patch.
To answer first question. I'd say yes, there may be multiple recipes that
contain an implementation of libGLX_VENDOR library
(libGLX_mesa.so, libGLX_nvidia.so, etc...). Although mesa recipe
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.21.rc1.
We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw
Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. NUC 7
3. ADL
4.
For now, there's no easy way to skip some specified tests when
using 'oe-selftest -r'. This is because '-R' and '-r' are in the
mutually exclusive group. Looking at the codes, the codes have already
allowed running specified tests and skipping specified tests at
the same time. So move '-R' out of t
This is the first release in 13 years;
I have reviewed the accumulated patches, and dropped some of them
where purpose or issue being fixed is not clear. Specifically:
0001-Add-listen-action-for-a-tcp-socket.patch
0001-daemon.c-Libtirpc-porting-fixes.patch
fixed upstream in
https://github.com/unfs
License-Update: upstream has clarified that
the combined work is gpl3 due to use of gnulib.
man-db's own pieces remain (l)gpl2 or later.
https://salsa.debian.org/debian/man-db/-/commit/695a3560fdf91f829f21f00a502244b0cf28e29d
https://salsa.debian.org/debian/man-db/-/blob/upstream/README.md#copyrig
It has been fixed by removing the check upstream see
https://github.com/WayneD/rsync/commit/9a3449a3980421f84ac55498ba565bc112b20d6c
Signed-off-by: Khem Raj
---
...antic-errors-at-the-end-of-configure.patch | 44 ---
meta/recipes-devtools/rsync/rsync_3.2.7.bb| 1 -
2 files c
I think the more accurate description is not that the patch has been
applied, but rather that upstream applied a different patch that makes
this one unnecessary.
Alex
On Wed, 23 Nov 2022 at 20:42, Khem Raj wrote:
>
> It has been applied upstream see
> https://github.com/WayneD/rsync/commit/9a344
Ya, it's very possible. It's been a while since I tried the validation
tool, but it used to complain about all our external document references
and "reversed" relationships (even though the spec allows it). Because of
that, it's possible there are other problems, since validation was failing
in tho
> On 23 Nov 2022, at 16:34, Khem Raj via lists.openembedded.org
> wrote:
>
> If
>> /usr/bin/python is available by default, as it is already on Fedora,
>
> There perhaps is a reason for that in Fedora, but it is in conflict
> with what PEP0384 is saying
It’s not in conflict: the PEP codifies
It has been applied upstream see
https://github.com/WayneD/rsync/commit/9a3449a3980421f84ac55498ba565bc112b20d6c
Signed-off-by: Khem Raj
---
...antic-errors-at-the-end-of-configure.patch | 44 ---
meta/recipes-devtools/rsync/rsync_3.2.7.bb| 1 -
2 files changed, 45 deletions
On Wed, Nov 23, 2022 at 2:55 AM Alexander Kanavin
wrote:
>
> On Wed, 23 Nov 2022 at 10:59, Ross Burton wrote:
> > > The serious need is that we need to patch all the scripts that ask for
> > > python to add a 3 to it. And there will be more of these going forward,
> > > not less. I’d rather jus
Hi Joshua
I used the create-spdx class a few weeks ago to generate an
IMAGE-MACHINE.spdx.json file in tmp/deploy/images/MACHINE/
I tried to validate this SPDX file using the online tool on
https://tools.spdx.org/app/validate/, but I get this warning (or error?):
The following warning(s) wer
The commit message also needs to be rewritten to follow the
common praxis for the repositories.
//Peter
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Steve Sakoman
> Sent: den 23 november 2022 16:44
> To: Manoj Saun
> Cc
This is the wrong mailing list for your patch since it is for
meta-openembedded, not oe-core. You should send it to:
openembedded-de...@lists.openembedded.org
Steve
On Wed, Nov 23, 2022 at 5:23 AM Manoj Saun
wrote:
>
> -> nginx: fix CVE-2022-41741
>
> -> nginx: disabled duplicate atoms.
>
> ->
-> nginx: fix CVE-2022-41741
-> nginx: disabled duplicate atoms.
-> Reference:
-> https://nvd.nist.gov/vuln/detail/CVE-2022-41742
-> Upstream fixes:
->
https://github.com/nginx/nginx/commit/0d23105373e6d8a720b9826079c077b9b4be919d
-> (LOCAL REV: NOT UPSTREAM) -- Not applicable, upstream out of
A vulnerability classified as problematic was found in ffmpeg. This
vulnerability affects the function
smc_encode_stream of the file libavcodec/smcenc.c of the component QuickTime
Graphics Video Encoder. The
manipulation of the argument y_size leads to out-of-bounds read. The attack can
be initi
A vulnerability classified as problematic has been found in ffmpeg. This
affects an unknown part of the file
libavcodec/rpzaenc.c of the component QuickTime RPZA Video Encoder. The
manipulation of the argument y_size
leads to out-of-bounds read. It is possible to initiate the attack remotely.
Th
A vulnerability classified as problematic was found in ffmpeg. This
vulnerability affects the function
smc_encode_stream of the file libavcodec/smcenc.c of the component QuickTime
Graphics Video Encoder. The
manipulation of the argument y_size leads to out-of-bounds read. The attack can
be initi
The following changes since commit 9237ffc4feee2dd6ff5bdd672072509ef9e82f6d:
build-appliance-image: Update to langdale head revision (2022-11-14 16:30:13
+)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/langdale-next
http://cgit
A vulnerability classified as problematic has been found in ffmpeg. This
affects an unknown part of the file
libavcodec/rpzaenc.c of the component QuickTime RPZA Video Encoder. The
manipulation of the argument y_size
leads to out-of-bounds read. It is possible to initiate the attack remotely.
Th
The following changes since commit 3243b069db7629d15e4b8c25b4133f824d18520c:
qemu: add io_uring PACKAGECONFIG (2022-11-10 07:13:46 -1000)
are available in the Git repository at:
https://git.openembedded.org/openembedded-core-contrib stable/kirkstone-next
http://cgit.openembedded.org/opene
> +PREFERRED_PROVIDER_virtual/libglx ?= "mesa"
Is there a real need for another preferred provider here?
> + if ${@bb.utils.contains('PACKAGECONFIG', 'egl', 'true', 'false', d)} && [
> -f ${D}${includedir}/EGL/eglplatform.h ]; then
Might as well just do the test, and not bother looking at PACK
On Wed, 23 Nov 2022 at 10:59, Ross Burton wrote:
> > The serious need is that we need to patch all the scripts that ask for
> > python to add a 3 to it. And there will be more of these going forward, not
> > less. I’d rather just always have python available. Not a problem worth
> > deliberatin
On 22 Nov 2022, at 18:32, Alexander Kanavin via lists.openembedded.org
wrote:
> While this might be 'too soon' to conclude that python2 is truly dead,
> maybe a year (or two, or three) from now it won't be. Fedora has
> already made the switch, Debian will follow, and honestly, I just
> can't mus
On 22 Nov 2022, at 18:03, Alexander Kanavin wrote:
>
> The serious need is that we need to patch all the scripts that ask for python
> to add a 3 to it. And there will be more of these going forward, not less.
> I’d rather just always have python available. Not a problem worth
> deliberating o
25 matches
Mail list logo
