Hi,
On Tue, Feb 27, 2024 at 12:33:15PM +, Richard Purdie wrote:
> On Tue, 2024-02-27 at 14:23 +0200, Mikko Rapeli wrote:
> > On Tue, Feb 27, 2024 at 12:06:41PM +, Richard Purdie wrote:
> > > Should we break it for others so it works for you?
> > >
> > > If I merge this patch and then I ge
On 2/29/24 14:04, Khem Raj wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Wed, Feb 28, 2024 at 9:56 PM Changqing Li
wrote:
On 2/28/24 17:45, Alexander Kanavin wrote
On Wed, Feb 28, 2024 at 9:56 PM Changqing Li
wrote:
>
>
> On 2/28/24 17:45, Alexander Kanavin wrote:
>
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and
> know the content is safe.
>
> On Wed, 28 Feb 2024
On 2/28/24 17:45, Alexander Kanavin wrote:
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know
the content is safe.
On Wed, 28 Feb 2024 at 04:19, Changqing Li wrote:
1.
Currently, There is one line i
This is last milestone before final release
Signed-off-by: Khem Raj
---
meta/recipes-devtools/llvm/llvm_git.bb | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/llvm/llvm_git.bb
b/meta/recipes-devtools/llvm/llvm_git.bb
index 40103a94aea..111fb07fac9 100
From: Changqing Li
patch 0007-exec.go-do-not-write-linker-flags-into-buildids.patch
removes linker flags from buildids for not breaking reproducibility,
but it seems that this will make go not rebuild when linker flag
changes, Refer [1]. So remove this oe-specific patch, and change to
filter out
The llvm github repo appears to see a lot of churn on branches we're not
interested in and is in general huge and unreliable to clone.
Switch to shallow clones to improve the user experience.
Signed-off-by: Richard Purdie
---
meta/classes-global/mirrors.bbclass | 6 +-
1 file changed, 5 ins
On Wed, 2024-02-28 at 15:32 +0800, wangmy via lists.openembedded.org wrote:
> From: Wang Mingyu
>
> License-Update: Copyright year updated to 2024.
>
> Changelog:
>
> * The JIT code no longer supports ARMv5 architecture.
> * A new function pcre2_get_match_data_heapframes_size() for
On Wed, 2024-02-28 at 15:32 +0800, wangmy via lists.openembedded.org wrote:
> From: Wang Mingyu
>
> 0001-fix-minicom-h-v-return-value-is-not-0.patch
> allow.to.disable.lockdev.patch
> removed since they're included in 2.9.
>
> Changelog:
>
> - Change Hardware Flow Control Default t
Go 1.22 Release Notes
https://go.dev/doc/go1.22
Signed-off-by: Jose Quaresma
---
meta/conf/distro/include/tcmode-default.inc | 2 +-
.../go/{go-1.21.7.inc => go-1.22.0.inc} | 2 +-
...e_1.21.7.bb => go-binary-native_1.22.0.bb} | 6 ++--
..._1.21.7.bb => go-cross-canadian_1.22.0.bb} |
some more failures in meta-openembedded layers ( meta-xfce)
https://errors.yoctoproject.org/Errors/Details/754995/
https://errors.yoctoproject.org/Errors/Details/754996/
On Tue, Feb 27, 2024 at 3:39 AM Martin Jansa wrote:
>
> Yes, it was reproducible on my host gentoo after removing distutils
>
Upgrade to latest 1.21.x release [1]:
$ git --no-pager log --oneline go1.21.5..go1.21.7
f29208030a (tag: go1.21.7) [release-branch.go1.21] go1.21.7
2fdad8af6d [release-branch.go1.21] cmd/internal/obj/arm64: fix frame pointer
restore in epilogue
01c93ad049 [release-branch.go1.21] cmd/go/internal/g
Upgrade to latest 1.21.x release [1]:
$ git --no-pager log --oneline go1.21.0..go1.21.5
6018ad99a4 (tag: go1.21.5) [release-branch.go1.21] go1.21.5
ec8c526e4b [release-branch.go1.21] net/http: limit chunked data overhead
f7a79cb5fc [release-branch.go1.21] cmd/compile: fix findIndVar so it does not
Since go-1.21 GOPROXY needs to be set explicitly, otherwise it fails with:
- GOPROXY list is not the empty string, but contains no entries
This fixes the selftest
Signed-off-by: Jose Quaresma
---
meta/lib/oeqa/selftest/cases/gotoolchain.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/met
With go-1.21 dynamic linking cause a runtime panic:
| root@qemux86-64:~# go-helloworld
| panic: runtime error: index out of range [0] with length 0
|
| goroutine 1 [running]:
| flag.init()
| /usr/lib/go/src/flag/flag.go:1199 +0xf9
In my opinion, this would be a good trade-off so that we c
All,
Please note that we have our regularly scheduled OpenEmbedded Happy Hour later
today, February 28 for Asia/Pacific timezones at 2100/9pm UTC (4pm ET/1pm PT)
https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedt
On Wed, 28 Feb 2024 at 16:41, Philip Lorenz wrote:
> > I'm assuming this data wouldn't be that large or that expensive to
> > compute so I'd prefer not to hide it behind extra configuration options
> > if we can help it. That does depend on the overheads/costs though.
> >
> I just executed build I
From: Alexis Lothoré
The recently introduced postactions module can raise, on failing ptests,
the following warning:
WARNING: core-image-ptest-glib-2.0-1.0-r0 do_testimage: Can not get host
disk usage: [Errno 2] No such file or directory: '/usr/bin/df'
The issue is likely not happening because
* Includes an upgrade to pyo3 from 0.20.0 to 0.20.3 which fixes ppc64
* Refresh -crates.inc
https://cryptography.io/en/latest/changelog/#v42-0-5
https://cryptography.io/en/latest/changelog/#v42-0-4
https://cryptography.io/en/latest/changelog/#v42-0-3
42.0.5 - 2024-02-23
* Limit the number of name
This upgrade fixes CVE-2024-26130 and also upgraes the pyo3 crate
to 0.20.3 which fixes builds for ppc64.
Supercedes:
"python3-cryptography: Update pyo3 crate to 0.20.3"
https://patchwork.yoctoproject.org/project/oe-core/patch/20240227175138.2843184-2-raj.k...@gmail.com/
"python3-cryptography{-ve
No
On Wed, Feb 28, 2024 at 7:36 AM Tim Orling wrote:
>
>
> On Tue, Feb 27, 2024 at 10:12 PM Khem Raj wrote:
>
>> On Tue, Feb 27, 2024 at 10:59 AM Tim Orling wrote:
>> >
>> >
>> >
>> > On Tue, Feb 27, 2024 at 9:51 AM Khem Raj wrote:
>> >>
>> >> This gets it building on architectures without 64
We need the change in 42.0.5 for ppc64 support.
I will submit the full bump from 42.0.2 to 42.0.5 later today.
On Tue, Feb 27, 2024 at 11:38 PM Soumya via lists.openembedded.org
wrote:
> From: Soumya Sambu
>
> Changelog:
> ==
> 42.0.4 - 2024-02-20
> * Fixed a null-pointer-dereference a
Hi Richard,
On 28.02.24 10:14, Richard Purdie wrote:
On Wed, 2024-02-28 at 07:21 +0100, Philip Lorenz wrote:
With the introduction of debuginfod ([1]), providing debug symbols to
developers has been greatly simplified. Initial support for spawning a
debuginfod server is already available as par
On Tue, Feb 27, 2024 at 10:12 PM Khem Raj wrote:
> On Tue, Feb 27, 2024 at 10:59 AM Tim Orling wrote:
> >
> >
> >
> > On Tue, Feb 27, 2024 at 9:51 AM Khem Raj wrote:
> >>
> >> This gets it building on architectures without 64bit atomics.
> >>
> >
> > We could also upgrade to python3-cryptograph
Apologies for the late reply. Can you please recheck the patch again?
Same patch works in our build without any Hunk failure issue, and also
confirmed that the patch changes are available in the source code of nghttp2
V1.47.0.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this
Hi Alex,
On 28.02.24 08:41, Alexander Kanavin wrote:
On Wed, 28 Feb 2024 at 07:22, Philip Lorenz wrote:
However, this relies on debuginfod scraping the debug packages for their
build IDs. This is not only inefficient (as all packages need to be
extracted again), but it also does not scale well
Don’t copy paste from target install. Make a function.
Alex
On Wed 28. Feb 2024 at 16.02, Oleh Matiusha via lists.openembedded.org
wrote:
> Nativesdk package contains host references in output packages.
> Remove them.
>
> Signed-off-by: Oleh Matiusha
> ---
> meta/recipes-extended/bash/bash.in
Nativesdk package contains host references in output packages.
Remove them.
Signed-off-by: Oleh Matiusha
---
meta/recipes-extended/bash/bash.inc | 21 +
1 file changed, 21 insertions(+)
diff --git a/meta/recipes-extended/bash/bash.inc
b/meta/recipes-extended/bash/bash.inc
i
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/gstreamer1.0-skip-a-test-that-is-known-to-be-flaky.patch
FAIL: test Upstream-Status presence: Upstream-Status is In
On Wed, 2024-02-28 at 15:32 +0800, wangmy via lists.openembedded.org
wrote:
> From: Wang Mingyu
>
> Changelog:
> ==
> -Do not load filelists metadata by default
> -Disable deltarpm support
> -Add a hint for user on transaction file dependency failure
> -Fix failing API unit test on rawhid
From: Ross Burton
The aggregator testcase test_infinite_seek_50_src_live is known upstream
to be flaky[1] and when this fails in their CI they just ignore it.
It's failing often on our autobuilder, so disable the test case for now
until upstream have resolved this issue.
[ YOCTO #15054 ]
[1] h
Jose Quaresma via lists.openembedded.org escreveu (terça, 27/02/2024 à(s) 15:20):
>
>
> Bruce Ashfield escreveu (terça, 27/02/2024
> à(s) 14:01):
>
>> On Tue, Feb 27, 2024 at 8:57 AM Richard Purdie
>> wrote:
>> >
>> > On Tue, 2024-02-27 at 10:13 +, Jose Quaresma wrote:
>> > > Hi,
>> > >
>>
ChenQi escreveu (quarta, 28/02/2024 à(s) 02:38):
> Is this 1.21 upgrade going to be merged in LTS 5.0?
> The reason I'm asking is that I'm going to upgrade some recipes in
> meta-virt and I'd like to check what would be the go version in the next
> release.
>
I am still testing in my distro with
Thank you for sending these patchsets regularly, it's much
appreciated. We struggle to keep up with upstream releases, and this
work helps a lot.
Alex
On Wed, 28 Feb 2024 at 08:33, wangmy via lists.openembedded.org
wrote:
>
> From: Wang Mingyu
>
> License-Update:
> docs(COPYING): use unmodifie
On Wed, 28 Feb 2024 at 04:19, Changqing Li wrote:
> 1.
>
> Currently, There is one line in /usr/lib/tmpfile.d/legacy.conf(this is in
> package systemd),
>
> "L /var/log/README - - - - ../../usr/share/doc/systemd/README.logs"
>
> This line will create an link to "${datadir}/doc/systemd/README.log
On Wed, 28 Feb 2024 at 03:45, Xiangyu Chen
wrote:
> Since SHIFTJIS is not a ISO2022/posix compliant and not in the list of
> glibc locale data support, it was generated by manual with localedef and
> don't have a unified name.
>
>
> The following name has been already found on different linux:
>
>
On Wed, 28 Feb 2024 at 02:54, Changqing Li wrote:
> Yes, the wrong location is the only problem. V4 patch is a way to make native
> tic install to a right location.
>
> but this solution (hardcode output dir to $(DESTDIR)$(datadir)/terminfo) is
> rejected by upstream.
>
> if use V4 patch, we
On Wed, 2024-02-28 at 07:21 +0100, Philip Lorenz wrote:
> With the introduction of debuginfod ([1]), providing debug symbols to
> developers has been greatly simplified. Initial support for spawning a
> debuginfod server is already available as part of poky.
>
> However, this relies on debuginfod
38 matches
Mail list logo
