Re: [OE-core] [PATCH] wic partition.py: add --apparent-size to du calls
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 get other reports in of issues,
> > > I'm
> > > going to be left to somehow fix those other problems. Since your
> > > case
> > > will work you will object if I revert this but you likely won't
> > > have
> > > time to work on the resulting other issues, or be able to reproduce
> > > them since you're building on zfs.
> > >
> > > So you can see my dilemma? :/
> > >
> > > Most people don't build on zfs which is probably what I need to
> > > balance
> > > this on.
> >
> > What if I make this optional for zfs? If build directory type is zfs,
> > then --apparent-size is added, else not.
>
> Wouldn't that cause some really interesting bug reports?
Well, if anyone builds on zfs they will hit bugs like this.
zfs usage can be detected and build can fail nicely or apply
the workaround/fix in wic.
> Asking the user to report their host system filesystem type to debug
> anything isn't going to be great.
>
> I don't like the idea of the non-determinism that introduces but I
> agree we do already have a determinism issue.
>
> What we probably need is the absolute files size, plus a number of
> files and a number of directories, then you can round up to the worst
> cases for the block size.
>
> Currently that size number is just including the block sizes.
FWIW, I tried to move this workaround into image recipe with
IMAGE_CMD:wic:prepend() {
alias df="df --apparent-size"
}
but wic python code doesn't seem to take this into account. Tried also
changing the du calls to have exec_cmd(..., as_shell=True) but this didn't
help either. Something in wic causes the use of another shell or different
default
environment for processes.
So I'm stuck with this change in poky to build on a machine with zfs.
Any hints how to apply this simple workaround are welcome.
Cheers,
-Mikko
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196417):
https://lists.openembedded.org/g/openembedded-core/message/196417
Mute This Topic: https://lists.openembedded.org/mt/104600633/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH V5] systemd: fix a dead link under /var/log
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:
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 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.logs" during
boot,
and ${datadir}/doc/systemd/README.logs is in package systemd-doc. So there will
be dead link when systemd-doc is not installed.
So that's why I create another legacy-doc.conf packaged into systemd-doc
Then legacy.conf and README.logs should be placed into the same
package. I would suggest that README.logs just goes into main systemd
package. (the other option is placing legacy.conf into systemd-doc,
but that file is not doc-specific, and should stay in systemd package,
especially if more entries are added to it).
The solution is also good. But package "${docdir}/systemd/README.logs" in
package systemd may make things more complicated.
since in bitabke .conf, ${PN}-doc is before ${PN} in PACKAGES, and FILES:${PN}-doc =
"${docdir} ...". we need to adjust the sequence,
and may have influences to current list of files and directories that are
placed in a package.
So maybe this patch is more simple and reasonable, and will not have other
impact.
2.
The symlink in legacy.conf use relative path. but for oe, when
VOLATILE_LOG_DIR is true, /var/log is a link to /var/volatile/log, so
/var/log/README need link to ../../../usr/share/doc/systemd/README.logs,
while VOLATILE_LOG_DIR is false, /var/log is a dir, so /var/log/README
need link to ../../usr/share/doc/systemd/README.logs.
After change it to absolute path, checking of VOLATILE_LOG_DIR is not needed.
That's ok, but can you make fixing the path to an absolute one a
separate, second commit then?
if use solution in this patch, it is better they are in one commit. I can
update description more detail.
You could also explore using -Dcreate-log-dirs=false via EXTRA_OEMESON
Thanks. I had do some research about turn off CREATE_LOG_DIR,
if turn off CREATE_LOG_DIR, " /var/log/journal/" will not be created.
By default, VOLATILE__LOG_DIR = "yes", this change will have no
influence, since we will remove content under /var/log.
if VOLATILE_LOG_DIR set to "no", the current default behavior will be
changed, log will saved from persistent to memory. our default
Storage set to auto, if " /var/log/journal/" not exist, the log will
save in memory /run/log/journal. Refer [1]. So I did not try to turn
off it in case current default behavior is changed.
Refer:
[1] https://www.freedesktop.org/software/systemd/man/journald.conf.html
//Changqing
Thanks
Changqing
Thanks,
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196416):
https://lists.openembedded.org/g/openembedded-core/message/196416
Mute This Topic: https://lists.openembedded.org/mt/104598170/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH V5] systemd: fix a dead link under /var/log
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 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.logs" during
> boot,
>
> and ${datadir}/doc/systemd/README.logs is in package systemd-doc. So there
> will be dead link when systemd-doc is not installed.
>
> So that's why I create another legacy-doc.conf packaged into systemd-doc
>
> Then legacy.conf and README.logs should be placed into the same
> package. I would suggest that README.logs just goes into main systemd
> package. (the other option is placing legacy.conf into systemd-doc,
> but that file is not doc-specific, and should stay in systemd package,
> especially if more entries are added to it).
>
> The solution is also good. But package "${docdir}/systemd/README.logs" in
> package systemd may make things more complicated.
>
> since in bitabke .conf, ${PN}-doc is before ${PN} in PACKAGES, and
> FILES:${PN}-doc = "${docdir} ...". we need to adjust the sequence,
>
> and may have influences to current list of files and directories that are
> placed in a package.
>
> So maybe this patch is more simple and reasonable, and will not have other
> impact.
>
> 2.
>
> The symlink in legacy.conf use relative path. but for oe, when
> VOLATILE_LOG_DIR is true, /var/log is a link to /var/volatile/log, so
>
> /var/log/README need link to ../../../usr/share/doc/systemd/README.logs,
>
> while VOLATILE_LOG_DIR is false, /var/log is a dir, so /var/log/README
>
> need link to ../../usr/share/doc/systemd/README.logs.
>
> After change it to absolute path, checking of VOLATILE_LOG_DIR is not needed.
>
> That's ok, but can you make fixing the path to an absolute one a
> separate, second commit then?
>
> if use solution in this patch, it is better they are in one commit. I can
> update description more detail.
>
You could also explore using -Dcreate-log-dirs=false via EXTRA_OEMESON
> Thanks
>
> Changqing
>
> Thanks,
> Alex
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196415):
https://lists.openembedded.org/g/openembedded-core/message/196415
Mute This Topic: https://lists.openembedded.org/mt/104598170/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH V5] systemd: fix a dead link under /var/log
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 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.logs" during
boot,
and ${datadir}/doc/systemd/README.logs is in package systemd-doc. So there will
be dead link when systemd-doc is not installed.
So that's why I create another legacy-doc.conf packaged into systemd-doc
Then legacy.conf and README.logs should be placed into the same
package. I would suggest that README.logs just goes into main systemd
package. (the other option is placing legacy.conf into systemd-doc,
but that file is not doc-specific, and should stay in systemd package,
especially if more entries are added to it).
The solution is also good. But package "${docdir}/systemd/README.logs"
in package systemd may make things more complicated.
since in bitabke .conf, ${PN}-doc is before ${PN} in PACKAGES, and
FILES:${PN}-doc = "${docdir} ...". we need to adjust the sequence,
and may have influences to current list of files and directories that
are placed in a package.
So maybe this patch is more simple and reasonable, and will not have
other impact.
2.
The symlink in legacy.conf use relative path. but for oe, when
VOLATILE_LOG_DIR is true, /var/log is a link to /var/volatile/log, so
/var/log/README need link to ../../../usr/share/doc/systemd/README.logs,
while VOLATILE_LOG_DIR is false, /var/log is a dir, so /var/log/README
need link to ../../usr/share/doc/systemd/README.logs.
After change it to absolute path, checking of VOLATILE_LOG_DIR is not needed.
That's ok, but can you make fixing the path to an absolute one a
separate, second commit then?
if use solution in this patch, it is better they are in one commit. I
can update description more detail.
Thanks
Changqing
Thanks,
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196414):
https://lists.openembedded.org/g/openembedded-core/message/196414
Mute This Topic: https://lists.openembedded.org/mt/104598170/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] llvm: Update to 18.1.0 RC4
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 100644
--- a/meta/recipes-devtools/llvm/llvm_git.bb
+++ b/meta/recipes-devtools/llvm/llvm_git.bb
@@ -24,7 +24,7 @@ MAJOR_VERSION = "${@oe.utils.trim_version("${PV}", 1)}"
LLVM_RELEASE = "${PV}"
BRANCH = "release/${MAJOR_VERSION}.x"
-SRCREV = "0d656f0f12d447ac0e197618a0d25495d66388d1"
+SRCREV = "461274b81d8641eab64d494accddc81d7db8a09e"
SRC_URI =
"git://github.com/llvm/llvm-project.git;branch=${BRANCH};protocol=https \
file://0007-llvm-allow-env-override-of-exe-path.patch;striplevel=2 \
file://0001-AsmMatcherEmitter-sort-ClassInfo-lists-by-name-as-we.patch;striplevel=2
\
@@ -148,6 +148,7 @@ FILES:${PN}-bugpointpasses = "\
FILES:${PN}-libllvm = "\
${libdir}/libLLVM-${MAJOR_VERSION}.so \
+${libdir}/libLLVM.so.${MAJOR_VER}.${MINOR_VER} \
"
FILES:${PN}-liblto += "\
--
2.44.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196412):
https://lists.openembedded.org/g/openembedded-core/message/196412
Mute This Topic: https://lists.openembedded.org/mt/104638745/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] go: filter out build specific path from the linker flags
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 build specific path from the linker flags
[1] https://github.com/golang/go/issues/63760
Signed-off-by: Changqing Li
---
meta/recipes-devtools/go/go-1.20.14.inc | 2 +-
...ut-build-specific-paths-from-linker-.patch | 61 +++
...not-write-linker-flags-into-buildids.patch | 41 -
3 files changed, 62 insertions(+), 42 deletions(-)
create mode 100644
meta/recipes-devtools/go/go/0001-exec.go-filter-out-build-specific-paths-from-linker-.patch
delete mode 100644
meta/recipes-devtools/go/go/0007-exec.go-do-not-write-linker-flags-into-buildids.patch
diff --git a/meta/recipes-devtools/go/go-1.20.14.inc
b/meta/recipes-devtools/go/go-1.20.14.inc
index 7e425effe5..0726da100f 100644
--- a/meta/recipes-devtools/go/go-1.20.14.inc
+++ b/meta/recipes-devtools/go/go-1.20.14.inc
@@ -11,8 +11,8 @@ SRC_URI += "\
file://0004-make.bash-override-CC-when-building-dist-and-go_boot.patch \
file://0005-cmd-dist-separate-host-and-target-builds.patch \
file://0006-cmd-go-make-GOROOT-precious-by-default.patch \
-file://0007-exec.go-do-not-write-linker-flags-into-buildids.patch \
file://0008-src-cmd-dist-buildgo.go-do-not-hardcode-host-compile.patch \
file://0009-go-Filter-build-paths-on-staticly-linked-arches.patch \
+file://0001-exec.go-filter-out-build-specific-paths-from-linker-.patch \
"
SRC_URI[main.sha256sum] =
"1aef321a0e3e38b7e91d2d7eb64040666cabdcc77d383de3c9522d0d69b67f4e"
diff --git
a/meta/recipes-devtools/go/go/0001-exec.go-filter-out-build-specific-paths-from-linker-.patch
b/meta/recipes-devtools/go/go/0001-exec.go-filter-out-build-specific-paths-from-linker-.patch
new file mode 100644
index 00..c5bf28f54a
--- /dev/null
+++
b/meta/recipes-devtools/go/go/0001-exec.go-filter-out-build-specific-paths-from-linker-.patch
@@ -0,0 +1,61 @@
+From 083b5c74b12a1abeb11dd7f58a1cb1593dc0 Mon Sep 17 00:00:00 2001
+From: Changqing Li
+Date: Tue, 27 Feb 2024 18:06:51 +0800
+Subject: [PATCH] exec.go: filter out build-specific paths from linker flags
+
+The flags can contain build-specific paths, breaking reproducibility.
+Filter out options that have build-specific paths.
+
+Upstream-Status: Inappropriate [ Not perfect for upstream ]
+
+Signed-off-by: Changqing Li
+---
+ src/cmd/go/internal/work/exec.go | 25 -
+ 1 file changed, 24 insertions(+), 1 deletion(-)
+
+diff --git a/src/cmd/go/internal/work/exec.go
b/src/cmd/go/internal/work/exec.go
+index cde867b..e3ce17d 100644
+--- a/src/cmd/go/internal/work/exec.go
b/src/cmd/go/internal/work/exec.go
+@@ -1358,6 +1358,29 @@ func (b *Builder) linkActionID(a *Action)
cache.ActionID {
+ return h.Sum()
+ }
+
++func filterLinkerFlags(flags []string) []string {
++ var newflags []string
++ var skipflag bool
++ skipflag = false
++ for i, flag := range flags {
++ if skipflag == true {
++ skipflag = false
++ continue
++ }
++ if strings.HasPrefix(flag, "--sysroot") ||
strings.HasPrefix(flag, "-fmacro-prefix-map") || strings.HasPrefix(flag,
"-fdebug-prefix-map") || strings.HasPrefix(flag, "-ffile-prefix-map") ||
strings.HasPrefix(flag, "-fcanon-prefix-map") || strings.HasPrefix(flag,
"-fprofile-prefix-map") || strings.HasPrefix(flag, "-Wl,-rpath-link"){
++ continue
++ } else if strings.HasPrefix(flag, "-extldflags") {
++ skipflag = true
++ newflags = append(newflags, flag)
++ var filterd_Extldflags []string =
filterLinkerFlags(strings.Split(flags[i+1], " "))
++ newflags = append(newflags,
strings.Join(filterd_Extldflags, " "))
++ } else {
++ newflags = append(newflags, flag)
++ }
++ }
++ return newflags
++}
++
+ // printLinkerConfig prints the linker config into the hash h,
+ // as part of the computation of a linker-related action ID.
+ func (b *Builder) printLinkerConfig(h io.Writer, p *load.Package) {
+@@ -1368,7 +1391,7 @@ func (b *Builder) printLinkerConfig(h io.Writer, p
*load.Package) {
+ case "gc":
+ fmt.Fprintf(h, "link %s %q %s\n", b.toolID("link"),
forcedLdflags, ldBuildmode)
+ if p != nil {
+- fmt.Fprintf(h, "linkflags %q\n", p.Internal.Ldflags)
++ fmt.Fprintf(h, "linkflags %q\n",
filterLinkerFlags(p.Internal.Ldflags))
+ }
+
+ // GOARM, GOMIPS, etc.
+--
+2.25.1
+
diff --git
a/meta/recipes-devtools/go/go/0007-exec.go-do-not-write-linker-flags-into-buildids.patch
[OE-core] [PATCH] mirrors: Switch llvm to use shallow cloning
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 insertions(+), 1 deletion(-)
diff --git a/meta/classes-global/mirrors.bbclass
b/meta/classes-global/mirrors.bbclass
index af66fb1832f..862648eec5f 100644
--- a/meta/classes-global/mirrors.bbclass
+++ b/meta/classes-global/mirrors.bbclass
@@ -83,7 +83,7 @@ git://.*/.* git://HOST/PATH;protocol=https \
git://.*/.* git://HOST/git/PATH;protocol=https \
"
-# Switch glibc and binutils recipes to use shallow clones as they're large and
this
+# Switch llvm, glibc and binutils recipes to use shallow clones as they're
large and this
# improves user experience whilst allowing the flexibility of git urls in the
recipes
BB_GIT_SHALLOW:pn-binutils = "1"
BB_GIT_SHALLOW:pn-binutils-cross-${TARGET_ARCH} = "1"
@@ -98,3 +98,7 @@ BB_GIT_SHALLOW:pn-glibc = "1"
BB_GIT_SHALLOW:pn-glibc-tests = "1"
PREMIRRORS += "git://sourceware.org/git/glibc.git
https://downloads.yoctoproject.org/mirror/sources/ \
git://sourceware.org/git/binutils-gdb.git
https://downloads.yoctoproject.org/mirror/sources/;
+
+BB_GIT_SHALLOW:pn-llvm = "1"
+BB_GIT_SHALLOW:pn-llvm-native = "1"
+BB_GIT_SHALLOW:pn-nativesdk-llvm = "1"
--
2.40.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196410):
https://lists.openembedded.org/g/openembedded-core/message/196410
Mute This Topic: https://lists.openembedded.org/mt/104633560/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 14/48] libpcre2: upgrade 10.42 -> 10.43
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 finer heap
> control.
> * New option flags to restrict the interaction between ASCII and non-ASCII
> characters for caseless matching and \d and friends. There are also new
> pattern constructs to control these flags from within a pattern.
> * Upgrade to Unicode 15.0.0.
> * Treat a NULL pattern with zero length as an empty string.
> * Added support for limited-length variable-length lookbehind assertions, with
> a default maximum length of 255 characters (same as Perl) but with a
> function
> to adjust the limit.
> * Support for LoongArch in JIT.
> * Perl changed the meaning of (for example) {,3} which did not used to be
> recognized as a quantifier. Now it means {0,3} and PCRE2 has also changed.
> Note that {,} is still not a quantifier.
> * Following Perl, allow spaces and tabs after { and before } in all Perl-
> compatible items that use braces, and also around commas in quantifiers. The
> one exception in PCRE2 is \u{...}, which is from ECMAScript, not Perl, and
> PCRE2 follows ECMAScript usage.
> * Changed the meaning of \w and its synonyms and derivatives (\b and \B) in
> UCP
> mode to follow Perl. It now matches characters whose general categories are
> L
> or N or whose particular categories are Mn (non-spacing mark) or Pc
> (combining punctuation).
> * Changed the default meaning of [:xdigit:] in UCP mode to follow Perl. It now
> matches the "fullwidth" versions of hex digits. PCRE2_EXTRA_ASCII_DIGIT can
> be used to keep it ASCII only.
> * Make PCRE2_UCP the default in UTF mode in pcre2grep and add -no_ucp,
> --case-restrict and --posix-digit.
> * Add --group-separator and --no-group-separator to pcre2grep.
>
> Signed-off-by: Wang Mingyu
> ---
> .../libpcre/{libpcre2_10.42.bb => libpcre2_10.43.bb} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-support/libpcre/{libpcre2_10.42.bb => libpcre2_10.43.bb}
> (92%)
This breaks glib-2.0 ptests:
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/6325/
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/6136
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196409):
https://lists.openembedded.org/g/openembedded-core/message/196409
Mute This Topic: https://lists.openembedded.org/mt/104619614/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 24/48] minicom: upgrade 2.8 -> 2.9
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 to No.
> - Timestamping mode is now saved and restored.
> - Split "Screen and Keyboard" menu into two menus.
> - Update to gettext-0.21.
> - Change return values of --help and --version to success.
> - Support higher baud rates on MacOS
> - Save character send delay to config file
> - Save newline send delay to config file
> - Update translations: Romanian, German, French, Norwegian/Bookmal, Polish,
> Serbian, Swedish
> - New translation: Georgian, Korean
>
> Signed-off-by: Wang Mingyu
> ---
> ...ix-minicom-h-v-return-value-is-not-0.patch | 33 ---
> .../minicom/allow.to.disable.lockdev.patch | 30 -
> .../{minicom_2.8.bb => minicom_2.9.bb} | 7 ++--
> 3 files changed, 2 insertions(+), 68 deletions(-)
> delete mode 100644
> meta/recipes-extended/minicom/minicom/0001-fix-minicom-h-v-return-value-is-not-0.patch
> delete mode 100644
> meta/recipes-extended/minicom/minicom/allow.to.disable.lockdev.patch
> rename meta/recipes-extended/minicom/{minicom_2.8.bb => minicom_2.9.bb} (80%)
This breaks selftests in devtool:
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/6478/steps/14/logs/stdio
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196408):
https://lists.openembedded.org/g/openembedded-core/message/196408
Mute This Topic: https://lists.openembedded.org/mt/104619622/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [RFC OE-core][PATCH v2 7/7] go: bump 1.22.0
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} | 0
...{go-cross_1.21.7.bb => go-cross_1.22.0.bb} | 0
...osssdk_1.21.7.bb => go-crosssdk_1.22.0.bb} | 0
...o-native_1.21.7.bb => go-native_1.22.0.bb} | 0
...runtime_1.21.7.bb => go-runtime_1.22.0.bb} | 0
...ent-based-hash-generation-less-pedan.patch | 32 +--
...OOLDIR-to-be-overridden-in-the-envir.patch | 8 ++---
...3-ld-add-soname-to-shareable-objects.patch | 10 +++---
...de-CC-when-building-dist-and-go_boot.patch | 6 ++--
...dist-separate-host-and-target-builds.patch | 18 +--
...d-go-make-GOROOT-precious-by-default.patch | 22 ++---
...not-write-linker-flags-into-buildids.patch | 8 ++---
...ldgo.go-do-not-hardcode-host-compile.patch | 4 +--
...uild-paths-on-staticly-linked-arches.patch | 10 +++---
.../go/{go_1.21.7.bb => go_1.22.0.bb} | 0
18 files changed, 64 insertions(+), 64 deletions(-)
rename meta/recipes-devtools/go/{go-1.21.7.inc => go-1.22.0.inc} (89%)
rename meta/recipes-devtools/go/{go-binary-native_1.21.7.bb =>
go-binary-native_1.22.0.bb} (78%)
rename meta/recipes-devtools/go/{go-cross-canadian_1.21.7.bb =>
go-cross-canadian_1.22.0.bb} (100%)
rename meta/recipes-devtools/go/{go-cross_1.21.7.bb => go-cross_1.22.0.bb}
(100%)
rename meta/recipes-devtools/go/{go-crosssdk_1.21.7.bb =>
go-crosssdk_1.22.0.bb} (100%)
rename meta/recipes-devtools/go/{go-native_1.21.7.bb => go-native_1.22.0.bb}
(100%)
rename meta/recipes-devtools/go/{go-runtime_1.21.7.bb => go-runtime_1.22.0.bb}
(100%)
rename meta/recipes-devtools/go/{go_1.21.7.bb => go_1.22.0.bb} (100%)
diff --git a/meta/conf/distro/include/tcmode-default.inc
b/meta/conf/distro/include/tcmode-default.inc
index 87666e5837..4c6fcbc436 100644
--- a/meta/conf/distro/include/tcmode-default.inc
+++ b/meta/conf/distro/include/tcmode-default.inc
@@ -23,7 +23,7 @@ GDBVERSION ?= "14.%"
GLIBCVERSION ?= "2.39%"
LINUXLIBCVERSION ?= "6.6%"
QEMUVERSION ?= "8.2%"
-GOVERSION ?= "1.21%"
+GOVERSION ?= "1.22%"
RUSTVERSION ?= "1.74%"
PREFERRED_VERSION_gcc ?= "${GCCVERSION}"
diff --git a/meta/recipes-devtools/go/go-1.21.7.inc
b/meta/recipes-devtools/go/go-1.22.0.inc
similarity index 89%
rename from meta/recipes-devtools/go/go-1.21.7.inc
rename to meta/recipes-devtools/go/go-1.22.0.inc
index 6de24e1e22..230ada5e4b 100644
--- a/meta/recipes-devtools/go/go-1.21.7.inc
+++ b/meta/recipes-devtools/go/go-1.22.0.inc
@@ -15,4 +15,4 @@ SRC_URI += "\
file://0008-src-cmd-dist-buildgo.go-do-not-hardcode-host-compile.patch \
file://0009-go-Filter-build-paths-on-staticly-linked-arches.patch \
"
-SRC_URI[main.sha256sum] =
"00197ab20f33813832bff62fd93cca1c42a08cc689a32a6672ca49591959bff6"
+SRC_URI[main.sha256sum] =
"4d196c3d41a0d6c1dfc64d04e3cc1f608b0c436bd87b7060ce3e23234e1f4d5c"
diff --git a/meta/recipes-devtools/go/go-binary-native_1.21.7.bb
b/meta/recipes-devtools/go/go-binary-native_1.22.0.bb
similarity index 78%
rename from meta/recipes-devtools/go/go-binary-native_1.21.7.bb
rename to meta/recipes-devtools/go/go-binary-native_1.22.0.bb
index d8826e20f1..da3a8f2237 100644
--- a/meta/recipes-devtools/go/go-binary-native_1.21.7.bb
+++ b/meta/recipes-devtools/go/go-binary-native_1.22.0.bb
@@ -9,9 +9,9 @@ PROVIDES = "go-native"
# Checksums available at https://go.dev/dl/
SRC_URI =
"https://dl.google.com/go/go${PV}.${BUILD_GOOS}-${BUILD_GOARCH}.tar.gz;name=go_${BUILD_GOTUPLE};
-SRC_URI[go_linux_amd64.sha256sum] =
"13b76a9b2a26823e53062fa841b07087d48ae2ef2936445dc34c4ae03293702c"
-SRC_URI[go_linux_arm64.sha256sum] =
"24744edcaeb827aafb76c67ebd406b5ae13291023b0ad9f061dd7a0e75b275ba"
-SRC_URI[go_linux_ppc64le.sha256sum] =
"48a99ecce9b1e632870c29420088f61cf17a6f0c5bdb3cc821ff5c00e14b1a8a"
+SRC_URI[go_linux_amd64.sha256sum] =
"f6c8a87aa03b92c4b0bf3d558e28ea03006eb29db78917daec5cfb6ec1046265"
+SRC_URI[go_linux_arm64.sha256sum] =
"7ca20c077148b69bb99887e04983955e60bd7c70c55e00bf85f9f7194874a3b2"
+SRC_URI[go_linux_ppc64le.sha256sum] =
"0e57f421df9449066f00155ce98a5be93744b3d81b00ee4c2c9b511be2a31d93"
UPSTREAM_CHECK_URI = "https://golang.org/dl/;
UPSTREAM_CHECK_REGEX = "go(?P\d+(\.\d+)+)\.linux"
diff --git a/meta/recipes-devtools/go/go-cross-canadian_1.21.7.bb
b/meta/recipes-devtools/go/go-cross-canadian_1.22.0.bb
similarity index 100%
rename from meta/recipes-devtools/go/go-cross-canadian_1.21.7.bb
rename to meta/recipes-devtools/go/go-cross-canadian_1.22.0.bb
diff --git a/meta/recipes-devtools/go/go-cross_1.21.7.bb
b/meta/recipes-devtools/go/go-cross_1.22.0.bb
similarity index 100%
rename from meta/recipes-devtools/go/go-cross_1.21.7.bb
rename to meta/recipes-devtools/go/go-cross_1.22.0.bb
diff --git a/meta/recipes-devtools/go/go-crosssdk_1.21.7.bb
Re: [OE-core] [PATCH] glib-2.0: backport a switch from distutils to packaging in codegen
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 > with dev-python/setuptools (and for updated glib-2.0-native after > removing dev-python/packaging) > > Fixes sent: > https://patchwork.yoctoproject.org/project/oe/patch/20240227113711.834767-1-martin.ja...@gmail.com/ > https://patchwork.yoctoproject.org/project/oe/patch/20240227113711.834767-2-martin.ja...@gmail.com/ > > Cheers, > > On Tue, Feb 27, 2024 at 12:58 AM Martin Jansa via > lists.openembedded.org > wrote: > > > > Thanks Khem, will try to reproduce tomorrow. Maybe these don't use > > CODEGEN_PYTHON_RDEPENDS. > > > > With this patch backported to kirkstone I've seen glib-2.0-native > > failing with the same issue as python3native there doesn't include > > python3-packaging. > > > > Maybe these recipes aren't using python3native and were depending on > > packaging from host, will debug tomorrow. > > > > On Tue, Feb 27, 2024 at 12:16 AM Khem Raj wrote: > > > > > > I am seeing some build failures which seems to be related to this patch > > > > > > https://autobuilder.yoctoproject.org/typhoon/#/builders/88/builds/3657/steps/15/logs/stdio > > > > > > | File > > > "/home/pokybuild/yocto-worker/meta-oe/build/build/tmp/work/core2-64-poky-linux/gattlib/0.2+git/recipe-sysroot-native/usr/share/glib-2.0/codegen/utils.py", > > > line 22, in > > > | import packaging.version > > > | ModuleNotFoundError: No module named 'packaging' > > > > > > > > > > > > | File > > > "/home/pokybuild/yocto-worker/meta-oe/build/build/tmp/work/core2-64-poky-linux/networkmanager-fortisslvpn/1.4.0/recipe-sysroot-native/usr/share/glib-2.0/codegen/utils.py", > > > line 22, in > > > | import packaging.version > > > | ModuleNotFoundError: No module named 'packaging' > > > | make: *** [Makefile:2081: src/nm-fortisslvpn-pppd-service-dbus.h] > > > Error 1 > > > > > > > > > On Sun, Feb 25, 2024 at 1:37 AM Martin Jansa > > > wrote: > > > > > > > > * to fix build on hosts with python-3.12, now it fails with: > > > > > > > > Traceback (most recent call last): > > > > File "recipe-sysroot-native/usr/bin/gdbus-codegen", line 53, in > > > > > > > > from codegen import codegen_main > > > > File > > > > "recipe-sysroot-native/usr/share/glib-2.0/codegen/codegen_main.py", > > > > line 29, in > > > > from . import dbustypes > > > > File "recipe-sysroot-native/usr/share/glib-2.0/codegen/dbustypes.py", > > > > line 22, in > > > > from . import utils > > > > File "recipe-sysroot-native/usr/share/glib-2.0/codegen/utils.py", > > > > line 22, in > > > > import distutils.version > > > > ModuleNotFoundError: No module named 'distutils' > > > > CMake Error at CMakeLists.txt:90 (message): > > > > Error in generating code for connman interface using gdbus-codegen > > > > > > > > Signed-off-by: Martin Jansa > > > > --- > > > > ...deprecated-distutils-module-to-the-p.patch | 34 +++ > > > > meta/recipes-core/glib-2.0/glib-2.0_2.78.3.bb | 1 + > > > > meta/recipes-core/glib-2.0/glib.inc | 4 +-- > > > > 3 files changed, 36 insertions(+), 3 deletions(-) > > > > create mode 100644 > > > > meta/recipes-core/glib-2.0/glib-2.0/0001-Switch-from-the-deprecated-distutils-module-to-the-p.patch > > > > > > > > diff --git > > > > a/meta/recipes-core/glib-2.0/glib-2.0/0001-Switch-from-the-deprecated-distutils-module-to-the-p.patch > > > > > > > > b/meta/recipes-core/glib-2.0/glib-2.0/0001-Switch-from-the-deprecated-distutils-module-to-the-p.patch > > > > new file mode 100644 > > > > index 00..50368ed22c > > > > --- /dev/null > > > > +++ > > > > b/meta/recipes-core/glib-2.0/glib-2.0/0001-Switch-from-the-deprecated-distutils-module-to-the-p.patch > > > > @@ -0,0 +1,34 @@ > > > > +From 05f0674c93d94fe6b29c1b707980aac469ddcd72 Mon Sep 17 00:00:00 2001 > > > > +From: Jordan Williams > > > > +Date: Fri, 1 Dec 2023 09:53:50 -0600 > > > > +Subject: [PATCH] Switch from the deprecated distutils module to the > > > > packaging > > > > + module > > > > + > > > > +The distutils module was removed in Python 3.12. > > > > + > > > > +Upstream-Status: Backport > > > > [https://gitlab.gnome.org/GNOME/glib/-/commit/6ef967a0f930ce37a8c9b5aff969693b34714291] > > > > + > > > > +Signed-off-by: Martin Jansa > > > > +--- > > > > + gio/gdbus-2.0/codegen/utils.py | 4 ++-- > > > > + 1 file changed, 2 insertions(+), 2 deletions(-) > > > > + > > > > +diff --git a/gio/gdbus-2.0/codegen/utils.py > > > > b/gio/gdbus-2.0/codegen/utils.py > > > > +index 0204610..08f1ba9 100644 > > > > +--- a/gio/gdbus-2.0/codegen/utils.py > > > > b/gio/gdbus-2.0/codegen/utils.py > > > > +@@ -19,7 +19,7 @@ > > > > + # > > > > + # Author: David Zeuthen > > > > + > > > > +-import distutils.version > > > >
[OE-core] [RFC OE-core][PATCH v2 6/7] go: upgrade 1.21.5 -> 1.21.7
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/generate: call
modload.InitWorkFile
db74bfba18 [release-branch.go1.21] Revert "crypto/internal/boring: upgrade
module to fips-20220613" +1
916e6cddf1 [release-branch.go1.21] runtime: fix Pinner.Pin documentation
6552f3d4ac [release-branch.go1.21] cmd/go/internal/toolchain: apply the
-modcacherw flag when downloading a module to determine what toolchain it needs
3960318b87 [release-branch.go1.21] crypto/x509: properly gate test on macos
version
00f974eb1f [release-branch.go1.21] go/types, types2: don't lose position info
of interface embeddings
2f91c16e68 [release-branch.go1.21] runtime: properly model rwmutex in lock
ranking
2540b1436f [release-branch.go1.21] slices: explicitly discard results of some
functions
7e34c4308f [release-branch.go1.21] runtime: clear g0 stack bounds in dropm
491c1e7e95 [release-branch.go1.21] runtime: allow update of system stack bounds
on callback from C thread
caafb50c0d [release-branch.go1.21] runtime: don't print "unexpected SPWRITE"
when printing traceback
cc85462b3d (tag: go1.21.6) [release-branch.go1.21] go1.21.6
d2cb140194 [release-branch.go1.21] crypto/tls: align FIPS-only mode with
BoringSSL policy
368e2a9461 [release-branch.go1.21] crypto/internal/boring: upgrade module to
fips-20220613
8c6078adfb [release-branch.go1.21] runtime: add race annotations in
IncNonDefault
f6b203c828 [release-branch.go1.21] maps: fix aliasing problems with Clone
43818206dc [release-branch.go1.21] runtime: put ReadMemStats debug assertions
behind a double-check mode
cf65d74bc5 [release-branch.go1.21] runtime: add the disablethp GODEBUG setting
ad1ec60a5b [release-branch.go1.21] runtime/pprof: fix generics function names
bbab863ada [release-branch.go1.21] os/signal: skip nohup tests on darwin
builders
7dc67e8f29 [release-branch.go1.21] os/signal: remove go t.Run from TestNohup
9f8b3ac8c4 [release-branch.go1.21] cmd/compile: fix escape analysis of string
min/max
8c840b10d0 [release-branch.go1.21] cmd/compile: fix memcombine pass for big
endian, > 1 byte elements
[1] https://github.com/golang/go/compare/go1.21.5...go1.21.7
Signed-off-by: Jose Quaresma
---
meta/recipes-devtools/go/{go-1.21.5.inc => go-1.21.7.inc} | 2 +-
...binary-native_1.21.5.bb => go-binary-native_1.21.7.bb} | 6 +++---
...oss-canadian_1.21.5.bb => go-cross-canadian_1.21.7.bb} | 0
.../go/{go-cross_1.21.5.bb => go-cross_1.21.7.bb} | 0
.../go/{go-crosssdk_1.21.5.bb => go-crosssdk_1.21.7.bb} | 0
.../go/{go-native_1.21.5.bb => go-native_1.21.7.bb} | 0
.../go/{go-runtime_1.21.5.bb => go-runtime_1.21.7.bb} | 0
...go-Allow-GOTOOLDIR-to-be-overridden-in-the-envir.patch | 2 +-
.../go/go/0003-ld-add-soname-to-shareable-objects.patch | 8
meta/recipes-devtools/go/{go_1.21.5.bb => go_1.21.7.bb} | 0
10 files changed, 9 insertions(+), 9 deletions(-)
rename meta/recipes-devtools/go/{go-1.21.5.inc => go-1.21.7.inc} (89%)
rename meta/recipes-devtools/go/{go-binary-native_1.21.5.bb =>
go-binary-native_1.21.7.bb} (78%)
rename meta/recipes-devtools/go/{go-cross-canadian_1.21.5.bb =>
go-cross-canadian_1.21.7.bb} (100%)
rename meta/recipes-devtools/go/{go-cross_1.21.5.bb => go-cross_1.21.7.bb}
(100%)
rename meta/recipes-devtools/go/{go-crosssdk_1.21.5.bb =>
go-crosssdk_1.21.7.bb} (100%)
rename meta/recipes-devtools/go/{go-native_1.21.5.bb => go-native_1.21.7.bb}
(100%)
rename meta/recipes-devtools/go/{go-runtime_1.21.5.bb => go-runtime_1.21.7.bb}
(100%)
rename meta/recipes-devtools/go/{go_1.21.5.bb => go_1.21.7.bb} (100%)
diff --git a/meta/recipes-devtools/go/go-1.21.5.inc
b/meta/recipes-devtools/go/go-1.21.7.inc
similarity index 89%
rename from meta/recipes-devtools/go/go-1.21.5.inc
rename to meta/recipes-devtools/go/go-1.21.7.inc
index f009ea77c7..6de24e1e22 100644
--- a/meta/recipes-devtools/go/go-1.21.5.inc
+++ b/meta/recipes-devtools/go/go-1.21.7.inc
@@ -15,4 +15,4 @@ SRC_URI += "\
file://0008-src-cmd-dist-buildgo.go-do-not-hardcode-host-compile.patch \
file://0009-go-Filter-build-paths-on-staticly-linked-arches.patch \
"
-SRC_URI[main.sha256sum] =
"285cbbdf4b6e6e62ed58f370f3f6d8c30825d6e56c5853c66d3c23bcdb09db19"
+SRC_URI[main.sha256sum] =
"00197ab20f33813832bff62fd93cca1c42a08cc689a32a6672ca49591959bff6"
diff --git a/meta/recipes-devtools/go/go-binary-native_1.21.5.bb
b/meta/recipes-devtools/go/go-binary-native_1.21.7.bb
similarity index 78%
rename from meta/recipes-devtools/go/go-binary-native_1.21.5.bb
rename to meta/recipes-devtools/go/go-binary-native_1.21.7.bb
index cc79a277ff..d8826e20f1 100644
--- a/meta/recipes-devtools/go/go-binary-native_1.21.5.bb
+++ b/meta/recipes-devtools/go/go-binary-native_1.21.7.bb
@@ -9,9 +9,9 @@ PROVIDES = "go-native"
#
[OE-core] [RFC OE-core][PATCH v2 5/7] go: upgrade 1.21.0 -> 1.21.5
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 match disjointed loop headers 3684d19c20 [release-branch.go1.21] runtime: call enableMetadataHugePages and its callees on the systemstack 9e43850a32 [release-branch.go1.21] crypto/rand,runtime: switch RtlGenRandom for ProcessPrng 8caf4bb3e7 [release-branch.go1.21] path/filepath: consider \\?\c: as a volume on Windows 23c943e529 [release-branch.go1.21] cmd/go/internal/vcs: error out if the requested repo does not support a secure protocol 4952f41180 [release-branch.go1.21] cmd/go: allow 'go mod download' to switch toolchains if called with explicit arguments f26fa05522 [release-branch.go1.21] os: report IO_REPARSE_TAG_DEDUP files as regular in Stat and Lstat 8ae493b5b8 [release-branch.go1.21] internal/poll: add SPLICE_F_NONBLOCK flag for splice to avoid inconsistency with O_NONBLOCK b9f245b8d3 [release-branch.go1.21] cmd/compile: ensure pointer arithmetic happens after the nil check caacf3a09a [release-branch.go1.21] cmd/compile: handle constant pointer offsets in dead store elimination 1e91861f67 [release-branch.go1.21] syscall: copy rlimit.go's build constraint to rlimit_test.go ed817f1c40 (tag: go1.21.4) [release-branch.go1.21] go1.21.4 9e933c189c [release-branch.go1.21] path/filepath: fix various issues in parsing Windows paths 434af8537e [release-branch.go1.21] net/http: pull http2 underflow fix from x/net/http2 7b04d81cbc [release-branch.go1.21] runtime/cgo: avoid taking the address of crosscall2 in code f9a31cda3c [release-branch.go1.21] cmd/compile/internal/typecheck: fix closure field naming 64b6c48107 [release-branch.go1.21] go/types, types2: don't use generics ef6993f327 [release-branch.go1.21] runtime: don't eagerly collapse hugepages bae01521f3 [release-branch.go1.21] go/types, types2: don't implicitly modify an argument function's type 236c07c049 [release-branch.go1.21] cmd/link: split text sections for arm 32-bit 9465990e0e [release-branch.go1.21] all: tidy dependency versioning after release 883f062fc0 (tag: go1.21.3) [release-branch.go1.21] go1.21.3 24ae2d9272 [release-branch.go1.21] net/http: regenerate h2_bundle.go 26b5783b72 (tag: go1.21.2) [release-branch.go1.21] go1.21.2 2ddfc04d12 [release-branch.go1.21] cmd/compile: use absolute file name in isCgo check a15ef1bb0f [release-branch.go1.21] cmd/compile: absorb InvertFlags into Noov comparisons 41d71a5afa [release-branch.go1.21] cmd/compile: reset memcombine correctly between basic blocks 0b6b0a275a [release-branch.go1.21] runtime: always lock OS thread in debugcall cd671a1180 [release-branch.go1.21] runtime: increase g0 stack size in non-cgo case fc57cc31a0 [release-branch.go1.21] cmd/link: suppress -bind_at_load deprecation warning for ld-prime 9bec49cf52 [release-branch.go1.21] cmd/link: disable DWARF by default in c-shared mode on darwin 3ef4f939c3 [release-branch.go1.21] cmd/link: force old Apple linker in plugin mode 556e9c36ba [release-branch.go1.21] cmd/link: avoid deadcode of global map vars for programs using plugins b64dc5f499 [release-branch.go1.21] cmd/go: in TestScript/gotoolchain_path, remove the user's PATH cd66ca0636 [release-branch.go1.21] runtime/metrics: fix /gc/scan/* metrics d7a0626806 [release-branch.go1.21] runtime: ignore SPWrite on innermost traceback frame 2c1e5b05fe (tag: go1.21.1) [release-branch.go1.21] go1.21.1 bbd043ff0d [release-branch.go1.21] html/template: properly handle special tags within the script context b0e1d3ea26 [release-branch.go1.21] html/template: support HTML-like comments in script contexts d25a935574 [release-branch.go1.21] cmd/go: reject toolchain directives containing path separators e3ba569c78 [release-branch.go1.21] net/http: revert "support streaming POST content in wasm" 8dc6ad1c61 [release-branch.go1.21] runtime: restore caller's frame pointer when recovering from panic 06df3292a8 [release-branch.go1.21] runtime: avoid MADV_HUGEPAGE for heap memory b120517ffd [release-branch.go1.21] go/types, types2: remove order dependency in inference involving channels 0a9582163c [release-branch.go1.21] cmd/go: retry ETXTBSY errors when running test binaries 91a4e74b98 [release-branch.go1.21] crypto/tls: QUIC: fix panics when processing post-handshake messages 6385a6fb18 [release-branch.go1.21] cmd/go: find GOROOT using os.Executable when installed to GOROOT/bin/GOOS_GOARCH 2d07bb86f0 [release-branch.go1.21] encoding/xml: overriding by empty namespace when no new name declaration 745b81b6e6 [release-branch.go1.21] encoding/gob: prevent panic from index out of range in Decoder.typeString 13339c75b8 [release-branch.go1.21] runtime: fix maps.Clone bug when cloning a map mid-grow 2977709875 [release-branch.go1.21] context: fix synchronization in
[OE-core] [RFC OE-core][PATCH v2 4/7] oeqa/gotoolchain: set GOPROXY
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/meta/lib/oeqa/selftest/cases/gotoolchain.py
b/meta/lib/oeqa/selftest/cases/gotoolchain.py
index 74c1c48117..ee2cf4b09a 100644
--- a/meta/lib/oeqa/selftest/cases/gotoolchain.py
+++ b/meta/lib/oeqa/selftest/cases/gotoolchain.py
@@ -54,6 +54,7 @@ class oeGoToolchainSelfTest(OESelftestTestCase):
cmd = cmd + "export GOPATH=%s; " % self.go_path
cmd = cmd + "export GOFLAGS=-modcacherw; "
cmd = cmd + "export CGO_ENABLED=1; "
+cmd = cmd + "export GOPROXY=https://proxy.golang.org,direct; "
cmd = cmd + "${CROSS_COMPILE}go %s" % gocmd
return runCmd(cmd).status
--
2.44.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196403):
https://lists.openembedded.org/g/openembedded-core/message/196403
Mute This Topic: https://lists.openembedded.org/mt/104628624/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [RFC OE-core][PATCH v2 3/7] goarch: disable dynamic linking globally
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 can update and leave the version 1.20 for the next LTS 5.0 since we are already quite behind on the version available upstream which already has the 1.22 available. Signed-off-by: Jose Quaresma --- meta/classes-recipe/goarch.bbclass | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/meta/classes-recipe/goarch.bbclass b/meta/classes-recipe/goarch.bbclass index 1ebe03864f..6899ec28e4 100644 --- a/meta/classes-recipe/goarch.bbclass +++ b/meta/classes-recipe/goarch.bbclass @@ -38,13 +38,13 @@ BASE_GOARM:armv5 = '5' # Go supports dynamic linking on a limited set of architectures. # See the supportsDynlink function in go/src/cmd/compile/internal/gc/main.go GO_DYNLINK = "" -GO_DYNLINK:arm ?= "1" -GO_DYNLINK:aarch64 ?= "1" -GO_DYNLINK:x86 ?= "1" -GO_DYNLINK:x86-64 ?= "1" -GO_DYNLINK:powerpc64 ?= "1" -GO_DYNLINK:powerpc64le ?= "1" -GO_DYNLINK:class-native ?= "" +GO_DYNLINK:arm = "" +GO_DYNLINK:aarch64 = "" +GO_DYNLINK:x86 = "" +GO_DYNLINK:x86-64 = "" +GO_DYNLINK:powerpc64 = "" +GO_DYNLINK:powerpc64le = "" +GO_DYNLINK:class-native = "" GO_DYNLINK:class-nativesdk = "" # define here because everybody inherits this class -- 2.44.0 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196402): https://lists.openembedded.org/g/openembedded-core/message/196402 Mute This Topic: https://lists.openembedded.org/mt/104628623/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] OpenEmbedded Happy Hour February 28 9pm/2100 UTC
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/fixedtime.html?msg=OpenEmbedded+Happy+Hour+February+28=20240228T21 Best regards, Denys Dmytriyenko OpenEmbedded Board of Directors -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#62641): https://lists.yoctoproject.org/g/yocto/message/62641 Mute This Topic: https://lists.yoctoproject.org/mt/104628429/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files
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 ID extraction on the debug packages of our medium > sized kirkstone based distro (see my reply to Alex for more details). > Sequentially extracting build IDs from around 8000 files took around > 1:30 minutes on my machine. While I wouldn't call this excessive, I am > also not sure whether this is too much overhead given that I only expect > this data to be used in some deployments. I have to object to the numbers because they were done with a sequential shell loop. Debuginfod does it in threads and is able to complete the scans much faster. So you need to check how quickly it completes its job when started with oe-debuginfod rather. There might be an improvement coming from what you are proposing, but it's most likely not going to be as drastic. >From debuginfod manpage: -c NUM --concurrency=NUM Set the concurrency limit for the scanning queue threads, which work together to process archives & files located by the traversal thread. This important for controlling CPU-intensive operations like parsing an ELF file and especially decompressing archives. The default is the number of processors on the system; the minimum is 1. https://manpages.debian.org/testing/debuginfod/debuginfod.8.en.html There's also something else I noticed just now: there seems to be an alternative implementation of debuginfod you want to introduce? Why? If the original from elfutils isn't working well enough, shouldn't we make it better? One possibility is teaching it to mass-import pre-computed entries into its index, so that sweeping file tree scans with archive extractions can be avoided altogether. Or doing incremental index imports directly from do_package. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196398): https://lists.openembedded.org/g/openembedded-core/message/196398 Mute This Topic: https://lists.openembedded.org/mt/104619206/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-Core][PATCH] oeqa/lib/utils/postactions: fix host disk usage stats retrieval
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 of df absence (to be confirmed
amongst the variety of workers) but because of the wrong path. Fix it by
letting subprocess search for df, passing only the binary name. To make it
work, we also have to reset the environment, otherwise the environment
configured before running bitbake will be used, and search will fail.
---
Example of such failure can be found on the autobuilder, as detected by
Richard:
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/6136/steps/13/logs/stdio
Signed-off-by: Alexis Lothoré
---
meta/lib/oeqa/utils/postactions.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/utils/postactions.py
b/meta/lib/oeqa/utils/postactions.py
index 03cecdc21578..8104400ac258 100644
--- a/meta/lib/oeqa/utils/postactions.py
+++ b/meta/lib/oeqa/utils/postactions.py
@@ -38,7 +38,7 @@ def get_host_disk_usage(d, tc):
output_file = os.path.join(get_json_result_dir(d), "artifacts",
"host_disk_usage.txt")
try:
with open(output_file, 'w') as f:
-output = subprocess.run(['/usr/bin/df', '-hl'], check=True,
text=True, stdout=f)
+output = subprocess.run(['df', '-hl'], check=True, text=True,
stdout=f, env={})
except Exception as e:
bb.warn(f"Can not get host disk usage: {e}")
--
2.43.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196397):
https://lists.openembedded.org/g/openembedded-core/message/196397
Mute This Topic: https://lists.openembedded.org/mt/104626401/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH 1/1] python3-cryptography{-vectors}: upgrade to 42.0.5
* 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 constraint checks that will be performed in
X.509 path validation to protect against denial of service attacks.
* Upgrade pyo3 version, which fixes building on PowerPC.
42.0.4 - 2024-02-20
* Fixed a null-pointer-dereference and segfault that could occur when
creating a PKCS#12 bundle. Credit to Alexander-Programming for
reporting the issue. CVE-2024-26130
* Fixed ASN.1 encoding for PKCS7/SMIME signed messages. The fields
SMIMECapabilities and SignatureAlgorithmIdentifier should now be
correctly encoded according to the definitions in RFC 2633 RFC 3370.
42.0.3 - 2024-02-15
* Fixed an initialization issue that caused key loading failures for
some users.
CVE: CVE-2024-26130
https://nvd.nist.gov/vuln/detail/CVE-2024-26130
Signed-off-by: Tim Orling
---
.../python/python3-cryptography-crates.inc| 22 ++-
...=> python3-cryptography-vectors_42.0.5.bb} | 2 +-
0.2.bb => python3-cryptography_42.0.5.bb} | 2 +-
3 files changed, 14 insertions(+), 12 deletions(-)
rename meta/recipes-devtools/python/{python3-cryptography-vectors_42.0.2.bb =>
python3-cryptography-vectors_42.0.5.bb} (91%)
rename meta/recipes-devtools/python/{python3-cryptography_42.0.2.bb =>
python3-cryptography_42.0.5.bb} (95%)
diff --git a/meta/recipes-devtools/python/python3-cryptography-crates.inc
b/meta/recipes-devtools/python/python3-cryptography-crates.inc
index 4714c76bd2b..b26e22b70c3 100644
--- a/meta/recipes-devtools/python/python3-cryptography-crates.inc
+++ b/meta/recipes-devtools/python/python3-cryptography-crates.inc
@@ -25,12 +25,13 @@ SRC_URI += " \
crate://crates.io/parking_lot_core/0.9.9 \
crate://crates.io/pem/3.0.3 \
crate://crates.io/pkg-config/0.3.29 \
+crate://crates.io/portable-atomic/1.6.0 \
crate://crates.io/proc-macro2/1.0.78 \
-crate://crates.io/pyo3/0.20.2 \
-crate://crates.io/pyo3-build-config/0.20.2 \
-crate://crates.io/pyo3-ffi/0.20.2 \
-crate://crates.io/pyo3-macros/0.20.2 \
-crate://crates.io/pyo3-macros-backend/0.20.2 \
+crate://crates.io/pyo3/0.20.3 \
+crate://crates.io/pyo3-build-config/0.20.3 \
+crate://crates.io/pyo3-ffi/0.20.3 \
+crate://crates.io/pyo3-macros/0.20.3 \
+crate://crates.io/pyo3-macros-backend/0.20.3 \
crate://crates.io/quote/1.0.35 \
crate://crates.io/redox_syscall/0.4.1 \
crate://crates.io/scopeguard/1.2.0 \
@@ -74,12 +75,13 @@ SRC_URI[parking_lot-0.12.1.sha256sum] =
"3742b2c103b9f06bc9fff0a37ff4912935851be
SRC_URI[parking_lot_core-0.9.9.sha256sum] =
"4c42a9226546d68acdd9c0a280d17ce19bfe27a46bf68784e4066115788d008e"
SRC_URI[pem-3.0.3.sha256sum] =
"1b8fcc794035347fb64beda2d3b462595dd2753e3f268d89c5aae77e8cf2c310"
SRC_URI[pkg-config-0.3.29.sha256sum] =
"2900ede94e305130c13ddd391e0ab7cbaeb783945ae07a279c268cb05109c6cb"
+SRC_URI[portable-atomic-1.6.0.sha256sum] =
"7170ef9988bc169ba16dd36a7fa041e5c4cbeb6a35b76d4c03daded371eae7c0"
SRC_URI[proc-macro2-1.0.78.sha256sum] =
"e2422ad645d89c99f8f3e6b88a9fdeca7fabeac836b1002371c4367c8f984aae"
-SRC_URI[pyo3-0.20.2.sha256sum] =
"9a89dc7a5850d0e983be1ec2a463a171d20990487c3cfcd68b5363f1ee3d6fe0"
-SRC_URI[pyo3-build-config-0.20.2.sha256sum] =
"07426f0d8fe5a601f26293f300afd1a7b1ed5e78b2a705870c5f30893c5163be"
-SRC_URI[pyo3-ffi-0.20.2.sha256sum] =
"dbb7dec17e17766b46bca4f1a4215a85006b4c2ecde122076c562dd058da6cf1"
-SRC_URI[pyo3-macros-0.20.2.sha256sum] =
"05f738b4e40d50b5711957f142878cfa0f28e054aa0ebdfc3fd137a843f74ed3"
-SRC_URI[pyo3-macros-backend-0.20.2.sha256sum] =
"0fc910d4851847827daf9d6cdd4a823fbdaab5b8818325c5e97a86da79e8881f"
+SRC_URI[pyo3-0.20.3.sha256sum] =
"53bdbb96d49157e65d45cc287af5f32ffadd5f4761438b527b055fb0d4bb8233"
+SRC_URI[pyo3-build-config-0.20.3.sha256sum] =
"deaa5745de3f5231ce10517a1f5dd97d53e5a2fd77aa6b5842292085831d48d7"
+SRC_URI[pyo3-ffi-0.20.3.sha256sum] =
"62b42531d03e08d4ef1f6e85a2ed422eb678b8cd62b762e53891c05faf0d4afa"
+SRC_URI[pyo3-macros-0.20.3.sha256sum] =
"7305c720fa01b8055ec95e484a6eca7a83c841267f0dd5280f0c8b8551d2c158"
+SRC_URI[pyo3-macros-backend-0.20.3.sha256sum] =
"7c7e9b68bb9c3149c5b0cade5d07f953d6d125eb4337723c4ccdb665f1f96185"
SRC_URI[quote-1.0.35.sha256sum] =
"291ec9ab5efd934aaf503a6466c5d5251535d108ee747472c3977cc5acc868ef"
SRC_URI[redox_syscall-0.4.1.sha256sum] =
"4722d768eff46b75989dd134e5c353f0d6296e5aaa3132e776cbdb56be7731aa"
SRC_URI[scopeguard-1.2.0.sha256sum] =
"94143f37725109f92c262ed2cf5e59bce7498c01bcc1502d7b9afe439a4e9f49"
diff --git
a/meta/recipes-devtools/python/python3-cryptography-vectors_42.0.2.bb
b/meta/recipes-devtools/python/python3-cryptography-vectors_42.0.5.bb
similarity index 91%
rename from meta/recipes-devtools/python/python3-cryptography-vectors_42.0.2.bb
[OE-core] [PATCH 0/1] python3-cryptograpy upgrade to 42.0.5
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{-vectors}: 42.0.2 -> 42.0.4"
https://patchwork.yoctoproject.org/project/oe-core/patch/20240228073818.2520528-1-soumya.sa...@windriver.com/
Built on top of current master-next, sans "python3-cryptography: Update pyo3
crate to 0.20.3".
All ptests pass on qemux86-64 for core-image-ptest-python3-cryptography
I will also sanity test ppc64 build, but am sending this now so it can be added
to AB builds.
Tim Orling (1):
python3-cryptography{-vectors}: upgrade to 42.0.5
.../python/python3-cryptography-crates.inc| 22 ++-
...=> python3-cryptography-vectors_42.0.5.bb} | 2 +-
0.2.bb => python3-cryptography_42.0.5.bb} | 2 +-
3 files changed, 14 insertions(+), 12 deletions(-)
rename meta/recipes-devtools/python/{python3-cryptography-vectors_42.0.2.bb =>
python3-cryptography-vectors_42.0.5.bb} (91%)
rename meta/recipes-devtools/python/{python3-cryptography_42.0.2.bb =>
python3-cryptography_42.0.5.bb} (95%)
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196395):
https://lists.openembedded.org/g/openembedded-core/message/196395
Mute This Topic: https://lists.openembedded.org/mt/104626052/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH v2 2/2] python3-cryptography: Update pyo3 crate to 0.20.3
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 64bit atomics. >> >> >> > >> > We could also upgrade to python3-cryptography 42.0.5 >> > https://cryptography.io/en/latest/changelog/#v42-0-5 >> > Do we want to do that at this stage? >> >> upgrade to 42.0.5 will still need this patch regardless >> since it will only be in next release, so update or not is orthogonal >> to this issue. >> >> The pyo3 upgrade was backported to 42.0.5 > https://github.com/pyca/cryptography/compare/42.0.2...42.0.5 > > https://github.com/pyca/cryptography/commit/8e9de309f850a17409da5de39cfcd9296c25ea36 > > Nice I was looking at the trunk alone > >> >> >> >> Signed-off-by: Khem Raj >> >> --- >> >> .../python/python3-cryptography-crates.inc| 22 ++-- >> >> ...m-0.20.2-to-0.20.3-in-src-rust-10462.patch | 105 ++ >> >> .../python/python3-cryptography_42.0.2.bb | 1 + >> >> 3 files changed, 118 insertions(+), 10 deletions(-) >> >> create mode 100644 >> meta/recipes-devtools/python/python3-cryptography/0001-Bump-pyo3-from-0.20.2-to-0.20.3-in-src-rust-10462.patch >> >> >> >> diff --git >> a/meta/recipes-devtools/python/python3-cryptography-crates.inc >> b/meta/recipes-devtools/python/python3-cryptography-crates.inc >> >> index 4714c76bd2b..b26e22b70c3 100644 >> >> --- a/meta/recipes-devtools/python/python3-cryptography-crates.inc >> >> +++ b/meta/recipes-devtools/python/python3-cryptography-crates.inc >> >> @@ -25,12 +25,13 @@ SRC_URI += " \ >> >> crate://crates.io/parking_lot_core/0.9.9 \ >> >> crate://crates.io/pem/3.0.3 \ >> >> crate://crates.io/pkg-config/0.3.29 \ >> >> +crate://crates.io/portable-atomic/1.6.0 \ >> >> crate://crates.io/proc-macro2/1.0.78 \ >> >> -crate://crates.io/pyo3/0.20.2 \ >> >> -crate://crates.io/pyo3-build-config/0.20.2 \ >> >> -crate://crates.io/pyo3-ffi/0.20.2 \ >> >> -crate://crates.io/pyo3-macros/0.20.2 \ >> >> -crate://crates.io/pyo3-macros-backend/0.20.2 \ >> >> +crate://crates.io/pyo3/0.20.3 \ >> >> +crate://crates.io/pyo3-build-config/0.20.3 \ >> >> +crate://crates.io/pyo3-ffi/0.20.3 \ >> >> +crate://crates.io/pyo3-macros/0.20.3 \ >> >> +crate://crates.io/pyo3-macros-backend/0.20.3 \ >> >> crate://crates.io/quote/1.0.35 \ >> >> crate://crates.io/redox_syscall/0.4.1 \ >> >> crate://crates.io/scopeguard/1.2.0 \ >> >> @@ -74,12 +75,13 @@ SRC_URI[parking_lot-0.12.1.sha256sum] = >> "3742b2c103b9f06bc9fff0a37ff4912935851be >> >> SRC_URI[parking_lot_core-0.9.9.sha256sum] = >> "4c42a9226546d68acdd9c0a280d17ce19bfe27a46bf68784e4066115788d008e" >> >> SRC_URI[pem-3.0.3.sha256sum] = >> "1b8fcc794035347fb64beda2d3b462595dd2753e3f268d89c5aae77e8cf2c310" >> >> SRC_URI[pkg-config-0.3.29.sha256sum] = >> "2900ede94e305130c13ddd391e0ab7cbaeb783945ae07a279c268cb05109c6cb" >> >> +SRC_URI[portable-atomic-1.6.0.sha256sum] = >> "7170ef9988bc169ba16dd36a7fa041e5c4cbeb6a35b76d4c03daded371eae7c0" >> >> SRC_URI[proc-macro2-1.0.78.sha256sum] = >> "e2422ad645d89c99f8f3e6b88a9fdeca7fabeac836b1002371c4367c8f984aae" >> >> -SRC_URI[pyo3-0.20.2.sha256sum] = >> "9a89dc7a5850d0e983be1ec2a463a171d20990487c3cfcd68b5363f1ee3d6fe0" >> >> -SRC_URI[pyo3-build-config-0.20.2.sha256sum] = >> "07426f0d8fe5a601f26293f300afd1a7b1ed5e78b2a705870c5f30893c5163be" >> >> -SRC_URI[pyo3-ffi-0.20.2.sha256sum] = >> "dbb7dec17e17766b46bca4f1a4215a85006b4c2ecde122076c562dd058da6cf1" >> >> -SRC_URI[pyo3-macros-0.20.2.sha256sum] = >> "05f738b4e40d50b5711957f142878cfa0f28e054aa0ebdfc3fd137a843f74ed3" >> >> -SRC_URI[pyo3-macros-backend-0.20.2.sha256sum] = >> "0fc910d4851847827daf9d6cdd4a823fbdaab5b8818325c5e97a86da79e8881f" >> >> +SRC_URI[pyo3-0.20.3.sha256sum] = >> "53bdbb96d49157e65d45cc287af5f32ffadd5f4761438b527b055fb0d4bb8233" >> >> +SRC_URI[pyo3-build-config-0.20.3.sha256sum] = >> "deaa5745de3f5231ce10517a1f5dd97d53e5a2fd77aa6b5842292085831d48d7" >> >> +SRC_URI[pyo3-ffi-0.20.3.sha256sum] = >> "62b42531d03e08d4ef1f6e85a2ed422eb678b8cd62b762e53891c05faf0d4afa" >> >> +SRC_URI[pyo3-macros-0.20.3.sha256sum] = >> "7305c720fa01b8055ec95e484a6eca7a83c841267f0dd5280f0c8b8551d2c158" >> >> +SRC_URI[pyo3-macros-backend-0.20.3.sha256sum] = >> "7c7e9b68bb9c3149c5b0cade5d07f953d6d125eb4337723c4ccdb665f1f96185" >> >> SRC_URI[quote-1.0.35.sha256sum] = >> "291ec9ab5efd934aaf503a6466c5d5251535d108ee747472c3977cc5acc868ef" >> >> SRC_URI[redox_syscall-0.4.1.sha256sum] = >> "4722d768eff46b75989dd134e5c353f0d6296e5aaa3132e776cbdb56be7731aa" >> >> SRC_URI[scopeguard-1.2.0.sha256sum] = >> "94143f37725109f92c262ed2cf5e59bce7498c01bcc1502d7b9afe439a4e9f49" >> >> diff --git >> a/meta/recipes-devtools/python/python3-cryptography/0001-Bump-pyo3-from-0.20.2-to-0.20.3-in-src-rust-10462.patch >>
Re: [OE-core][PATCH 1/1] python3-cryptography{-vectors}: 42.0.2 -> 42.0.4
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 and segfault that could occur
> when creating a PKCS#12 bundle. Credit to Alexander-Programming for
> reporting the issue. CVE-2024-26130
> * Fixed ASN.1 encoding for PKCS7/SMIME signed messages. The fields
> SMIMECapabilities and SignatureAlgorithmIdentifier should now be
> correctly encoded according to the definitions in RFC 2633 RFC 3370.
>
> 42.0.3 - 2024-02-15
> * Fixed an initialization issue that caused key loading failures for
> some users.
>
> https://cryptography.io/en/latest/changelog/#v42-0-4
>
> Signed-off-by: Soumya Sambu
> ---
> ...vectors_42.0.2.bb => python3-cryptography-vectors_42.0.4.bb} | 2 +-
> ...n3-cryptography_42.0.2.bb => python3-cryptography_42.0.4.bb} | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
> rename meta/recipes-devtools/python/{
> python3-cryptography-vectors_42.0.2.bb =>
> python3-cryptography-vectors_42.0.4.bb} (91%)
> rename meta/recipes-devtools/python/{python3-cryptography_42.0.2.bb =>
> python3-cryptography_42.0.4.bb} (95%)
>
> diff --git a/meta/recipes-devtools/python/
> python3-cryptography-vectors_42.0.2.bb b/meta/recipes-devtools/python/
> python3-cryptography-vectors_42.0.4.bb
> similarity index 91%
> rename from meta/recipes-devtools/python/
> python3-cryptography-vectors_42.0.2.bb
> rename to meta/recipes-devtools/python/
> python3-cryptography-vectors_42.0.4.bb
> index 94fbc94c55..9500e890f3 100644
> --- a/meta/recipes-devtools/python/python3-cryptography-vectors_42.0.2.bb
> +++ b/meta/recipes-devtools/python/python3-cryptography-vectors_42.0.4.bb
> @@ -9,7 +9,7 @@ LIC_FILES_CHKSUM =
> "file://LICENSE;md5=8c3617db4fb6fae01f1d253ab91511e4 \
> # NOTE: Make sure to keep this recipe at the same version as
> python3-cryptography
> # Upgrade both recipes at the same time
>
> -SRC_URI[sha256sum] =
> "adcdccf5d9ee661a9602ad21d2525f678ba07a6e768ce79835994e208bab0e16"
> +SRC_URI[sha256sum] =
> "d6b707d238a5e2390c3dae7761b997b68c2b8c0723ed24fc13f832bcc8739945"
>
> PYPI_PACKAGE = "cryptography_vectors"
>
> diff --git a/meta/recipes-devtools/python/python3-cryptography_42.0.2.bb
> b/meta/recipes-devtools/python/python3-cryptography_42.0.4.bb
> similarity index 95%
> rename from meta/recipes-devtools/python/python3-cryptography_42.0.2.bb
> rename to meta/recipes-devtools/python/python3-cryptography_42.0.4.bb
> index c21c4d1a03..e864d6ce4f 100644
> --- a/meta/recipes-devtools/python/python3-cryptography_42.0.2.bb
> +++ b/meta/recipes-devtools/python/python3-cryptography_42.0.4.bb
> @@ -8,7 +8,7 @@ LIC_FILES_CHKSUM =
> "file://LICENSE;md5=8c3617db4fb6fae01f1d253ab91511e4 \
> "
> LDSHARED += "-pthread"
>
> -SRC_URI[sha256sum] =
> "e0ec52ba3c7f1b7d813cd52649a5b3ef1fc0d433219dc8c93827c57eab6cf888"
> +SRC_URI[sha256sum] =
> "831a4b37accef30cccd34fcb916a5d7b5be3cbbe27268a02832c3e450aea39cb"
>
> SRC_URI +=
> "file://0001-pyproject.toml-remove-benchmark-disable-option.patch \
> file://check-memfree.py \
> --
> 2.40.0
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196393):
https://lists.openembedded.org/g/openembedded-core/message/196393
Mute This Topic: https://lists.openembedded.org/mt/104619680/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files
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 part of poky. 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 when covering a large number of builds. To mitigate this, we are currently working on an approach to extract the metadata needed to provide debug symbols as part of the bitbake build. This metadata includes the mapping of the GNU build ID to the package holding the debug symbol. The metadata will be treated as another build artifact and can be consumed by a daemon implementing the debuginfod HTTP API to serve debug symbol file requests from the package feed produced by the bitbake build. Initially, we considered implementing the generation of debug metadata directly as part of emit_pkgdata() in package.bbclass (disabled by default). However, we discarded this idea as introducing a configuration option would increase maintenance effort for a feature that would potentially only be enabled in very few builds. Instead, we opted to extend package.bbclass to expose the minimal information needed to reliably identify debug symbol files, which can then be consumed by a packaging hook. Is this extension something that is viable to be merged? We are considering open-sourcing the other parts needed to implement the setup described above, but as those parts are still in the prototyping phase, it will require some more time. [1] https://sourceware.org/elfutils/Debuginfod.html I think this is the kind of direction we've wanted to go in. I'm not sure the patch as it stands is that useful as it just lists files which you could just as easily obtain with a os.walk on the filesystem but in principle I'd be fine with writing some extra data during do_package or do_packagedata which saves the buildid mappings. In one of my first iterations I placed the build ID to file mapping into the "extended" section of "pkgdata". We'd then consume this data after the build has finished to produce the debug info metadata database which contains the mapping from build ID to debug symbol file and the package containing the file. If this sounds sane to you I can clean up that version and share it here. So yes, in principle the idea sounds good but obviously the final decision would depend upon the patches. 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 ID extraction on the debug packages of our medium sized kirkstone based distro (see my reply to Alex for more details). Sequentially extracting build IDs from around 8000 files took around 1:30 minutes on my machine. While I wouldn't call this excessive, I am also not sure whether this is too much overhead given that I only expect this data to be used in some deployments. Br, Philip -- Philip Lorenz BMW Car IT GmbH, Software-Plattform, -Integration Connected Company, Lise-Meitner-Straße 14, 89081 Ulm - BMW Car IT GmbH Management: Chris Brandt and Michael Böttrich Domicile and Court of Registry: München HRB 134810 - -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196392): https://lists.openembedded.org/g/openembedded-core/message/196392 Mute This Topic: https://lists.openembedded.org/mt/104619206/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH v2 2/2] python3-cryptography: Update pyo3 crate to 0.20.3
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-cryptography 42.0.5 > > https://cryptography.io/en/latest/changelog/#v42-0-5 > > Do we want to do that at this stage? > > upgrade to 42.0.5 will still need this patch regardless > since it will only be in next release, so update or not is orthogonal > to this issue. > > The pyo3 upgrade was backported to 42.0.5 https://github.com/pyca/cryptography/compare/42.0.2...42.0.5 https://github.com/pyca/cryptography/commit/8e9de309f850a17409da5de39cfcd9296c25ea36 > > > >> > >> Signed-off-by: Khem Raj > >> --- > >> .../python/python3-cryptography-crates.inc| 22 ++-- > >> ...m-0.20.2-to-0.20.3-in-src-rust-10462.patch | 105 ++ > >> .../python/python3-cryptography_42.0.2.bb | 1 + > >> 3 files changed, 118 insertions(+), 10 deletions(-) > >> create mode 100644 > meta/recipes-devtools/python/python3-cryptography/0001-Bump-pyo3-from-0.20.2-to-0.20.3-in-src-rust-10462.patch > >> > >> diff --git > a/meta/recipes-devtools/python/python3-cryptography-crates.inc > b/meta/recipes-devtools/python/python3-cryptography-crates.inc > >> index 4714c76bd2b..b26e22b70c3 100644 > >> --- a/meta/recipes-devtools/python/python3-cryptography-crates.inc > >> +++ b/meta/recipes-devtools/python/python3-cryptography-crates.inc > >> @@ -25,12 +25,13 @@ SRC_URI += " \ > >> crate://crates.io/parking_lot_core/0.9.9 \ > >> crate://crates.io/pem/3.0.3 \ > >> crate://crates.io/pkg-config/0.3.29 \ > >> +crate://crates.io/portable-atomic/1.6.0 \ > >> crate://crates.io/proc-macro2/1.0.78 \ > >> -crate://crates.io/pyo3/0.20.2 \ > >> -crate://crates.io/pyo3-build-config/0.20.2 \ > >> -crate://crates.io/pyo3-ffi/0.20.2 \ > >> -crate://crates.io/pyo3-macros/0.20.2 \ > >> -crate://crates.io/pyo3-macros-backend/0.20.2 \ > >> +crate://crates.io/pyo3/0.20.3 \ > >> +crate://crates.io/pyo3-build-config/0.20.3 \ > >> +crate://crates.io/pyo3-ffi/0.20.3 \ > >> +crate://crates.io/pyo3-macros/0.20.3 \ > >> +crate://crates.io/pyo3-macros-backend/0.20.3 \ > >> crate://crates.io/quote/1.0.35 \ > >> crate://crates.io/redox_syscall/0.4.1 \ > >> crate://crates.io/scopeguard/1.2.0 \ > >> @@ -74,12 +75,13 @@ SRC_URI[parking_lot-0.12.1.sha256sum] = > "3742b2c103b9f06bc9fff0a37ff4912935851be > >> SRC_URI[parking_lot_core-0.9.9.sha256sum] = > "4c42a9226546d68acdd9c0a280d17ce19bfe27a46bf68784e4066115788d008e" > >> SRC_URI[pem-3.0.3.sha256sum] = > "1b8fcc794035347fb64beda2d3b462595dd2753e3f268d89c5aae77e8cf2c310" > >> SRC_URI[pkg-config-0.3.29.sha256sum] = > "2900ede94e305130c13ddd391e0ab7cbaeb783945ae07a279c268cb05109c6cb" > >> +SRC_URI[portable-atomic-1.6.0.sha256sum] = > "7170ef9988bc169ba16dd36a7fa041e5c4cbeb6a35b76d4c03daded371eae7c0" > >> SRC_URI[proc-macro2-1.0.78.sha256sum] = > "e2422ad645d89c99f8f3e6b88a9fdeca7fabeac836b1002371c4367c8f984aae" > >> -SRC_URI[pyo3-0.20.2.sha256sum] = > "9a89dc7a5850d0e983be1ec2a463a171d20990487c3cfcd68b5363f1ee3d6fe0" > >> -SRC_URI[pyo3-build-config-0.20.2.sha256sum] = > "07426f0d8fe5a601f26293f300afd1a7b1ed5e78b2a705870c5f30893c5163be" > >> -SRC_URI[pyo3-ffi-0.20.2.sha256sum] = > "dbb7dec17e17766b46bca4f1a4215a85006b4c2ecde122076c562dd058da6cf1" > >> -SRC_URI[pyo3-macros-0.20.2.sha256sum] = > "05f738b4e40d50b5711957f142878cfa0f28e054aa0ebdfc3fd137a843f74ed3" > >> -SRC_URI[pyo3-macros-backend-0.20.2.sha256sum] = > "0fc910d4851847827daf9d6cdd4a823fbdaab5b8818325c5e97a86da79e8881f" > >> +SRC_URI[pyo3-0.20.3.sha256sum] = > "53bdbb96d49157e65d45cc287af5f32ffadd5f4761438b527b055fb0d4bb8233" > >> +SRC_URI[pyo3-build-config-0.20.3.sha256sum] = > "deaa5745de3f5231ce10517a1f5dd97d53e5a2fd77aa6b5842292085831d48d7" > >> +SRC_URI[pyo3-ffi-0.20.3.sha256sum] = > "62b42531d03e08d4ef1f6e85a2ed422eb678b8cd62b762e53891c05faf0d4afa" > >> +SRC_URI[pyo3-macros-0.20.3.sha256sum] = > "7305c720fa01b8055ec95e484a6eca7a83c841267f0dd5280f0c8b8551d2c158" > >> +SRC_URI[pyo3-macros-backend-0.20.3.sha256sum] = > "7c7e9b68bb9c3149c5b0cade5d07f953d6d125eb4337723c4ccdb665f1f96185" > >> SRC_URI[quote-1.0.35.sha256sum] = > "291ec9ab5efd934aaf503a6466c5d5251535d108ee747472c3977cc5acc868ef" > >> SRC_URI[redox_syscall-0.4.1.sha256sum] = > "4722d768eff46b75989dd134e5c353f0d6296e5aaa3132e776cbdb56be7731aa" > >> SRC_URI[scopeguard-1.2.0.sha256sum] = > "94143f37725109f92c262ed2cf5e59bce7498c01bcc1502d7b9afe439a4e9f49" > >> diff --git > a/meta/recipes-devtools/python/python3-cryptography/0001-Bump-pyo3-from-0.20.2-to-0.20.3-in-src-rust-10462.patch > b/meta/recipes-devtools/python/python3-cryptography/0001-Bump-pyo3-from-0.20.2-to-0.20.3-in-src-rust-10462.patch > >> new file mode 100644 > >> index 000..33dd7ae5d5a > >> --- /dev/null > >> +++ >
Re: [OE-core] [kirkstone][PATCH V2] nghttp2: fix CVE-2023-44487
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 group. View/Reply Online (#196390): https://lists.openembedded.org/g/openembedded-core/message/196390 Mute This Topic: https://lists.openembedded.org/mt/104049487/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files
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 when covering a large number of builds. Is it possible to see numbers behind this claim? When there is a proposal to increase code complexity, that needs to be justified in a way that can be locally observed. Let me provide some numbers based on both an internal medium-sized build based on kirkstone as well as a core-image-minimal build based on master. Kirkstone: find -name "*.ipk" | wc 8415 8415 615076 du -h -c 3.5G total time /bin/sh -c 'for f in */*.ipk; do ar p $f data.tar.xz | tar -tJ > /dev/null; done' real 5m13.629s user 4m56.653s sys 1m41.578s master (core-image-minimal): find -name "*.ipk" | wc 4553 4553 287890 du -h -c 2.1G total time /bin/sh -c 'for f in */*.ipk; do ar p $f data.tar.zst | tar --zstd -t > /dev/null; done' real 1m2.521s user 0m40.876s sys 1m8.232s Exact figures of course vary and this can be further optimized by introducing parallelism. However, given that the artifacts are available uncompressed during packaging and the packaging step is also the one responsible for splitting out the debug symbols so limiting build ID extraction to the files that are known to contain debug symbols also is an efficiency win (and one also avoid implementing any kind of heuristics to determine which files actually contain the debug symbols). Is this extension something that is viable to be merged? We are considering open-sourcing the other parts needed to implement the setup described above, but as those parts are still in the prototyping phase, it will require some more time. The patch looks okay, but it's not useful without those other parts, so you need to get them ready and submit the whole set. I'll answer this as part of my reply to Richard. I'd be more than happy to share the tooling we use to produce the build ID metadata and this was more an issue of where to actually place it. The only thing that is not yet in a state ready for public consumption is our daemon that consumes this metadata and then transparently fulfills any incoming debuginfo requests by retrieving the debug file from the corresponding package. Br, Philip -- Philip Lorenz BMW Car IT GmbH, Software-Plattform, -Integration Connected Company, Lise-Meitner-Straße 14, 89081 Ulm - BMW Car IT GmbH Management: Chris Brandt and Michael Böttrich Domicile and Court of Registry: München HRB 134810 - -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196389): https://lists.openembedded.org/g/openembedded-core/message/196389 Mute This Topic: https://lists.openembedded.org/mt/104619206/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH] bash: improve reproducibility
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.inc | 21 +
> 1 file changed, 21 insertions(+)
>
> diff --git a/meta/recipes-extended/bash/bash.inc
> b/meta/recipes-extended/bash/bash.inc
> index 2c3e605511..c8275c0443 100644
> --- a/meta/recipes-extended/bash/bash.inc
> +++ b/meta/recipes-extended/bash/bash.inc
> @@ -74,6 +74,7 @@ do_install:append () {
> mv ${D}${bindir}/bash ${D}${base_bindir}
> fi
> }
> +
> do_install:append:class-target () {
> # Clean buildhost references in bashbug
> sed -i -e "s,--sysroot=${STAGING_DIR_TARGET},,g" \
> @@ -93,6 +94,26 @@ do_install:append:class-target () {
> ${D}${libdir}/bash/Makefile.inc
> }
>
> +
> +do_install:append:class-nativesdk () {
> + # Clean buildhost references in bashbug
> + sed -i -e "s,--sysroot=${STAGING_DIR_TARGET},,g" \
> + -e "s,-I${WORKDIR}/\S* ,,g" \
> + -e 's|${DEBUG_PREFIX_MAP}||g' \
> + ${D}${bindir}/bashbug
> +
> + # Clean buildhost references in bash.pc
> + sed -i -e "s,--sysroot=${STAGING_DIR_TARGET},,g" \
> +${D}${libdir}/pkgconfig/bash.pc
> +
> + # Clean buildhost references in Makefile.inc
> + sed -i -e "s,--sysroot=${STAGING_DIR_TARGET},,g" \
> + -e 's|${DEBUG_PREFIX_MAP}||g' \
> + -e 's:${HOSTTOOLS_DIR}/::g' \
> + -e 's:${BASE_WORKDIR}/${MULTIMACH_TARGET_SYS}::g' \
> + ${D}${libdir}/bash/Makefile.inc
> +}
> +
> do_install_ptest () {
> make INSTALL_TEST_DIR=${D}${PTEST_PATH}/tests install-test
> cp ${B}/Makefile ${D}${PTEST_PATH}
> --
> 2.33.0
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196388):
https://lists.openembedded.org/g/openembedded-core/message/196388
Mute This Topic: https://lists.openembedded.org/mt/104624288/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] bash: improve reproducibility
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
index 2c3e605511..c8275c0443 100644
--- a/meta/recipes-extended/bash/bash.inc
+++ b/meta/recipes-extended/bash/bash.inc
@@ -74,6 +74,7 @@ do_install:append () {
mv ${D}${bindir}/bash ${D}${base_bindir}
fi
}
+
do_install:append:class-target () {
# Clean buildhost references in bashbug
sed -i -e "s,--sysroot=${STAGING_DIR_TARGET},,g" \
@@ -93,6 +94,26 @@ do_install:append:class-target () {
${D}${libdir}/bash/Makefile.inc
}
+
+do_install:append:class-nativesdk () {
+ # Clean buildhost references in bashbug
+ sed -i -e "s,--sysroot=${STAGING_DIR_TARGET},,g" \
+ -e "s,-I${WORKDIR}/\S* ,,g" \
+ -e 's|${DEBUG_PREFIX_MAP}||g' \
+ ${D}${bindir}/bashbug
+
+ # Clean buildhost references in bash.pc
+ sed -i -e "s,--sysroot=${STAGING_DIR_TARGET},,g" \
+${D}${libdir}/pkgconfig/bash.pc
+
+ # Clean buildhost references in Makefile.inc
+ sed -i -e "s,--sysroot=${STAGING_DIR_TARGET},,g" \
+ -e 's|${DEBUG_PREFIX_MAP}||g' \
+ -e 's:${HOSTTOOLS_DIR}/::g' \
+ -e 's:${BASE_WORKDIR}/${MULTIMACH_TARGET_SYS}::g' \
+ ${D}${libdir}/bash/Makefile.inc
+}
+
do_install_ptest () {
make INSTALL_TEST_DIR=${D}${PTEST_PATH}/tests install-test
cp ${B}/Makefile ${D}${PTEST_PATH}
--
2.33.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196387):
https://lists.openembedded.org/g/openembedded-core/message/196387
Mute This Topic: https://lists.openembedded.org/mt/104624288/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] Patchtest results for [PATCH] gstreamer1.0: skip a test that is known to be flaky
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 Inappropriate, but no reason was provided (test_patch.TestPatch.test_upstream_status_presence_format) PASS: pretest src uri left files (test_metadata.TestMetadata.pretest_src_uri_left_files) PASS: test CVE check ignore (test_metadata.TestMetadata.test_cve_check_ignore) PASS: test CVE tag format (test_patch.TestPatch.test_cve_tag_format) PASS: test Signed-off-by presence (test_mbox.TestMbox.test_signed_off_by_presence) PASS: test Signed-off-by presence (test_patch.TestPatch.test_signed_off_by_presence) PASS: test author valid (test_mbox.TestMbox.test_author_valid) PASS: test bugzilla entry format (test_mbox.TestMbox.test_bugzilla_entry_format) PASS: test commit message presence (test_mbox.TestMbox.test_commit_message_presence) PASS: test lic files chksum modified not mentioned (test_metadata.TestMetadata.test_lic_files_chksum_modified_not_mentioned) PASS: test max line length (test_metadata.TestMetadata.test_max_line_length) PASS: test mbox format (test_mbox.TestMbox.test_mbox_format) PASS: test non-AUH upgrade (test_mbox.TestMbox.test_non_auh_upgrade) PASS: test shortlog format (test_mbox.TestMbox.test_shortlog_format) PASS: test shortlog length (test_mbox.TestMbox.test_shortlog_length) PASS: test src uri left files (test_metadata.TestMetadata.test_src_uri_left_files) SKIP: pretest pylint: No python related patches, skipping test (test_python_pylint.PyLint.pretest_pylint) SKIP: test lic files chksum presence: No added recipes, skipping test (test_metadata.TestMetadata.test_lic_files_chksum_presence) SKIP: test license presence: No added recipes, skipping test (test_metadata.TestMetadata.test_license_presence) SKIP: test pylint: No python related patches, skipping test (test_python_pylint.PyLint.test_pylint) SKIP: test series merge on head: Merge test is disabled for now (test_mbox.TestMbox.test_series_merge_on_head) SKIP: test summary presence: No added recipes, skipping test (test_metadata.TestMetadata.test_summary_presence) SKIP: test target mailing list: Series merged, no reason to check other mailing lists (test_mbox.TestMbox.test_target_mailing_list) --- Please address the issues identified and submit a new revision of the patch, or alternatively, reply to this email with an explanation of why the patch should be accepted. If you believe these results are due to an error in patchtest, please submit a bug at https://bugzilla.yoctoproject.org/ (use the 'Patchtest' category under 'Yocto Project Subprojects'). For more information on specific failures, see: https://wiki.yoctoproject.org/wiki/Patchtest. Thank you! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196386): https://lists.openembedded.org/g/openembedded-core/message/196386 Mute This Topic: https://lists.openembedded.org/mt/104622896/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 04/48] dnf: upgrade 4.18.2 -> 4.19.0
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 rawhide (RhBug:2261066)
> -automatic: Use add_security_filters, not _update_security_filters
>
> Signed-off-by: Wang Mingyu
> ---
> meta/recipes-devtools/dnf/{dnf_4.18.2.bb => dnf_4.19.0.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta/recipes-devtools/dnf/{dnf_4.18.2.bb => dnf_4.19.0.bb}
> (98%)
>
> diff --git a/meta/recipes-devtools/dnf/dnf_4.18.2.bb b/meta/recipes-
> devtools/dnf/dnf_4.19.0.bb
> similarity index 98%
> rename from meta/recipes-devtools/dnf/dnf_4.18.2.bb
> rename to meta/recipes-devtools/dnf/dnf_4.19.0.bb
> index dc0c18be5e..784d7a94b3 100644
> --- a/meta/recipes-devtools/dnf/dnf_4.18.2.bb
> +++ b/meta/recipes-devtools/dnf/dnf_4.19.0.bb
> @@ -19,7 +19,7 @@ SRC_URI = "git://github.com/rpm-software-
> management/dnf.git;branch=master;protoc
>
> SRC_URI:append:class-native =
> "file://0001-dnf-write-the-log-lock-to-root.patch"
>
> -SRCREV = "1c43d0999178d492381ad0b43917ffd9c74016f8"
> +SRCREV = "566a61f9d8a2830ac6dcc3a94c59224cef1c3d03"
> UPSTREAM_CHECK_GITTAGREGEX = "(?P\d+(\.\d+)+)"
>
> S = "${WORKDIR}/git"
>
This broke in image and sdk construction:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/6620
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196385):
https://lists.openembedded.org/g/openembedded-core/message/196385
Mute This Topic: https://lists.openembedded.org/mt/104619602/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [PATCH] gstreamer1.0: skip a test that is known to be flaky
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] https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/410
Signed-off-by: Ross Burton
---
.../gstreamer1.0/skip-aggregator-test.patch | 35 +++
.../gstreamer/gstreamer1.0_1.22.10.bb | 1 +
2 files changed, 36 insertions(+)
create mode 100644
meta/recipes-multimedia/gstreamer/gstreamer1.0/skip-aggregator-test.patch
diff --git
a/meta/recipes-multimedia/gstreamer/gstreamer1.0/skip-aggregator-test.patch
b/meta/recipes-multimedia/gstreamer/gstreamer1.0/skip-aggregator-test.patch
new file mode 100644
index 000..81337512fdd
--- /dev/null
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0/skip-aggregator-test.patch
@@ -0,0 +1,35 @@
+From 9b72aa7cdbc2a81cffc6f855933afe90c81046d5 Mon Sep 17 00:00:00 2001
+From: Ross Burton
+Date: Wed, 28 Feb 2024 12:40:34 +
+Subject: [PATCH] Skip aggregator test
+
+This test case is known to be flaky upstream[1] and often fails on the
+autobuilder[2], so skip it until this has been resolved upstream.
+
+[1] https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/410
+[2] https://bugzilla.yoctoproject.org/show_bug.cgi?id=15054
+
+Upstream-Status: Inappropriate
+Signed-off-by: Ross Burton
+---
+ tests/check/libs/aggregator.c | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/tests/check/libs/aggregator.c b/tests/check/libs/aggregator.c
+index 1f2c5b4..27b3ac7 100644
+--- a/tests/check/libs/aggregator.c
b/tests/check/libs/aggregator.c
+@@ -1475,7 +1475,9 @@ gst_aggregator_suite (void)
+ tcase_add_test (general, test_flushing_seek);
+ tcase_add_test (general, test_infinite_seek);
+ tcase_add_test (general, test_infinite_seek_50_src);
+- tcase_add_test (general, test_infinite_seek_50_src_live);
++ // This test case is known to be flaky, remove it until resolved:
++ // https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/410
++ // tcase_add_test (general, test_infinite_seek_50_src_live);
+ tcase_add_test (general, test_linear_pipeline);
+ tcase_add_test (general, test_two_src_pipeline);
+ tcase_add_test (general, test_timeout_pipeline);
+--
+2.34.1
+
diff --git a/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.22.10.bb
b/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.22.10.bb
index 0c944e9e110..c16f0de3b72 100644
--- a/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.22.10.bb
+++ b/meta/recipes-multimedia/gstreamer/gstreamer1.0_1.22.10.bb
@@ -21,6 +21,7 @@ SRC_URI =
"https://gstreamer.freedesktop.org/src/gstreamer/gstreamer-${PV}.tar.x
file://0002-tests-add-support-for-install-the-tests.patch \
file://0003-tests-use-a-dictionaries-for-environment.patch \
file://0004-tests-add-helper-script-to-run-the-installed_tests.patch \
+ file://skip-aggregator-test.patch \
"
SRC_URI[sha256sum] =
"969aaef396f252ce925132a4be2aa004e0320f5c1baf0acaaae09c544a6759f4"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196384):
https://lists.openembedded.org/g/openembedded-core/message/196384
Mute This Topic: https://lists.openembedded.org/mt/104622607/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [RFC OE-core][PATCH 3/3] goarch: disable dynamic linking globally
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, >> > > >> > > I would like to ask if this patchset could be exercised in the >> > > autobuilder? >> > > I only got it working yesterday and today I'm going to do a more >> > > exhaustive test. >> > > This is still missing the update to 1.22, which I'll do later, but >> > > testing this would be a good help. >> > >> > I did put this in for testing. The build is still running but so far >> > there were two issues: >> > >> > >> https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/6466/steps/14/logs/stdio >> > >> > from oe-selftest -r gotoolchain.oeGoToolchainSelfTest.test_go_dep_build >> > > I have see of this also in my local builds in my distro and there are some > reports upstream > https://github.com/golang/go/issues/61928 > I believe this one is expected with the update but I am still doing my > local tests. > I have fixed something like this in my distro so I will fix it also in my next and final submission. Jose > >> > >> > and meta-clang: >> > >> > https://autobuilder.yoctoproject.org/typhoon/#/builders/142/builds/39 >> > >> > meta-virt did pass our testing but I've copied Bruce so he's aware of >> > this and can comment. Copying Khem for meta-clang too. >> > > For meta-clang maybe we can switch to gcc to build the go-helloworld > > >> >> I'm running into some golang issues linking with my latest updates to >> meta-virt . >> >> I'll apply these locally and see if they help, make things worse or have >> no impact on my upcoming recipe bumps for m-virt. >> > > I am testing mostly docker and everything seems fine so far. > > Jose > > >> >> Bruce >> >> >> > >> > Cheers, >> > >> > Richard >> >> >> >> -- >> - Thou shalt not follow the NULL pointer, for chaos and madness await >> thee at its end >> - "Use the force Harry" - Gandalf, Star Trek II >> > > > -- > Best regards, > > José Quaresma > > > > -- Best regards, José Quaresma -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196383): https://lists.openembedded.org/g/openembedded-core/message/196383 Mute This Topic: https://lists.openembedded.org/mt/104600118/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [RFC OE-core][PATCH 3/3] goarch: disable dynamic linking globally
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 the overwall virtualization stack we use and everything seems fine so far. If no issues come in, I intend to submit the final version today or tomorrow at the latest. > P.S. > Is this runtime error OE specific? Is it caused by some OE specific patch? > I don't know the reason for the runtime error yet. When I start I suspected it could be due to separate-host-and-target-builds patch https://git.openembedded.org/openembedded-core/tree/meta/recipes-devtools/go/go/0005-cmd-dist-separate-host-and-target-builds.patch?id=44f81b6239f0f08877ccd6507c2a81f3650f193b After several unsuccessful attempts, I was going to use gdb to debug the target. I decided to disable the dynamic linking because it would make it easier for me with the symbols and I would have just one binary. After that, when I was going to run gdb on the target everything started working without any issue. Jose > Regards, > Qi > > On 2/27/24 18:07, Jose Quaresma wrote: > > 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 can update and > > leave the version 1.20 for the next LTS 5.0 since we are already quite > > behind on the version available upstream which already has the 1.22 > available. > > > > Signed-off-by: Jose Quaresma > > --- > > meta/classes-recipe/goarch.bbclass | 14 +++--- > > 1 file changed, 7 insertions(+), 7 deletions(-) > > > > diff --git a/meta/classes-recipe/goarch.bbclass > b/meta/classes-recipe/goarch.bbclass > > index 1ebe03864f..6899ec28e4 100644 > > --- a/meta/classes-recipe/goarch.bbclass > > +++ b/meta/classes-recipe/goarch.bbclass > > @@ -38,13 +38,13 @@ BASE_GOARM:armv5 = '5' > > # Go supports dynamic linking on a limited set of architectures. > > # See the supportsDynlink function in > go/src/cmd/compile/internal/gc/main.go > > GO_DYNLINK = "" > > -GO_DYNLINK:arm ?= "1" > > -GO_DYNLINK:aarch64 ?= "1" > > -GO_DYNLINK:x86 ?= "1" > > -GO_DYNLINK:x86-64 ?= "1" > > -GO_DYNLINK:powerpc64 ?= "1" > > -GO_DYNLINK:powerpc64le ?= "1" > > -GO_DYNLINK:class-native ?= "" > > +GO_DYNLINK:arm = "" > > +GO_DYNLINK:aarch64 = "" > > +GO_DYNLINK:x86 = "" > > +GO_DYNLINK:x86-64 = "" > > +GO_DYNLINK:powerpc64 = "" > > +GO_DYNLINK:powerpc64le = "" > > +GO_DYNLINK:class-native = "" > > GO_DYNLINK:class-nativesdk = "" > > > > # define here because everybody inherits this class > > > > > > > > -- Best regards, José Quaresma -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196382): https://lists.openembedded.org/g/openembedded-core/message/196382 Mute This Topic: https://lists.openembedded.org/mt/104600087/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH 01/48] bash-completion: upgrade 2.11 -> 2.12.0
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 unmodified upstream license file
>
> Changelog:
> https://github.com/scop/bash-completion/releases/tag/2.12.0
>
> Signed-off-by: Wang Mingyu
> ---
> .../{bash-completion_2.11.bb => bash-completion_2.12.0.bb} | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
> rename meta/recipes-support/bash-completion/{bash-completion_2.11.bb =>
> bash-completion_2.12.0.bb} (83%)
>
> diff --git a/meta/recipes-support/bash-completion/bash-completion_2.11.bb
> b/meta/recipes-support/bash-completion/bash-completion_2.12.0.bb
> similarity index 83%
> rename from meta/recipes-support/bash-completion/bash-completion_2.11.bb
> rename to meta/recipes-support/bash-completion/bash-completion_2.12.0.bb
> index 19bc81619f..66f65f565c 100644
> --- a/meta/recipes-support/bash-completion/bash-completion_2.11.bb
> +++ b/meta/recipes-support/bash-completion/bash-completion_2.12.0.bb
> @@ -8,14 +8,13 @@ HOMEPAGE = "https://github.com/scop/bash-completion;
> BUGTRACKER = "https://github.com/scop/bash-completion/issues;
>
> LICENSE = "GPL-2.0-only"
> -LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>
> SECTION = "console/utils"
>
> SRC_URI = "${GITHUB_BASE_URI}/download/${PV}/${BPN}-${PV}.tar.xz"
>
> -SRC_URI[md5sum] = "2514c6772d0de6254758b98c53f91861"
> -SRC_URI[sha256sum] =
> "73a8894bad94dee83ab468fa09f628daffd567e8bef1a24277f1e9a0daf911ac"
> +SRC_URI[sha256sum] =
> "3eb05b1783c339ef59ed576afb0f678fa4ef49a6de8a696397df3148f8345af9"
> GITHUB_BASE_URI = "https://github.com/scop/bash-completion/releases;
>
> PARALLEL_MAKE = ""
> --
> 2.34.1
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196381):
https://lists.openembedded.org/g/openembedded-core/message/196381
Mute This Topic: https://lists.openembedded.org/mt/104619601/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH V5] systemd: fix a dead link under /var/log
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.logs" during
> boot,
>
> and ${datadir}/doc/systemd/README.logs is in package systemd-doc. So there
> will be dead link when systemd-doc is not installed.
>
> So that's why I create another legacy-doc.conf packaged into systemd-doc
Then legacy.conf and README.logs should be placed into the same
package. I would suggest that README.logs just goes into main systemd
package. (the other option is placing legacy.conf into systemd-doc,
but that file is not doc-specific, and should stay in systemd package,
especially if more entries are added to it).
> 2.
>
> The symlink in legacy.conf use relative path. but for oe, when
> VOLATILE_LOG_DIR is true, /var/log is a link to /var/volatile/log, so
>
> /var/log/README need link to ../../../usr/share/doc/systemd/README.logs,
>
> while VOLATILE_LOG_DIR is false, /var/log is a dir, so /var/log/README
>
> need link to ../../usr/share/doc/systemd/README.logs.
>
> After change it to absolute path, checking of VOLATILE_LOG_DIR is not needed.
That's ok, but can you make fixing the path to an absolute one a
separate, second commit then?
Thanks,
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196380):
https://lists.openembedded.org/g/openembedded-core/message/196380
Mute This Topic: https://lists.openembedded.org/mt/104598170/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core][PATCH 1/2] bash: add locale alias for ja_JP shiftjis in run-ptest
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: > > ja_JP.SJIS ja_JP.SHIFT_JIS ja_JP.shiftjis japanese.sjis Hello Chen, I need to note that we specifically exclude bash from ptests, and this is the reason: https://git.yoctoproject.org/poky/commit/?id=2758f6d0337ec84c9143546bc65a80559e8d7808 As a result, bash ptest would keep regressing in various ways, simply because it's not executed, and I would suggest that you either first fix these failures, so we can restore bash in meta/conf/distro/include/ptests-packagelists.inc, or drop bash from your own testing. Is there a particular reason you need to run those tests? Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196379): https://lists.openembedded.org/g/openembedded-core/message/196379 Mute This Topic: https://lists.openembedded.org/mt/104599698/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH V6] rxvt-unicode: Fix installing of terminfo
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 need to make it an oe specific patch.
>
>
> upstream said that to it is better to use target tic to generate the terminfo
> to make sure ncurses in the
>
> target environment can get the correct terminfo. That's why I changed to use
> target tic. but we do will met
>
> "some targets don't support usermode" problem.
>
> So what's your suggestion about this? use V4 patch?
I would suggest this:
- recipe needs to depend on ncurses-native, otherwise we have a
floating dependency on tic executable
- drop the patch, and instead just add a manual tic invocation into
do_install:append () that places the output into correct directory in
${D}. As far as I understand, what doc/Makefile does is harmless, but
you can additionally set environment variable TIC to : or
/usr/bin/true as suggested by upstream to avoid that happening.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196378):
https://lists.openembedded.org/g/openembedded-core/message/196378
Mute This Topic: https://lists.openembedded.org/mt/104598938/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [RFC PATCH 0/1] package.bbclass: Expose list of split out debug files
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 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 when covering a large > number of builds. > > To mitigate this, we are currently working on an approach to extract the > metadata needed to provide debug symbols as part of the bitbake build. > This metadata includes the mapping of the GNU build ID to the package > holding the debug symbol. The metadata will be treated as another build > artifact and can be consumed by a daemon implementing the debuginfod > HTTP API to serve debug symbol file requests from the package feed > produced by the bitbake build. > > Initially, we considered implementing the generation of debug metadata > directly as part of emit_pkgdata() in package.bbclass (disabled by > default). However, we discarded this idea as introducing a configuration > option would increase maintenance effort for a feature that would > potentially only be enabled in very few builds. Instead, we opted to > extend package.bbclass to expose the minimal information needed to > reliably identify debug symbol files, which can then be consumed by a > packaging hook. > > Is this extension something that is viable to be merged? We are > considering open-sourcing the other parts needed to implement the setup > described above, but as those parts are still in the prototyping phase, > it will require some more time. > > [1] https://sourceware.org/elfutils/Debuginfod.html I think this is the kind of direction we've wanted to go in. I'm not sure the patch as it stands is that useful as it just lists files which you could just as easily obtain with a os.walk on the filesystem but in principle I'd be fine with writing some extra data during do_package or do_packagedata which saves the buildid mappings. So yes, in principle the idea sounds good but obviously the final decision would depend upon the patches. 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. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196377): https://lists.openembedded.org/g/openembedded-core/message/196377 Mute This Topic: https://lists.openembedded.org/mt/104619206/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
