From: Vijay Anusuri
Upstream-Status: Backport
[https://github.com/golang/go/commit/9baafabac9a84813a336f068862207d2bb06d255
&
https://github.com/golang/go/commit/c9d5f60eaa4450ccf1ce878d55b4c6a12843f2f3
&
https://github.com/golang/go/commit/8f676144ad7b7c91adb0c6e1ec89aaa6283c6807
&
On Fri, Jan 5, 2024 at 7:02 AM Steve Sakoman via
lists.openembedded.org
wrote:
>
> On Fri, Jan 5, 2024 at 6:54 AM Martin Jansa wrote:
> >
> > On Fri, Jan 5, 2024 at 5:06 PM Martin Jansa via lists.openembedded.org
> > wrote:
> >>
> >> FWIW: I see the processes running after bitbake exit only in
Ignore this one, since it has already been addressed by:
https://patchwork.yoctoproject.org/project/oe-core/patch/1704271378-18012-1-git-send-email-wan...@fujitsu.com/
But please take 2/2 for ptest.
On Fri, Jan 5, 2024 at 10:17 AM Tim Orling via lists.openembedded.org
wrote:
>
The conftest.py file is needed to define the "slots" and "frozen" fixtures
for pytest
Signed-off-by: Tim Orling
---
All ptests passed on core-image-ptest-python3-attrs in about 19 seconds
on qemux86-64
.../conf/distro/include/ptest-packagelists.inc | 1 +
.../python/python3-attrs/run-ptest
https://www.attrs.org/en/stable/changelog.html
23.2.0 - 2023-12-31
Changes
* The type annotation for attrs.resolve_types() is now correct. #1141
* Type stubs now use typing.dataclass_transform to decorate dataclass-like
decorators, instead of the non-standard __dataclass_transform__ special
On Fri, Jan 5, 2024 at 8:16 AM Alexandre Belloni
wrote:
>
> I believe this caused:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4191/steps/12/logs/stdio
>
Likely, so because this patch
* Refresh -crates.inc
https://github.com/pyca/bcrypt/compare/4.1.1...4.1.2
https://github.com/pyca/bcrypt/?tab=readme-ov-file#changelog
https://github.com/pyca/bcrypt/?tab=readme-ov-file#412
* Publish both py37 and py39 wheels. This should resolve some errors
relating to initializing a module
On Fri, Jan 5, 2024, 9:54 AM Martin Jansa wrote:
> On Fri, Jan 5, 2024 at 5:06 PM Martin Jansa via lists.openembedded.org
> wrote:
>
>> FWIW: I see the processes running after bitbake exit only in kirkstone
>> and only with
>> PRSERV_HOST = "localhost:0"
>> if I drop PRSERV_HOST then all 3
On Fri, Jan 5, 2024 at 6:54 AM Martin Jansa wrote:
>
> On Fri, Jan 5, 2024 at 5:06 PM Martin Jansa via lists.openembedded.org
> wrote:
>>
>> FWIW: I see the processes running after bitbake exit only in kirkstone and
>> only with
>> PRSERV_HOST = "localhost:0"
>> if I drop PRSERV_HOST then all
* Relocate Upstream-Status in
0001-regress-banner.sh-log-input-and-output-files-on-erro.patch
so it will not throw an error in AUH
https://www.openssh.com/txt/release-9.6
https://github.com/openssh/openssh-portable/compare/V_9_5_P1...V_9_6_P1
https://nvd.nist.gov/vuln/detail/CVE-2023-48795
On Fri, Jan 5, 2024 at 5:06 PM Martin Jansa via lists.openembedded.org
wrote:
> FWIW: I see the processes running after bitbake exit only in kirkstone and
> only with
> PRSERV_HOST = "localhost:0"
> if I drop PRSERV_HOST then all 3 bitbake-server processes exist together
> with bitbake itself.
>
I believe this caused:
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/4191/steps/12/logs/stdio
On 03/01/2024 18:10:51-0800, Khem Raj wrote:
> This reverts commit a856192be5dd78c621478ed29871191c580686c4.
>
> It causes a regression in creating different GIDs in image and ipk
FWIW: I see the processes running after bitbake exit only in kirkstone and
only with
PRSERV_HOST = "localhost:0"
if I drop PRSERV_HOST then all 3 bitbake-server processes exist together
with bitbake itself.
luneos-kirkstone $ rm -f bitbake-cookerdaemon.log
luneos-kirkstone $ ps aux | grep
Hello,
This fails with:
https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/7361/steps/12/logs/warnings
WARNING: core-image-full-cmdline-1.0-r0 do_rootfs: User root has been defined
as (root, 0, 0, root, /root, /bin/sh) but sysusers.d expects it as (root, 0, 0,
Super User,
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/dunfell-4-5-cve-update-nvd2-native-increase-the-delay-between-subsequent-request-failures.patch
FAIL: test
From: Dmitry Baryshkov
License-Update: additional firmwares
Signed-off-by: Dmitry Baryshkov
Signed-off-by: Alexandre Belloni
(cherry picked from commit 7c725d1f2ed9a271d39d899ac2534558c2d103fc)
Signed-off-by: Steve Sakoman
---
...{linux-firmware_20230804.bb => linux-firmware_20231030.bb} |
From: Dhairya Nagodra
Sometimes NVD servers are unstable and return too many errors.
There is an option to have higher fetch attempts to increase the chances
of successfully fetching the CVE data.
Additionally, it also makes sense to progressively increase the delay
after a failed request to an
From: Dhairya Nagodra
As per NVD, the public rate limit is 5 requests in 30s (6s delay).
Using an API key increases the limit to 50 requests in 30s (0.6s delay).
However, NVD still recommends sleeping for several seconds so that the
other legitimate requests are serviced without denial or
From: Peter Marko
Sometimes NVD servers are unstable and return too many errors.
Last time we increased number of attempts from 3 to 5, but
further increasing is not reasonable as in normal case
too many retries is just abusive.
Keep retries low as default and allow to increase as needed.
From: Peter Marko
This variable is not referenced in oe-core anymore.
Signed-off-by: Peter Marko
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 905b45a814cb33327503b793741c19b44c8550b3)
Signed-off-by: Steve Sakoman
---
Please review this set of changes for dunfell and have comments back by
end of day Tuesday, January 9
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6418
The following changes since commit 3ea36d92800b139eaaf75995cdd59912b63db9ee:
tzdata:
V2 also has issues, as flagged by patchtest and my local testing:
Applying: go: Backport fix for CVE-2023-45287
error: corrupt patch at line 2273
error: could not build fake ancestor
Patch failed at 0001 go: Backport fix for CVE-2023-45287
Steve
On Thu, Jan 4, 2024 at 9:33 PM Vijay Anusuri via
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/3-3-python3-cython-update-0.29.36---3.0.7.patch
FAIL: test lic files chksum modified not mentioned:
pep517 build backends require cython 3.x when
python is at 3.12, so we can't hold this update any
longer. There are only a few things in meta-oe
and meta that break anymore, and fixes for them
are provided at the same time as this patch.
License-update: http -> https
Signed-off-by: Alexander
This has been rejected by upstream in favour of requiring obsolete cython
until there's 'proper' 3.x support. Months later, there's still no progress
so let's just take the rejected fix, as it does work (as reported by others as
well),
and allows moving forward with cython.
Signed-off-by:
python 3.12 points out that:
SyntaxWarning: invalid escape sequence '\*'
Signed-off-by: Alexander Kanavin
---
scripts/lib/devtool/standard.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index
On Fri, 2024-01-05 at 12:42 +0100, Alexander Kanavin wrote:
> On Fri, 5 Jan 2024 at 12:22, Richard Purdie
> wrote:
>
> > I've a few ideas on how we might be able to detect potential problems,
> > I'll continue to try and work something out but I want to make it clear
> > there are some things it
Since we're changing the return values of the function, add a version so
bitbake can ensure it is using a compatible function.
Signed-off-by: Richard Purdie
---
meta/lib/oe/sstatesig.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/lib/oe/sstatesig.py b/meta/lib/oe/sstatesig.py
index
On Fri, 5 Jan 2024 at 12:22, Richard Purdie
wrote:
> I've a few ideas on how we might be able to detect potential problems,
> I'll continue to try and work something out but I want to make it clear
> there are some things it is hard to change :/.
There's the option of adding another function
On Mon, 2023-12-18 at 09:43 +0100, Alexander Kanavin wrote:
> find_siginfo() returns two different data structures depending
> on whether its third argument (list of hashes to find) is empty or
> not:
> - a dict of timestamps keyed by path
> - a dict of paths keyed by hash
>
> This is not a good
On Fri, 5 Jan 2024 at 12:14, Jermain Horsman wrote:
> This leave the question of what to do if only the '--reference' option is
> used?
> Do nothing or update/use a custom revision for all repos?
Updating all repos to the same reference is unlikely to work well with
real world combinations of
> On further thought, if done this way, then --update could instead
> serve to update file that already exists, whereas the default would be
I would prefer this, as I might have a config with repo A and B for which
I have changed both locally, but I'd only want to apply the changes to B
to the
Right, I guess the code can be tweaked to not return entries where
mtime could not be determined, but I'd like to observe the actual
failure in the wild first, for the sake of a better commit message.
Alex
On Fri, 5 Jan 2024 at 11:46, Richard Purdie
wrote:
>
> On Tue, 2024-01-02 at 15:50 +0100,
On Tue, 2024-01-02 at 15:50 +0100, Alexander Kanavin wrote:
> Suppressing the error and returning None can result in a delayed failure:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/6254/steps/14/logs/stdio
>
Hi, Richard
I had send a similar patch before, subjected as "bitbake.conf: support
persistent /var/tmp",
and you have replied me with some concerns on 2021/9/13. But I noticed
that another variable VOLATILE_TMP_DIR is added in 2023.
but as I tested, it not works, so I make this patch to
35 matches
Mail list logo
