On 07.05.21 08:02, Mikko Rapeli wrote:
Hi,
On Thu, May 06, 2021 at 07:12:32AM -1000, Steve Sakoman wrote:
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from check
On Fri, 2021-05-07 at 06:02 +, Mikko Rapeli wrote:
> Hi,
>
> On Thu, May 06, 2021 at 07:12:32AM -1000, Steve Sakoman wrote:
> > The preferred methods for CVE resolution are:
> >
> > 1. Version upgrades where possible
> > 2. Patches where not possible
> > 3. Database updates where version info
Make sure help2man output is reproducible. Fixes:
| .\"·DO·NOT·MODIFY·THIS·FILE!··It·was·generated·by·help2man·1.022.
.\"·DO·NOT·MODIFY·THIS·FILE!··It·was·generated·by·help2man·1.022.
| .TH·FSG·"1"·"April·2021"·"FSG·lsb_release·v1.4"·FSG
.TH·FSG·"1"·"May·2021"·"FSG·lsb_release·v1.4"·FSG
|
Hi,
On Thu, May 06, 2021 at 07:12:32AM -1000, Steve Sakoman wrote:
> The preferred methods for CVE resolution are:
>
> 1. Version upgrades where possible
> 2. Patches where not possible
> 3. Database updates where version info is incorrect
> 4. Exclusion from checking where it is determined that
On Thu, 2021-05-06 at 17:55 +0530, Vinay Kumar wrote:
> Hi Anuj,
>
> Thanks for the feedback.
>
> > > This doesn't look like a cherry pick of:
> > > https://github.com/bminor/binutils-gdb/commit/d3edaa91d4cf7202ec14342410194841e2f67f12
> > > What else is in there?
>
> cherry picked commit ids i
On Thu, May 6, 2021 at 11:49 AM Alexander Kanavin
wrote:
>
> No package 'gdk-pixbuf-xlib-2.0' found
>
> gdk-pixbuf has fully removed support for this:
> https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/38
>
in this pull they talk about soft API break, have we understood the
breadth of i
No package 'gdk-pixbuf-xlib-2.0' found
gdk-pixbuf has fully removed support for this:
https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/38
Alex
On Thu, 6 May 2021 at 16:56, Khem Raj wrote:
> seeing failures on meta-oe builds
>
> https://errors.yoctoproject.org/Errors/Details/580243/
Hi Richard,
>> The patch was tested and then merged but we can update the patch header with
>> more info if we have it.
Thanks for clarification.
Updated the patch header with additional info,
===
This patch is cherry picked from commit
95b91a043aeaeb546d2fea556d84a2de1e91
Source: git://sourceware.org/git/binutils-gdb.git
Tracking -- https://sourceware.org/bugzilla/show_bug.cgi?id=26945
Backported upstream commit d3edaa91d4cf7202ec14342410194841e2f67f12 to
binutils-2.36 source along with commit id dependencies
(8e03235147a9e774d3ba084e93c2da1aa94d1cec and
8b69e61d4
The preferred methods for CVE resolution are:
1. Version upgrades where possible
2. Patches where not possible
3. Database updates where version info is incorrect
4. Exclusion from checking where it is determined that the CVE
does not apply to our environment
In some cases none of these method
This ptest package was accidentally not enabled. The tests run quickly (2s) and
pass so add to the standard test suite.
Signed-off-by: Richard Purdie
---
meta/conf/distro/include/ptest-packagelists.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/conf/distro/include/ptest-packagelist
From: Bruce Ashfield
Dynamic layers may have a conf directory, but don't need (or
want) a conf/layer.conf
This isn't an error, so we can just log it and indicate the
layer is being skipped.
A full layer without a conf file isn't all that useable, so we
aren't letting anything subtle slip throug
This information is useful, but should not be a warning level.
[YOCTO #14382]
Signed-off-by: Saul Wold
---
meta/lib/oeqa/utils/qemurunner.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/utils/qemurunner.py
b/meta/lib/oeqa/utils/qemurunner.py
index 3d3213d3d
This information is useful, but should not be a warning level.
[YOCTO #14382]
Signed-off-by: Saul Wold
---
meta/lib/oeqa/utils/qemurunner.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/utils/qemurunner.py
b/meta/lib/oeqa/utils/qemurunner.py
index 3d3213d3d
Hello Khem,
Thank you for looking into this issue. Below is the content of pseudo.log file
as asked by you.
debug_logfile: fd 2
pid 453 [parent 452], doing new pid setup and server start
Setup complete, sending SIGUSR1 to pid 452.
db cleanup for server shutdown, 08:07:22.373
memory-to-file backu
seeing failures on meta-oe builds
https://errors.yoctoproject.org/Errors/Details/580243/
On Wed, May 5, 2021 at 8:19 AM Alexander Kanavin wrote:
>
> Note: jpg/png loaders are now builtin and no longer
> provided as separate packages.
>
> Drop backport missing-test-data.patch.
>
> Drop no longer
> -Original Message-
> From: Steve Sakoman
> Sent: 06 May 2021 16:14
> To: Diego Santa Cruz
> Cc: Steve Sakoman ; openembedded-
> c...@lists.openembedded.org; Mark Hatle
>
> Subject: Re: [OE-core] Unihash warning building kernels in Yocto 3.1.7
>
> On Tue, May 4, 2021 at 10:17 PM Diego
On Tue, May 4, 2021 at 10:17 PM Diego Santa Cruz via
lists.openembedded.org
wrote:
> Any news on this one? I have been doing our own builds with the equivalent of
> that patch for our BSPs with a linux-intel derived kernel recipe plus another
> internal kernel recipe (both using kernel.bbclass)
On Thu, May 6, 2021 at 3:39 AM Joshua Watt wrote:
>
> Can we backport this to hardknott and dunfell (and gatesgarth if it's
> still active)?
Yes, will backport to dunfell!
Steve
> On 5/5/21 4:40 PM, Joshua Watt wrote:
> > Instead of having find directly invoke touch for each file in the root
>
On Thu, May 06, 2021 at 08:39:27AM -0500, Joshua Watt wrote:
> Can we backport this to hardknott and dunfell (and gatesgarth if it's still
> active)?
Yes indeed, please to dunfell!
-Mikko, who also marked the patch but didn't have time to put it to test on
dunfell..
> On 5/5/21 4:40 PM, Joshua
Can we backport this to hardknott and dunfell (and gatesgarth if it's
still active)?
On 5/5/21 4:40 PM, Joshua Watt wrote:
Instead of having find directly invoke touch for each file in the root
file system, pass a list to xargs for batching. This significantly
reduces the number of times the to
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/5.10:
qemuppc32: reduce serial issues seen on shutdown
Richard reported:
We've been seeing a lot of the qemuppc shutdown issue and I decided to
look into it. The really worrying thing looking at the logs lo
On Thu, 2021-05-06 at 17:55 +0530, Vinay Kumar wrote:
> Hi Anuj,
>
> Thanks for the feedback.
>
> > > This doesn't look like a cherry pick of:
> > > https://github.com/bminor/binutils-gdb/commit/d3edaa91d4cf7202ec14342410194841e2f67f12
> > > What else is in there?
>
> cherry picked commit ids i
Hi Anuj,
Thanks for the feedback.
>> This doesn't look like a cherry pick of:
>> https://github.com/bminor/binutils-gdb/commit/d3edaa91d4cf7202ec14342410194841e2f67f12
>> What else is in there?
cherry picked commit ids in the below order to "SRCREV" of binutils-2.36.inc.
1. 8e03235147a9e774d3b
On Thu, May 6, 2021 at 3:30 AM Richard Purdie
wrote:
>
> On Wed, 2021-05-05 at 13:58 -0400, bruce.ashfi...@gmail.com wrote:
> > From: Bruce Ashfield
> >
> > Integrating the following commit(s) to linux-yocto/5.10:
> >
> > qemuppc32: reduce serial issues seen on shutdown
> >
>
> Thanks for thi
Hi Quentin,
Thanks for the review!
On 5/6/21 11:25 AM, Quentin Schulz wrote:
> Hi Michael,
>
> On Wed, May 05, 2021 at 07:56:15PM +0200, Michael Opdenacker wrote:
>> This expands the error message when a network failure is detected.
>> It happens that some ISPs or networks block the default examp
On Thu, 6 May 2021 at 00:36, Alexander Kanavin via lists.openembedded.org
wrote:
> On Thu, 6 May 2021 at 00:32, Richard Purdie <
> richard.pur...@linuxfoundation.org> wrote:
>
>> Doesn't removing this degrade the accuracy of the ptest reporting?
>>
>
> I'll check the outputs before and after.
>
I'm pleased to be able to announce that the project is planning to have
the April 2022 release next year be our next LTS release.
This fits in with our original announced plan of 2 year cycles and
recognises that the LTS has been well received by members and our
community. It also aligns well wi
Signed-off-by: Anatol Belski
---
.../tar/tar/CVE-2021-20193.patch | 133 ++
meta/recipes-extended/tar/tar_1.32.bb | 1 +
2 files changed, 134 insertions(+)
create mode 100644 meta/recipes-extended/tar/tar/CVE-2021-20193.patch
diff --git a/meta/recipes-exte
Signed-off-by: Anatol Belski
---
.../tar/tar/CVE-2021-20193.patch | 133 ++
meta/recipes-extended/tar/tar_1.32.bb | 1 +
2 files changed, 134 insertions(+)
create mode 100644 meta/recipes-extended/tar/tar/CVE-2021-20193.patch
diff --git a/meta/recipes-exte
Hi Michael,
On Wed, May 05, 2021 at 07:56:15PM +0200, Michael Opdenacker wrote:
> This expands the error message when a network failure is detected.
> It happens that some ISPs or networks block the default example.com
> domain. Therefore, instead of disabling network access, it
> lets the user kn
After the addition of the qmp socket, runqemu started failing:
ERROR - Failed to run qemu: qemu-system-aarch64: -qmp
unix:/home/yocto/actions-runner-meta-openembedded/_work/meta-openembedded/meta-openembedded/yoe/build/tmp/.3eg5fiid,server,wait:
UNIX socket path
'/home/yocto/actions-runner-meta-
Rather than totally disabling the logging, inform it we're about to exit
so we can log messages over the exit cleanly too. This aids debugging. It
also avoids a race where the logging handler could still error whilst
shutting down.
Also remove a race window by notificing the handler of the shutdow
If the scripts/postinst-intercepts is owned by root/root then the copyfile()
calls
will fail due to chown issues. We don't care about ownership of these files so
use shutil.copy() instead which won't perform any chown.
Signed-off-by: Richard Purdie
---
meta/lib/oe/package_manager/__init__.py |
On Wed, 2021-05-05 at 13:58 -0400, bruce.ashfi...@gmail.com wrote:
> From: Bruce Ashfield
>
> Integrating the following commit(s) to linux-yocto/5.10:
>
> qemuppc32: reduce serial issues seen on shutdown
>
Thanks for this, I appreciate being able to test it quickly. We are seeing
a warning
35 matches
Mail list logo
