[OE-core] [PATCH] libsdl2: Add libunwind-native to the libsdl2-native DEPENDS
This fixes this CMake configuration error:
| -- Checking for one of the modules 'libunwind'
| CMake Error at
[...]/build/tmp/work/x86_64-linux/libsdl2-native/2.0.20-r0/recipe-sysroot-native/usr/share/cmake-3.22/Modules/FindPkgConfig.cmake:890
(message):
| None of the required 'libunwind' found
| Call Stack (most recent call first):
| CMakeLists.txt:1367 (pkg_search_module)
This error happens even if libunwind is installed complete with its C
headers and development .so files (in Ubuntu, this means libunwind-dev
is installed).
Signed-off-by: Carlos Rafael Giani
---
meta/recipes-graphics/libsdl2/libsdl2_2.0.20.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.20.bb
b/meta/recipes-graphics/libsdl2/libsdl2_2.0.20.bb
index 90724ab8b7..802efba980 100644
--- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.20.bb
+++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.20.bb
@@ -27,6 +27,8 @@ SRC_URI[sha256sum] =
"c56aba1d7b5b0e7e999e4a7698c70b63a3394ff9704b5f6e1c57e0c16f
inherit cmake lib_package binconfig-disabled pkgconfig
+DEPENDS:class-native += "libunwind-native"
+
BINCONFIG = "${bindir}/sdl2-config"
CVE_PRODUCT = "simple_directmedia_layer sdl"
--
2.32.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162710):
https://lists.openembedded.org/g/openembedded-core/message/162710
Mute This Topic: https://lists.openembedded.org/mt/89544908/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] libsdl2: Fix build when libunwind is not used
libunwind is installed on the host, complete with its -dev package. OE
still does not find it.
I'll submit a patch that adds libunwind-native to the native DEPENDS.
On 16.02.22 18:30, Khem Raj wrote:
On Wed, Feb 16, 2022 at 1:58 AM Carlos Rafael Giani via
lists.openembedded.org
wrote:
"MACHINE=qemux86-64 bitbake libsdl2-native" still fails with a similar error:
| CMake Error at
/home/test/yocto-master/poky/build/tmp/work/x86_64-linux/libsdl2-native/2.0.20-r0/recipe-sysroot-native/usr/share/cmake-3.22/Modules/FindPkgConfig.cmake:890
(message):
| None of the required 'libunwind' found
This is triggered by the "pkg_search_module(UNWIND REQUIRED libunwind)" line
right above the one that is modified by this patch.
Any idea what is going on?
I think its looking for libunwind on your build host.
On 07.01.22 21:34, Alexander Kanavin wrote:
Thanks :)
Alex
On Fri, 7 Jan 2022 at 20:23, Khem Raj wrote:
clang provides libunwind.h and cmake adds a check to
find libunwind when this header is detected, which was
not the case with automake. The check however is expecting
specific unwinder implementation which provides libunwind-generic
solib, this is not a standard library that all implementations
will provide, therefore make this check optional.
Signed-off-by: Khem Raj
Cc: Andreas Müller
---
v2: Udate patch status to submitted
.../libsdl2/optional-libunwind-generic.patch | 18 ++
.../recipes-graphics/libsdl2/libsdl2_2.0.18.bb | 1 +
2 files changed, 19 insertions(+)
create mode 100644
meta/recipes-graphics/libsdl2/libsdl2/optional-libunwind-generic.patch
diff --git
a/meta/recipes-graphics/libsdl2/libsdl2/optional-libunwind-generic.patch
b/meta/recipes-graphics/libsdl2/libsdl2/optional-libunwind-generic.patch
new file mode 100644
index 000..757b99a5f68
--- /dev/null
+++ b/meta/recipes-graphics/libsdl2/libsdl2/optional-libunwind-generic.patch
@@ -0,0 +1,18 @@
+Do not error when libunwind-generic is not found, Not all
+implementations of libunwind will provide this library therefore
+do not make it hard error if its not found.
+
+Upstream-Status: Submitted [https://github.com/libsdl-org/SDL/pull/5194]
+Signed-off-by: Khem Raj
+
+--- a/CMakeLists.txt
b/CMakeLists.txt
+@@ -1358,7 +1358,7 @@ elseif(UNIX AND NOT APPLE AND NOT ANDROI
+ if(HAVE_LIBUNWIND_H)
+ # We've already found the header, so REQUIRE the lib to be present
+ pkg_search_module(UNWIND REQUIRED libunwind)
+-pkg_search_module(UNWIND_GENERIC REQUIRED libunwind-generic)
++pkg_search_module(UNWIND_GENERIC libunwind-generic)
+ list(APPEND EXTRA_LIBS ${UNWIND_LIBRARIES}
${UNWIND_GENERIC_LIBRARIES})
+ endif()
+ endif()
diff --git a/meta/recipes-graphics/libsdl2/libsdl2_2.0.18.bb
b/meta/recipes-graphics/libsdl2/libsdl2_2.0.18.bb
index 893386343a7..1559d5e9425 100644
--- a/meta/recipes-graphics/libsdl2/libsdl2_2.0.18.bb
+++ b/meta/recipes-graphics/libsdl2/libsdl2_2.0.18.bb
@@ -18,6 +18,7 @@ PROVIDES = "virtual/libsdl2"
SRC_URI ="http://www.libsdl.org/release/SDL2-${PV}.tar.gz \
file://0001-Fix-build-against-wayland-1.20.patch \ +
file://optional-libunwind-generic.patch \ "
S = "${WORKDIR}/SDL2-${PV}"
--
2.34.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162709):
https://lists.openembedded.org/g/openembedded-core/message/162709
Mute This Topic: https://lists.openembedded.org/mt/88269209/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] btrfs-tools: upgrade 5.16 -> 5.16.2
0001-btrfs-progs-kerncompat-add-local-definition-for-alig.patch
removed since it's included in 5.16.2
Changelog:
=
mkfs: fix detection of profile type for zoned mode when creating DUP
build:
- add missing stub for zoned mode helper when zoned mode not enabled
- fix 64bit types on MIPS and PowerPC
- improved zoned mode support autodetection, for systems with existing
blkzone.h
header but missing support for zone capacity
other: doc updates, test updates
Signed-off-by: Wang Mingyu
---
...compat-add-local-definition-for-alig.patch | 46 ---
...fs-tools_5.16.bb => btrfs-tools_5.16.2.bb} | 3 +-
2 files changed, 1 insertion(+), 48 deletions(-)
delete mode 100644
meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-progs-kerncompat-add-local-definition-for-alig.patch
rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_5.16.bb =>
btrfs-tools_5.16.2.bb} (95%)
diff --git
a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-progs-kerncompat-add-local-definition-for-alig.patch
b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-progs-kerncompat-add-local-definition-for-alig.patch
deleted file mode 100644
index b0fe67922d..00
---
a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-progs-kerncompat-add-local-definition-for-alig.patch
+++ /dev/null
@@ -1,46 +0,0 @@
-From b0cfe12c4d4b8b4ef335cdf4ddefcbdcd1b70d58 Mon Sep 17 00:00:00 2001
-From: David Sterba
-Date: Thu, 13 Jan 2022 14:47:08 +0100
-Subject: [PATCH] btrfs-progs: kerncompat: add local definition for alignment
- macros
-
-There's still problem left with compilation on musl and kernel < 5.11,
-because __ALIGN_KERNEL is not defined anymore:
-
-../bin/ld: kernel-shared/volumes.o: in function `create_chunk':
-volumes.c:(.text+0x17f8): undefined reference to `__ALIGN_KERNEL'
-
-Due to the entangled includes and unconditional definition of
-__ALIGN_KERNEL, we can't use #ifdef in kerncompat.h to define it
-eventually (as kerncompat.h is the first include). Instead add local
-definitions of the macros and rename them to avoid name clashes.
-
-Pull-request: #433
-
-Upstream-Status: Backport
[https://github.com/kdave/btrfs-progs/commit/b0cfe12c4d4b8b4ef335cdf4ddefcbdcd1b70d58]
-
-Signed-off-by: Wang Mingyu
- kerncompat.h | 9 -
- 1 file changed, 8 insertions(+), 1 deletion(-)
-
-diff --git a/kerncompat.h b/kerncompat.h
-index 6ca1526e2..f0a6e196e 100644
a/kerncompat.h
-+++ b/kerncompat.h
-@@ -359,7 +359,14 @@ do { \
-
- /* Alignment check */
- #define IS_ALIGNED(x, a)(((x) & ((typeof(x))(a) - 1)) == 0)
--#define ALIGN(x, a) __ALIGN_KERNEL((x), (a))
-+
-+/*
-+ * Alignment, copied and renamed from /usr/include/linux/const.h to work
around
-+ * issues caused by moving the definition in 5.12
-+ */
-+#define __ALIGN_KERNEL__(x, a)__ALIGN_KERNEL_MASK__(x,
(typeof(x))(a) - 1)
-+#define __ALIGN_KERNEL_MASK__(x, mask)(((x) + (mask)) & ~(mask))
-+#define ALIGN(x, a) __ALIGN_KERNEL__((x), (a))
-
- static inline int is_power_of_2(unsigned long n)
- {
diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.16.bb
b/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.16.2.bb
similarity index 95%
rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_5.16.bb
rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_5.16.2.bb
index e5b2057f26..4ab486c465 100644
--- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.16.bb
+++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_5.16.2.bb
@@ -17,9 +17,8 @@ DEPENDS = "lzo util-linux zlib"
SRC_URI =
"git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;branch=master
\
file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
-
file://0001-btrfs-progs-kerncompat-add-local-definition-for-alig.patch \
"
-SRCREV = "8ad326b2f28c044cb6ed9016d7c3285e23b673c8"
+SRCREV = "31458c9c81935abbed010221261897273a98d2c1"
S = "${WORKDIR}/git"
PACKAGECONFIG ??= " \
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162708):
https://lists.openembedded.org/g/openembedded-core/message/162708
Mute This Topic: https://lists.openembedded.org/mt/89543706/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] libical: Do not set CC explicitly for gir compiler
This ensures that right sysroot is used during build, otherwise we see
warnings in build about using wrong sysroot and it fails explicitly with
clang
x86_64-yoe-linux-ld: warning: library search path "/usr/lib/gcc/x86_6
4-pc-linux-gnu/11.2.0/../../../../lib64" is unsafe for cross-compilation
x86_64-yoe-linux-ld: cannot find /usr/lib/clang/14.0.0/lib/linux/libc
lang_rt.builtins-x86_64.a: No such file or directory
Signed-off-by: Khem Raj
---
...e-Do-not-export-CC-into-gir-compiler.patch | 33 +++
.../recipes-support/libical/libical_3.0.14.bb | 4 ++-
2 files changed, 36 insertions(+), 1 deletion(-)
create mode 100644
meta/recipes-support/libical/libical/0001-cmake-Do-not-export-CC-into-gir-compiler.patch
diff --git
a/meta/recipes-support/libical/libical/0001-cmake-Do-not-export-CC-into-gir-compiler.patch
b/meta/recipes-support/libical/libical/0001-cmake-Do-not-export-CC-into-gir-compiler.patch
new file mode 100644
index 000..3841c060eeb
--- /dev/null
+++
b/meta/recipes-support/libical/libical/0001-cmake-Do-not-export-CC-into-gir-compiler.patch
@@ -0,0 +1,33 @@
+From c06d8a8990c996cbb854508a944202ba70ba7a7c Mon Sep 17 00:00:00 2001
+From: Khem Raj
+Date: Thu, 3 Mar 2022 20:10:04 -0800
+Subject: [PATCH] cmake: Do not export CC into gir compiler
+
+this helps cross compilers where full compiler commandline defines the
+compiler rather than just CC variable, therefore let it use the default
+values from environment and not synthesize it from CMAKE_C_COMPILER just
+for this case.
+
+Upstream-Status: Submitted [https://github.com/libical/libical/pull/552]
+Signed-off-by: Khem Raj
+---
+ cmake/modules/GObjectIntrospectionMacros.cmake | 3 +--
+ 1 file changed, 1 insertion(+), 2 deletions(-)
+
+diff --git a/cmake/modules/GObjectIntrospectionMacros.cmake
b/cmake/modules/GObjectIntrospectionMacros.cmake
+index 83aff931..d7d3f898 100644
+--- a/cmake/modules/GObjectIntrospectionMacros.cmake
b/cmake/modules/GObjectIntrospectionMacros.cmake
+@@ -50,8 +50,7 @@ macro(gir_add_introspections introspections_girs)
+ set(_gir_libtool "--no-libtool")
+
+ add_custom_command(
+- COMMAND ${CMAKE_COMMAND} -E env "CC='${CMAKE_C_COMPILER}'"
+- ${GObjectIntrospection_SCANNER}
++ COMMAND ${GObjectIntrospection_SCANNER}
+ ${GObjectIntrospection_SCANNER_ARGS}
+ --namespace=${_gir_namespace}
+ --nsversion=${_gir_version}
+--
+2.35.1
+
diff --git a/meta/recipes-support/libical/libical_3.0.14.bb
b/meta/recipes-support/libical/libical_3.0.14.bb
index 717eb11e125..58baf3f32f7 100644
--- a/meta/recipes-support/libical/libical_3.0.14.bb
+++ b/meta/recipes-support/libical/libical_3.0.14.bb
@@ -12,7 +12,9 @@ LIC_FILES_CHKSUM =
"file://LICENSE;md5=1910a2a76ddf6a9ba369182494170d87 \
"
SECTION = "libs"
-SRC_URI =
"https://github.com/${BPN}/${BPN}/releases/download/v${PV}/${BP}.tar.gz;
+SRC_URI =
"https://github.com/${BPN}/${BPN}/releases/download/v${PV}/${BP}.tar.gz \
+ file://0001-cmake-Do-not-export-CC-into-gir-compiler.patch \
+ "
SRC_URI[sha256sum] =
"4284b780356f1dc6a01f16083e7b836e63d3815e27ed0eaaad684712357ccc8f"
UPSTREAM_CHECK_URI = "https://github.com/libical/libical/releases;
--
2.35.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162707):
https://lists.openembedded.org/g/openembedded-core/message/162707
Mute This Topic: https://lists.openembedded.org/mt/89543298/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] python3-native: Remove all pyc files
On Thu, 2022-03-03 at 15:28 -0800, Tim Orling wrote: > > > On Thu, Mar 3, 2022 at 9:16 AM Richard Purdie > wrote: > > On Thu, 2022-03-03 at 17:14 +, Ross Burton wrote: > > > On Thu, 3 Mar 2022 at 16:34, Richard Purdie > > > wrote: > > > > This removes a further 1600 files from sstate handling and lets python > > > > create the ones it wants at runtime which is likely much better overall > > > > for performance. > > > > > > Playing devil's advocate: doesn't having them in sstate mean they're > > > generated once and hardlinked, instead of needing to be generated for > > > every recipe which runs pythonnative? > > > > > > Whilst I can't disagree that 1600 files being dropped from sstate is > > > good, we're just punting the recompile step to every recipe when it > > > runs python code. > > > > > > I guess the question here is how long does the Python library take to > > recompile. > > > > > At runtime it should only generate pyc for modules actually used? Yes. > > Another consideration is that there are many sysroots pulling in python3- > > native > > which don't run python and they're only there as there are python scripts > > being > > added which means python has to come too. > > > > I suspect for that reason it could be a net win but it is a tough call. > > > > I tend to be in favor of the reduced number of files moving around. I suppose > we could do some timing comparisons if we really care. It will be a trade-off > of network/io vs compute/io, correct? Yes. I suspect the compile cost is tiny compared to the io/network cost of chucking so many small files around when I suspect they're not used that often. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162706): https://lists.openembedded.org/g/openembedded-core/message/162706 Mute This Topic: https://lists.openembedded.org/mt/89528765/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] python3-native: Remove all pyc files
On Thu, Mar 3, 2022 at 9:16 AM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Thu, 2022-03-03 at 17:14 +, Ross Burton wrote: > > On Thu, 3 Mar 2022 at 16:34, Richard Purdie > > wrote: > > > This removes a further 1600 files from sstate handling and lets python > > > create the ones it wants at runtime which is likely much better overall > > > for performance. > > > > Playing devil's advocate: doesn't having them in sstate mean they're > > generated once and hardlinked, instead of needing to be generated for > > every recipe which runs pythonnative? > > > > Whilst I can't disagree that 1600 files being dropped from sstate is > > good, we're just punting the recompile step to every recipe when it > > runs python code. > > > > I guess the question here is how long does the Python library take to > recompile. > At runtime it should only generate pyc for modules actually used? > > Another consideration is that there are many sysroots pulling in > python3-native > which don't run python and they're only there as there are python scripts > being > added which means python has to come too. > > I suspect for that reason it could be a net win but it is a tough call. > I tend to be in favor of the reduced number of files moving around. I suppose we could do some timing comparisons if we really care. It will be a trade-off of network/io vs compute/io, correct? > Cheers, > > Richard > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162705): https://lists.openembedded.org/g/openembedded-core/message/162705 Mute This Topic: https://lists.openembedded.org/mt/89528765/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] libical: Pass TOOLCHAIN_OPTIONS via CFLAGS
On Thu, 2022-03-03 at 15:05 -0800, Khem Raj wrote:
> On Thu, Mar 3, 2022 at 2:53 PM Richard Purdie
> wrote:
> >
> > On Mon, 2022-02-28 at 20:13 -0800, Khem Raj wrote:
> > > This ensures that right sysroot is used during build, otherwise we see
> > > warnings in build about using wrong sysroot and it fails explicitly with
> > > clang
> > >
> > > x86_64-yoe-linux-ld: warning: library search path "/usr/lib/gcc/x86_6
> > > 4-pc-linux-gnu/11.2.0/../../../../lib64" is unsafe for cross-compilation
> > >
> > > x86_64-yoe-linux-ld: cannot find /usr/lib/clang/14.0.0/lib/linux/libc
> > > lang_rt.builtins-x86_64.a: No such file or directory
> > >
> > > Signed-off-by: Khem Raj
> > > ---
> > > meta/recipes-support/libical/libical_3.0.14.bb | 2 ++
> > > 1 file changed, 2 insertions(+)
> > >
> > > diff --git a/meta/recipes-support/libical/libical_3.0.14.bb
> > > b/meta/recipes-support/libical/libical_3.0.14.bb
> > > index 717eb11e125..879ad8ed595 100644
> > > --- a/meta/recipes-support/libical/libical_3.0.14.bb
> > > +++ b/meta/recipes-support/libical/libical_3.0.14.bb
> > > @@ -18,6 +18,8 @@ UPSTREAM_CHECK_URI =
> > > "https://github.com/libical/libical/releases;
> > >
> > > inherit cmake pkgconfig gobject-introspection vala
> > >
> > > +CFLAGS += "${TOOLCHAIN_OPTIONS}"
> > > +
> > > DEPENDS += "libical-native"
> > >
> > > PACKAGECONFIG ??= "icu glib"
> >
> >
> > I gave this (and the cmake patch) a go and whilst it mostly worked, it
> > doesn't
> > work on arm (qemuarm or beaglebone):
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/4855
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/3774
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/4829
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/3715
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/4825
> >
> > Any ideas?
>
> I think we need to check why CC is being passed here from env
> explicitly when invoking g-ir-scanner-wrapper, which is bare compiler
> without TOOLCHAIN_OPTIONS and this cmd seems to not
> respect CFLAGS
>
> > [95/112] cd
> > /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/build/src/libical
> &&
> /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/recipe-sysroot-native/usr/bin/cmake
> -E env
> "CC='/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc'"
> /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/recipe-sysroot/usr/bin/g-ir-scanner-wrapper
> --c-include=libical/ical.h --pkg-export libical
> --identifier-prefix=ical
> -I/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/libical-3.0.14/src/libical
> /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/build/src/libical/ical.h
> --namespace=ICal --nsversion=3.0 --no-libtool --library=ical
> --include=GObject-2.0
> -L/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/build/lib
> --output
> /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/build/src/libical/ICal-3.0.gir
> --accept-unprefixed
>
> I will take a look later today.
Thanks, I'll be asleep shortly I hope! :)
>
> btw. is this the only failure left ?
>
For that patch in core, yes, I think so.
Cheers,
Richard
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162704):
https://lists.openembedded.org/g/openembedded-core/message/162704
Mute This Topic: https://lists.openembedded.org/mt/89469112/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] libical: Pass TOOLCHAIN_OPTIONS via CFLAGS
On Thu, Mar 3, 2022 at 2:53 PM Richard Purdie
wrote:
>
> On Mon, 2022-02-28 at 20:13 -0800, Khem Raj wrote:
> > This ensures that right sysroot is used during build, otherwise we see
> > warnings in build about using wrong sysroot and it fails explicitly with
> > clang
> >
> > x86_64-yoe-linux-ld: warning: library search path "/usr/lib/gcc/x86_6
> > 4-pc-linux-gnu/11.2.0/../../../../lib64" is unsafe for cross-compilation
> >
> > x86_64-yoe-linux-ld: cannot find /usr/lib/clang/14.0.0/lib/linux/libc
> > lang_rt.builtins-x86_64.a: No such file or directory
> >
> > Signed-off-by: Khem Raj
> > ---
> > meta/recipes-support/libical/libical_3.0.14.bb | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/recipes-support/libical/libical_3.0.14.bb
> > b/meta/recipes-support/libical/libical_3.0.14.bb
> > index 717eb11e125..879ad8ed595 100644
> > --- a/meta/recipes-support/libical/libical_3.0.14.bb
> > +++ b/meta/recipes-support/libical/libical_3.0.14.bb
> > @@ -18,6 +18,8 @@ UPSTREAM_CHECK_URI =
> > "https://github.com/libical/libical/releases;
> >
> > inherit cmake pkgconfig gobject-introspection vala
> >
> > +CFLAGS += "${TOOLCHAIN_OPTIONS}"
> > +
> > DEPENDS += "libical-native"
> >
> > PACKAGECONFIG ??= "icu glib"
>
>
> I gave this (and the cmake patch) a go and whilst it mostly worked, it doesn't
> work on arm (qemuarm or beaglebone):
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/4855
> https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/3774
> https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/4829
> https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/3715
> https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/4825
>
> Any ideas?
I think we need to check why CC is being passed here from env
explicitly when invoking g-ir-scanner-wrapper, which is bare compiler
without TOOLCHAIN_OPTIONS and this cmd seems to not
respect CFLAGS
| [95/112] cd
/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/build/src/libical
&&
/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/recipe-sysroot-native/usr/bin/cmake
-E env
"CC='/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc'"
/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/recipe-sysroot/usr/bin/g-ir-scanner-wrapper
--c-include=libical/ical.h --pkg-export libical
--identifier-prefix=ical
-I/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/libical-3.0.14/src/libical
/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/build/src/libical/ical.h
--namespace=ICal --nsversion=3.0 --no-libtool --library=ical
--include=GObject-2.0
-L/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/build/lib
--output
/home/pokybuild/yocto-worker/beaglebone/build/build/tmp/work/cortexa8hf-neon-poky-linux-gnueabi/libical/3.0.14-r0/build/src/libical/ICal-3.0.gir
--accept-unprefixed
I will take a look later today.
btw. is this the only failure left ?
>
> Cheers,
>
> Richard
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162703):
https://lists.openembedded.org/g/openembedded-core/message/162703
Mute This Topic: https://lists.openembedded.org/mt/89469112/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] libical: Pass TOOLCHAIN_OPTIONS via CFLAGS
On Mon, 2022-02-28 at 20:13 -0800, Khem Raj wrote:
> This ensures that right sysroot is used during build, otherwise we see
> warnings in build about using wrong sysroot and it fails explicitly with
> clang
>
> x86_64-yoe-linux-ld: warning: library search path "/usr/lib/gcc/x86_6
> 4-pc-linux-gnu/11.2.0/../../../../lib64" is unsafe for cross-compilation
>
> x86_64-yoe-linux-ld: cannot find /usr/lib/clang/14.0.0/lib/linux/libc
> lang_rt.builtins-x86_64.a: No such file or directory
>
> Signed-off-by: Khem Raj
> ---
> meta/recipes-support/libical/libical_3.0.14.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-support/libical/libical_3.0.14.bb
> b/meta/recipes-support/libical/libical_3.0.14.bb
> index 717eb11e125..879ad8ed595 100644
> --- a/meta/recipes-support/libical/libical_3.0.14.bb
> +++ b/meta/recipes-support/libical/libical_3.0.14.bb
> @@ -18,6 +18,8 @@ UPSTREAM_CHECK_URI =
> "https://github.com/libical/libical/releases;
>
> inherit cmake pkgconfig gobject-introspection vala
>
> +CFLAGS += "${TOOLCHAIN_OPTIONS}"
> +
> DEPENDS += "libical-native"
>
> PACKAGECONFIG ??= "icu glib"
I gave this (and the cmake patch) a go and whilst it mostly worked, it doesn't
work on arm (qemuarm or beaglebone):
https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/4855
https://autobuilder.yoctoproject.org/typhoon/#/builders/106/builds/3774
https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/4829
https://autobuilder.yoctoproject.org/typhoon/#/builders/110/builds/3715
https://autobuilder.yoctoproject.org/typhoon/#/builders/47/builds/4825
Any ideas?
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162702):
https://lists.openembedded.org/g/openembedded-core/message/162702
Mute This Topic: https://lists.openembedded.org/mt/89469112/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] insane: Accomodate llvm-objdump
llvm-objdump emite MIPS_XHASH where as GNU objdump emits DT_MIPS_XHASH,
checking for shorted sequence makes this check work in both cases
mips-yoe-linux-objdump -p libx264.so.163 | grep XHASH
DT_MIPS_XHASH0x0168
mips-yoe-linux-llvm-objdump -p libx264.so.163 | grep XHASH
MIPS_XHASH0x0168
both are same things
Signed-off-by: Khem Raj
---
meta/classes/insane.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/insane.bbclass b/meta/classes/insane.bbclass
index 3c8d49f13bd..270b7860c7e 100644
--- a/meta/classes/insane.bbclass
+++ b/meta/classes/insane.bbclass
@@ -429,7 +429,7 @@ def package_qa_hash_style(path, name, d, elf, messages):
for line in phdrs.split("\n"):
if "SYMTAB" in line:
has_syms = True
-if "GNU_HASH" in line or "DT_MIPS_XHASH" in line:
+if "GNU_HASH" in line or "MIPS_XHASH" in line:
sane = True
if ("[mips32]" in line or "[mips64]" in line) and d.getVar('TCLIBC')
== "musl":
sane = True
--
2.35.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162701):
https://lists.openembedded.org/g/openembedded-core/message/162701
Mute This Topic: https://lists.openembedded.org/mt/89536121/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 2/2] python3-jsonschema: upgrade 3.2.0 -> 4.4.0
Upstream changed from setup.py to pyproject.toml+setup.cfg
inherit setuptools_build_meta
For changes see:
https://github.com/Julian/jsonschema/blob/main/CHANGELOG.rst#v440
Signed-off-by: Tim Orling
---
...n3-jsonschema_3.2.0.bb => python3-jsonschema_4.4.0.bb} | 8
1 file changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-devtools/python/{python3-jsonschema_3.2.0.bb =>
python3-jsonschema_4.4.0.bb} (88%)
diff --git a/meta/recipes-devtools/python/python3-jsonschema_3.2.0.bb
b/meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb
similarity index 88%
rename from meta/recipes-devtools/python/python3-jsonschema_3.2.0.bb
rename to meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb
index c7efe33a832..4c142296410 100644
--- a/meta/recipes-devtools/python/python3-jsonschema_3.2.0.bb
+++ b/meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb
@@ -3,12 +3,12 @@ HOMEPAGE = "https://github.com/Julian/jsonschema;
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://COPYING;md5=7a60a81c146ec25599a3e1dabb8610a8 \
file://json/LICENSE;md5=9d4de43111d33570c8fe49b4cb0e01af"
-DEPENDS += "${PYTHON_PN}-vcversioner-native ${PYTHON_PN}-setuptools-scm-native"
-SRC_URI[md5sum] = "f1a0b5011f05a02a8dee1070cd10a26d"
-SRC_URI[sha256sum] =
"c8a85b28d377cc7737e46e2d9f2b4f44ee3c0e1deac6bf46ddefc7187d30797a"
+SRC_URI[sha256sum] =
"636694eb41b3535ed608fe04129f26542b59ed99808b4f688aa32dcf55317a83"
+
+inherit pypi setuptools_build_meta
-inherit pypi setuptools3
+DEPENDS += "${PYTHON_PN}-vcversioner-native ${PYTHON_PN}-setuptools-scm-native"
PACKAGECONFIG ??= "format"
PACKAGECONFIG[format] = ",,,\
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162700):
https://lists.openembedded.org/g/openembedded-core/message/162700
Mute This Topic: https://lists.openembedded.org/mt/89534636/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/2] python3-importlib-metadata: upgrade 4.10.1 -> 4.11.2
inherit setuptools_build_meta
v4.11.2
369: Fixed bug where EntryPoint.extras was returning match objects and not the
extras strings.
v4.11.1
367: In Distribution.requires for egg-info, if requires.txt is empty, return an
empty list.
v4.11.0
bpo-46246: Added __slots__ to EntryPoints.
v4.10.2
365 and bpo-46546: Avoid leaking method_name in DeprecatedList.
Signed-off-by: Tim Orling
---
...-metadata_4.10.1.bb => python3-importlib-metadata_4.11.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/python/{python3-importlib-metadata_4.10.1.bb =>
python3-importlib-metadata_4.11.2.bb} (88%)
diff --git a/meta/recipes-devtools/python/python3-importlib-metadata_4.10.1.bb
b/meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb
similarity index 88%
rename from meta/recipes-devtools/python/python3-importlib-metadata_4.10.1.bb
rename to meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb
index ff40def563f..15c468e41b7 100644
--- a/meta/recipes-devtools/python/python3-importlib-metadata_4.10.1.bb
+++ b/meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb
@@ -8,7 +8,7 @@ inherit pypi setuptools3
PYPI_PACKAGE = "importlib_metadata"
UPSTREAM_CHECK_REGEX = "/importlib-metadata/(?P(\d+[\.\-_]*)+)/"
-SRC_URI[sha256sum] =
"951f0d8a5b7260e9db5e41d429285b5f451e928479f19d80818878527d36e95e"
+SRC_URI[sha256sum] =
"b36ffa925fe3139b2f6ff11d6925ffd4fa7bc47870165e3ac260ac7b4f91e6ac"
S = "${WORKDIR}/importlib_metadata-${PV}"
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162699):
https://lists.openembedded.org/g/openembedded-core/message/162699
Mute This Topic: https://lists.openembedded.org/mt/89534634/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] vulkan-loader: upgrading to 1.3.204.1 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-loader* to *1.3.204.1* has Succeeded. Next steps: - apply the patch: git am 0001-vulkan-loader-upgrade-1.3.204.0-1.3.204.1.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper Loading cache...done. Loaded 0 entries from dependency cache. Parsing recipes...done. Parsing of 843 .bb files complete (0 cached, 843 parsed). 1522 targets, 50 skipped, 0 masked, 0 errors. Removing 43 recipes from the core2-32 sysroot...done. Removing 50 recipes from the qemux86 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.53.1" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "i686-poky-linux-musl" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "3.4+snapshot-f7e66a546b8f9537779b63d96155b8846077b723" TUNE_FEATURES= "m32 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:f7e66a546b8f9537779b63d96155b8846077b723" workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c" Initialising tasks...done. Sstate summary: Wanted 218 Local 206 Mirrors 0 Missed 12 Current 170 (94% match, 96% complete) Removing 2 stale sstate objects for arch x86_64...done. NOTE: Executing Tasks NOTE: Running setscene task 174 of 388 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/mesa/mesa_21.3.7.bb:do_packagedata_setscene) NOTE: Running task 718 of 1407 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-headers_1.3.204.0.bb:do_fetch) NOTE: Running task 723 of 1407 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-loader_1.3.204.1.bb:do_fetch) NOTE: recipe vulkan-headers-1.3.204.0-r0: task do_fetch: Started NOTE: recipe vulkan-loader-1.3.204.1-r0: task do_fetch: Started NOTE: recipe mesa-2_21.3.7-r0: task do_packagedata_setscene: Started NOTE: recipe vulkan-headers-1.3.204.0-r0: task do_fetch: Succeeded NOTE: recipe vulkan-loader-1.3.204.1-r0: task do_fetch: Succeeded NOTE: Running task 768 of 1407 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-loader_1.3.204.1.bb:do_unpack) NOTE: Running task 769 of 1407 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-headers_1.3.204.0.bb:do_unpack) NOTE: recipe vulkan-headers-1.3.204.0-r0: task do_unpack: Started NOTE: recipe vulkan-loader-1.3.204.1-r0: task do_unpack: Started NOTE: recipe mesa-2_21.3.7-r0: task do_packagedata_setscene: Succeeded NOTE: Running setscene task 186 of 388 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/mesa/mesa_21.3.7.bb:do_package_setscene) NOTE: recipe vulkan-loader-1.3.204.1-r0: task do_unpack: Succeeded NOTE: recipe vulkan-headers-1.3.204.0-r0: task do_unpack: Succeeded NOTE: Running task 770 of 1407 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-headers_1.3.204.0.bb:do_patch) NOTE: Running task 771 of 1407 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-loader_1.3.204.1.bb:do_patch) NOTE: recipe vulkan-headers-1.3.204.0-r0: task do_patch: Started NOTE: recipe vulkan-loader-1.3.204.1-r0: task do_patch: Started NOTE: recipe vulkan-headers-1.3.204.0-r0: task do_patch: Succeeded NOTE: recipe vulkan-loader-1.3.204.1-r0: task do_patch: Succeeded NOTE: Running task 772 of 1407 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-headers_1.3.204.0.bb:do_generate_toolchain_file) NOTE: Running task 773 of 1407 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-headers_1.3.204.0.bb:do_deploy_source_date_epoch) NOTE: Running task 774 of 1407 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-loader_1.3.204.1.bb:do_deploy_source_date_epoch) NOTE: Running task 775 of 1407 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/vulkan/vulkan-loader_1.3.204.1.bb:do_generate_toolchain_file) NOTE: Running task 776 of 1407
[OE-core] [AUH] Upgrade status: 2022-03-03
Recipe upgrade statistics: * Succeeded: 16 kea, 2.0.2, Unassigned seatd, 0.6.4, Alexander Kanavin apt, 2.4.0, Aníbal Limón btrfs-tools, 5.16.2, Wang Mingyu mmc-utils, 0.1-new-commits-available, Anuj Mittal python3-cython, 0.29.28, Oleksandr Kravchuk python3-setuptools, 60.9.3, Oleksandr Kravchuk asciidoc, 10.1.4, Yi Zhao libsecret, 0.20.5, Alexander Kanavin harfbuzz, 4.0.0, Anuj Mittal piglit, 1.0-new-commits-available, Ross Burton vulkan-headers, 1.3.204.1, Anuj Mittal vulkan-loader, 1.3.204.1, Anuj Mittal vulkan-tools, 1.3.204.1, Anuj Mittal webkitgtk, 2.34.6, Alexander Kanavin diffoscope, 206, Joshua Watt * Failed(do_compile): 4 openssh, 8.9p1, Unassigned python3-importlib-metadata, 4.11.2, Tim Orling python3-jsonschema, 4.4.0, Bruce Ashfield xwayland, 22.1.0, Unassigned * Failed (devtool error): 6 dbus-test, 1.14.0, Chen Qi dbus, 1.14.0, Chen Qi gnu-config, 20211108-new-commits-available, Robert Yang libstd-rs, 1.59.0, Randy MacLeod rust-llvm, 1.59.0, Randy MacLeod librsvg, 2.52.6, Anuj Mittal * Failed(other errors): 2 cargo, 1.59.0, Randy MacLeod vulkan-samples, git-new-commits-available, Ross Burton TOTAL: attempted=28 succeeded=16(57.14%) failed=12(42.86%) Recipe upgrade statistics per Maintainer: Oleksandr Kravchuk -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162694): https://lists.openembedded.org/g/openembedded-core/message/162694 Mute This Topic: https://lists.openembedded.org/mt/89530606/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] python3-setuptools: upgrading to 60.9.3 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-setuptools* to *60.9.3* has Succeeded. Next steps: - apply the patch: git am 0001-python3-setuptools-upgrade-59.5.0-60.9.3.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper 0001-python3-setuptools-upgrade-59.5.0-60.9.3.patch Description: Binary data packages/core2-32-poky-linux/python3-setuptools: PKGV changed from 59.5.0 [default] to 60.9.3 [default] packages/core2-32-poky-linux/python3-setuptools: PV changed from "59.5.0" to "60.9.3" packages/core2-32-poky-linux/python3-setuptools: SRC_URI changed from "https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-59.5.0.tar.gz file://0001-change-shebang-to-python3.patch file://0001-_distutils-sysconfig-append-STAGING_LIBDIR-python-sy.patch" to "https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-60.9.3.tar.gz file://0001-change-shebang-to-python3.patch file://0001-_distutils-sysconfig-append-STAGING_LIBDIR-python-sy.patch" packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: PKGV changed from 59.5.0 [default] to 60.9.3 [default] packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: PV changed from "59.5.0" to "60.9.3" packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: PKGSIZE changed from 867940 to 1313766 (+51%) packages/core2-32-poky-linux/python3-setuptools/python3-pkg-resources: FILELIST: removed "/usr/lib/python3.10/site-packages/pkg_resources/tests/data/my-test-package-source/__pycache__/setup.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/tests/data/my-test-package-source/setup.py", added "/usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/__pycache__/abc.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/more_itertools/__pycache__/more.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/jaraco/__pycache__/context.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/__pycache__/_legacy.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/more_itertools/__pycache__/recipes.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/jaraco/__pycache__/__init__.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/jaraco /context.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/_common.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/jaraco/text/__pycache__/__init__.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/more_itertools/__pycache__/__init__.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/more_itertools/recipes.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/__pycache__/simple.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/_legacy.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/simple.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/jaraco/__pycache__/functools.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/zipp.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/__pycache__/_compat.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_reso urces/_vendor/importlib_resources/__pycache__/_adapters.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/_adapters.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/more_itertools/more.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/__pycache__/__init__.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/__init__.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/_itertools.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/abc.py /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/__pycache__/_common.cpython-310.pyc /usr/lib/python3.10/site-packages/pkg_resources/_vendor/importlib_resources/__pycache__/_itertools.cpython-310.pyc
[OE-core] [AUH] vulkan-tools: upgrading to 1.3.204.1 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-tools* to *1.3.204.1* has Succeeded. Next steps: - apply the patch: git am 0001-vulkan-tools-upgrade-1.3.204.0-1.3.204.1.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper packages/core2-32-poky-linux/vulkan-tools: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-tools: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-dbg: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-dbg: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-dev: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-dev: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-doc: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-doc: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-locale: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-locale: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-src: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-src: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-staticdev: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-tools/vulkan-tools-staticdev: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-tools/vulkan-tools: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-tools/vulkan-tools: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] 0001-vulkan-tools-upgrade-1.3.204.0-1.3.204.1.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162691): https://lists.openembedded.org/g/openembedded-core/message/162691 Mute This Topic: https://lists.openembedded.org/mt/89530603/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] vulkan-samples: upgrading to 02f8d8465d4df3fa8a0d4d051fcb12538de1d448 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-samples* to *02f8d8465d4df3fa8a0d4d051fcb12538de1d448* has Failed(other errors). Detailed error information: 'MACHINE=qemux86 bitbake vulkan-samples' failed Loading cache...done. Loaded 0 entries from dependency cache. Parsing recipes...done. Parsing of 843 .bb files complete (0 cached, 843 parsed). 1521 targets, 35 skipped, 0 masked, 0 errors. Removing 44 recipes from the core2-32 sysroot...done. Removing 50 recipes from the qemux86 sysroot...done. Summary: There was 1 ERROR message, returning a non-zero exit code. /usr/lib64/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve package from __spec__ or __package__, falling back on __name__ and __path__ return f(*args, **kwds) ERROR: Nothing PROVIDES 'vulkan-samples' vulkan-samples was skipped: incompatible with host i686-poky-linux (not in COMPATIBLE_HOST) Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162688): https://lists.openembedded.org/g/openembedded-core/message/162688 Mute This Topic: https://lists.openembedded.org/mt/89530600/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] vulkan-headers: upgrading to 1.3.204.1 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-headers* to *1.3.204.1* has Succeeded. Next steps: - apply the patch: git am 0001-vulkan-headers-upgrade-1.3.204.0-1.3.204.1.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper 0001-vulkan-headers-upgrade-1.3.204.0-1.3.204.1.patch Description: Binary data packages/core2-32-poky-linux/vulkan-headers: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-headers: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-dbg: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-dbg: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-dev: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-dev: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-doc: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-doc: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-locale: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-locale: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-src: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-src: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-staticdev: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-headers/vulkan-headers-staticdev: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] packages/core2-32-poky-linux/vulkan-headers/vulkan-headers: PV changed from "1.3.204.0" to "1.3.204.1" packages/core2-32-poky-linux/vulkan-headers/vulkan-headers: PKGV changed from 1.3.204.0 [default] to 1.3.204.1 [default] -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162692): https://lists.openembedded.org/g/openembedded-core/message/162692 Mute This Topic: https://lists.openembedded.org/mt/89530604/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] piglit: upgrading to 96180e4850d10ae41ace32c5c0deca25f9a89b1f SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *piglit* to *96180e4850d10ae41ace32c5c0deca25f9a89b1f* has Succeeded. Next steps: - apply the patch: git am 0001-piglit-upgrade-to-latest-revision.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper 0001-piglit-upgrade-to-latest-revision.patch Description: Binary data packages/core2-32-poky-linux/piglit: PKGV changed from 1.0+gitrAUTOINC+2f80c7cc9c [default] to 1.0+gitrAUTOINC+96180e4850 [default] packages/core2-32-poky-linux/piglit: PV changed from "1.0+gitrAUTOINC+2f80c7cc9c" to "1.0+gitrAUTOINC+96180e4850" packages/core2-32-poky-linux/piglit/piglit-bash-completion: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-bash-completion: PV changed from "1.0+gitrAUTOINC+2f80c7cc9c" to "1.0+gitrAUTOINC+96180e4850" packages/core2-32-poky-linux/piglit/piglit-dbg: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-dbg: PV changed from "1.0+gitrAUTOINC+2f80c7cc9c" to "1.0+gitrAUTOINC+96180e4850" packages/core2-32-poky-linux/piglit/piglit-dev: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-dev: PV changed from "1.0+gitrAUTOINC+2f80c7cc9c" to "1.0+gitrAUTOINC+96180e4850" packages/core2-32-poky-linux/piglit/piglit-doc: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-doc: PV changed from "1.0+gitrAUTOINC+2f80c7cc9c" to "1.0+gitrAUTOINC+96180e4850" packages/core2-32-poky-linux/piglit/piglit-locale: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-locale: PV changed from "1.0+gitrAUTOINC+2f80c7cc9c" to "1.0+gitrAUTOINC+96180e4850" packages/core2-32-poky-linux/piglit/piglit-src: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-src: PV changed from "1.0+gitrAUTOINC+2f80c7cc9c" to "1.0+gitrAUTOINC+96180e4850" packages/core2-32-poky-linux/piglit/piglit-staticdev: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-staticdev: PV changed from "1.0+gitrAUTOINC+2f80c7cc9c" to "1.0+gitrAUTOINC+96180e4850" packages/core2-32-poky-linux/piglit/piglit: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit: PV changed from "1.0+gitrAUTOINC+2f80c7cc9c" to "1.0+gitrAUTOINC+96180e4850" packages/core2-32-poky-linux/piglit/piglit: PKGSIZE changed from 2042257178 to 2042257370 (+0%) packages/core2-32-poky-linux/piglit/piglit-bash-completion: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-dbg: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-dev: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-doc: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-locale: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-src: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit-staticdev: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 packages/core2-32-poky-linux/piglit/piglit: PKGV changed from 1.0+gitr0+2f80c7cc9c to 1.0+gitr0+96180e4850 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162687): https://lists.openembedded.org/g/openembedded-core/message/162687 Mute This Topic: https://lists.openembedded.org/mt/89530599/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] asciidoc: upgrading to 10.1.4 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *asciidoc* to *10.1.4* has Succeeded. Next steps: - apply the patch: git am 0001-asciidoc-upgrade-10.1.3-10.1.4.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper packages/core2-32-poky-linux/asciidoc/asciidoc-dbg: PKGV changed from 10.1.3 [default] to 10.1.4 [default] packages/core2-32-poky-linux/asciidoc/asciidoc-dbg: PV changed from "10.1.3" to "10.1.4" packages/core2-32-poky-linux/asciidoc/asciidoc-dev: PKGV changed from 10.1.3 [default] to 10.1.4 [default] packages/core2-32-poky-linux/asciidoc/asciidoc-dev: PV changed from "10.1.3" to "10.1.4" packages/core2-32-poky-linux/asciidoc/asciidoc-doc: PKGV changed from 10.1.3 [default] to 10.1.4 [default] packages/core2-32-poky-linux/asciidoc/asciidoc-doc: PV changed from "10.1.3" to "10.1.4" packages/core2-32-poky-linux/asciidoc/asciidoc-locale: PKGV changed from 10.1.3 [default] to 10.1.4 [default] packages/core2-32-poky-linux/asciidoc/asciidoc-locale: PV changed from "10.1.3" to "10.1.4" packages/core2-32-poky-linux/asciidoc/asciidoc-src: PKGV changed from 10.1.3 [default] to 10.1.4 [default] packages/core2-32-poky-linux/asciidoc/asciidoc-src: PV changed from "10.1.3" to "10.1.4" packages/core2-32-poky-linux/asciidoc/asciidoc-staticdev: PKGV changed from 10.1.3 [default] to 10.1.4 [default] packages/core2-32-poky-linux/asciidoc/asciidoc-staticdev: PV changed from "10.1.3" to "10.1.4" packages/core2-32-poky-linux/asciidoc/asciidoc: PKGV changed from 10.1.3 [default] to 10.1.4 [default] packages/core2-32-poky-linux/asciidoc/asciidoc: FILELIST: directory renamed /usr/lib/python3.10/site-packages/asciidoc-10.1.3.dist-info -> /usr/lib/python3.10/site-packages/asciidoc-10.1.4.dist-info, added "/usr/lib/python3.10/site-packages/asciidoc/attrs.py /usr/lib/python3.10/site-packages/asciidoc/__pycache__/attrs.cpython-310.pyc" packages/core2-32-poky-linux/asciidoc/asciidoc: PV changed from "10.1.3" to "10.1.4" packages/core2-32-poky-linux/asciidoc/asciidoc: PKGSIZE changed from 1082433 to 1081650 (-0%) packages/core2-32-poky-linux/asciidoc: PKGV changed from 10.1.3 [default] to 10.1.4 [default] packages/core2-32-poky-linux/asciidoc: PV changed from "10.1.3" to "10.1.4" Changes to packages/core2-32-poky-linux/asciidoc (sysroot): /usr/lib/python3.10/site-packages/asciidoc-10.1.3.dist-info moved to /usr/lib/python3.10/site-packages/asciidoc-10.1.4.dist-info /usr/lib/python3.10/site-packages/asciidoc/attrs.py was added /usr/lib/python3.10/site-packages/asciidoc/__pycache__/attrs.cpython-310.pyc was added packages/core2-32-poky-linux/asciidoc/asciidoc: FILELIST: directory renamed /usr/lib/python3.10/site-packages/asciidoc-10.1.3.dist-info -> /usr/lib/python3.10/site-packages/asciidoc-10.1.4.dist-info, added "/usr/lib/python3.10/site-packages/asciidoc/__pycache__/attrs.cpython-310.pyc /usr/lib/python3.10/site-packages/asciidoc/attrs.py" Changes to packages/core2-32-poky-linux/asciidoc (sysroot): /usr/lib/python3.10/site-packages/asciidoc-10.1.3.dist-info moved to /usr/lib/python3.10/site-packages/asciidoc-10.1.4.dist-info /usr/lib/python3.10/site-packages/asciidoc/attrs.py was added /usr/lib/python3.10/site-packages/asciidoc/__pycache__/attrs.cpython-310.pyc was added 0001-asciidoc-upgrade-10.1.3-10.1.4.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162690): https://lists.openembedded.org/g/openembedded-core/message/162690 Mute This Topic: https://lists.openembedded.org/mt/89530602/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] libsecret: upgrading to 0.20.5 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libsecret* to *0.20.5* has Succeeded. Next steps: - apply the patch: git am 0001-libsecret-upgrade-0.20.4-0.20.5.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper 0001-libsecret-upgrade-0.20.4-0.20.5.patch Description: Binary data packages/core2-32-poky-linux/libsecret: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret: PACKAGES: added "libsecret-locale-ab libsecret-locale-fi libsecret-locale-vi" packages/core2-32-poky-linux/libsecret: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret: SRC_URI changed from "https://download.gnome.org/sources//libsecret/0.20/libsecret-0.20.4.tar.xz;name=archive file://determinism.patch" to "https://download.gnome.org/sources//libsecret/0.20/libsecret-0.20.5.tar.xz;name=archive; packages/core2-32-poky-linux/libsecret/libsecret-dbg: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-dbg: PKGSIZE changed from 787936 to 796960 (+1%) packages/core2-32-poky-linux/libsecret/libsecret-dbg: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-dev: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-dev: PKGSIZE changed from 668274 to 674256 (+1%) packages/core2-32-poky-linux/libsecret/libsecret-dev: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-doc: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-doc: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-an: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-locale-an: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-ar: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-locale-ar: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-as: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-locale-as: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-be: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-locale-be: PKGSIZE changed from 1714 to 2165 (+26%) packages/core2-32-poky-linux/libsecret/libsecret-locale-be: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-bg: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-locale-bg: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-bs: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-locale-bs: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-ca+valencia: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-locale-ca+valencia: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-ca: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-locale-ca: PKGSIZE changed from 1505 to 1537 (+2%) packages/core2-32-poky-linux/libsecret/libsecret-locale-ca: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-ckb: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-locale-ckb: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-cs: PV changed from "0.20.4" to "0.20.5" packages/core2-32-poky-linux/libsecret/libsecret-locale-cs: PKGSIZE changed from 1540 to 1588 (+3%) packages/core2-32-poky-linux/libsecret/libsecret-locale-cs: PKGV changed from 0.20.4 [default] to 0.20.5 [default] packages/core2-32-poky-linux/libsecret/libsecret-locale-da: PV changed from "0.20.4" to "0.20.5"
[OE-core] [AUH] xwayland: upgrading to 22.1.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *xwayland* to *22.1.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-xwayland-upgrade-21.1.4-22.1.0.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper Loading cache...done. Loaded 1521 entries from dependency cache. Parsing recipes...done. Parsing of 843 .bb files complete (842 cached, 1 parsed). 1521 targets, 35 skipped, 0 masked, 0 errors. Removing 1 recipes from the core2-32 sysroot...done. Removing 1 recipes from the qemux86 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.53.1" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "i686-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "3.4+snapshot-81a7e08b7e52b2af495e3e414dd163708595b9b5" TUNE_FEATURES= "m32 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:81a7e08b7e52b2af495e3e414dd163708595b9b5" workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c" Initialising tasks...done. Sstate summary: Wanted 118 Local 111 Mirrors 0 Missed 7 Current 318 (94% match, 98% complete) NOTE: Executing Tasks NOTE: Setscene tasks completed NOTE: Running task 1468 of 1561 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/xwayland/xwayland_22.1.0.bb:do_fetch) NOTE: Running task 1530 of 1561 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/xwayland/xwayland_22.1.0.bb:do_write_config) NOTE: recipe xwayland-22.1.0-r0: task do_fetch: Started NOTE: recipe xwayland-22.1.0-r0: task do_write_config: Started NOTE: recipe xwayland-22.1.0-r0: task do_fetch: Succeeded NOTE: Running task 1548 of 1561 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/xwayland/xwayland_22.1.0.bb:do_unpack) NOTE: Running task 1549 of 1561 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/xwayland/xwayland_22.1.0.bb:do_prepare_recipe_sysroot) NOTE: recipe xwayland-22.1.0-r0: task do_write_config: Succeeded NOTE: recipe xwayland-22.1.0-r0: task do_unpack: Started NOTE: recipe xwayland-22.1.0-r0: task do_prepare_recipe_sysroot: Started NOTE: recipe xwayland-22.1.0-r0: task do_unpack: Succeeded NOTE: Running task 1550 of 1561 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/xwayland/xwayland_22.1.0.bb:do_patch) NOTE: recipe xwayland-22.1.0-r0: task do_patch: Started NOTE: recipe xwayland-22.1.0-r0: task do_patch: Succeeded NOTE: Running task 1551 of 1561 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/xwayland/xwayland_22.1.0.bb:do_deploy_source_date_epoch) NOTE: Running task 1552 of 1561 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/xwayland/xwayland_22.1.0.bb:do_populate_lic) NOTE: recipe xwayland-22.1.0-r0: task do_prepare_recipe_sysroot: Succeeded NOTE: recipe xwayland-22.1.0-r0: task do_deploy_source_date_epoch: Started NOTE: recipe xwayland-22.1.0-r0: task do_populate_lic: Started NOTE: recipe xwayland-22.1.0-r0: task do_populate_lic: Succeeded NOTE: recipe xwayland-22.1.0-r0: task do_deploy_source_date_epoch: Succeeded NOTE: Running task 1553 of 1561 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/xwayland/xwayland_22.1.0.bb:do_configure) NOTE: recipe xwayland-22.1.0-r0: task do_configure: Started Log data follows: | DEBUG: Executing python function extend_recipe_sysroot | NOTE: Direct dependencies are ['/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-graphics/xorg-proto/xorgproto_2021.5.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3_3.10.2.bb:do_populate_sysroot', '/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/quilt/quilt-native_0.67.bb:do_populate_sysroot', 'virtual:native:/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/ninja/ninja_1.10.2.bb:do_populate_sysroot',
[OE-core] [AUH] python3-importlib-metadata: upgrading to 4.11.2 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-importlib-metadata* to *4.11.2* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-python3-importlib-metadata-upgrade-4.10.1-4.11.2.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper 0001-python3-importlib-metadata-upgrade-4.10.1-4.11.2.patch Description: Binary data Loading cache...done. Loaded 1521 entries from dependency cache. Parsing recipes...done. Parsing of 843 .bb files complete (842 cached, 1 parsed). 1521 targets, 35 skipped, 0 masked, 0 errors. Removing 1 recipes from the core2-32 sysroot...done. Removing 1 recipes from the qemux86 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.53.1" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "i686-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "3.4+snapshot-95c91b4ad71f01eb02dc0ae5e983734e5a1b4e4a" TUNE_FEATURES= "m32 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:95c91b4ad71f01eb02dc0ae5e983734e5a1b4e4a" workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c" Initialising tasks...done. Sstate summary: Wanted 92 Local 85 Mirrors 0 Missed 7 Current 236 (92% match, 97% complete) NOTE: Executing Tasks NOTE: Setscene tasks completed NOTE: Running task 1028 of 1236 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb:do_fetch) NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_fetch: Started NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_fetch: Succeeded NOTE: Running task 1223 of 1236 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb:do_unpack) NOTE: Running task 1224 of 1236 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb:do_prepare_recipe_sysroot) NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_unpack: Started NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_prepare_recipe_sysroot: Started NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_unpack: Succeeded NOTE: Running task 1225 of 1236 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb:do_patch) NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_patch: Started NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_patch: Succeeded NOTE: Running task 1226 of 1236 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb:do_deploy_source_date_epoch) NOTE: Running task 1227 of 1236 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb:do_populate_lic) NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_prepare_recipe_sysroot: Succeeded NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_deploy_source_date_epoch: Started NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_populate_lic: Started NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_populate_lic: Succeeded NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_deploy_source_date_epoch: Succeeded NOTE: Running task 1228 of 1236 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb:do_configure) NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_configure: Started NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_configure: Succeeded NOTE: Running task 1229 of 1236 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-importlib-metadata_4.11.2.bb:do_compile) NOTE: recipe python3-importlib-metadata-4.11.2-r0: task do_compile: Started Log data follows: | DEBUG: Executing shell function do_compile |
[OE-core] [AUH] libstd-rs: upgrading to 1.59.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libstd-rs* to *1.59.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade libstd-rs -V 1.59.0 NOTE: Starting bitbake server... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection (#1)... Loading cache...done. Loaded 1521 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.53.1" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "3.4+snapshot-2ab1f8f011a9c85bd1cad3445f2c454790a7acb4" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:2ab1f8f011a9c85bd1cad3445f2c454790a7acb4" workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c" Initialising tasks...done. Sstate summary: Wanted 3 Local 3 Mirrors 0 Missed 0 Current 19 (100% match, 100% complete) NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 102 tasks of which 99 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1521 entries from dependency cache. Parsing recipes...done. Parsing of 844 .bb files complete (842 cached, 2 parsed). 1522 targets, 34 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.53.1" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "3.4+snapshot-2ab1f8f011a9c85bd1cad3445f2c454790a7acb4" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:2ab1f8f011a9c85bd1cad3445f2c454790a7acb4" workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c" Initialising tasks...done. Sstate summary: Wanted 3 Local 3 Mirrors 0 Missed 0 Current 15 (100% match, 100% complete) NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 83 tasks of which 81 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 1% || ETA: 0:00:49 Adding changed files: 2% || ETA: 0:00:38 Adding changed files: 3% |# | ETA: 0:00:32 Adding changed files: 4% |# | ETA: 0:00:29 Adding changed files: 5% |# | ETA: 0:00:26 Adding changed files: 6% |## | ETA: 0:00:24 Adding changed files: 7% |## | ETA: 0:00:23 Adding changed files: 8% |### | ETA: 0:00:22 Adding changed files: 9% |### | ETA: 0:00:21 Adding changed files: 10% |### | ETA: 0:00:20 Adding changed files: 11% || ETA: 0:00:19 Adding changed files: 12% || ETA: 0:00:19 Adding changed files: 13% || ETA: 0:00:18 Adding changed files: 14% |# | ETA: 0:00:18 Adding changed files: 15% |# | ETA: 0:00:17 Adding changed files: 16% |## | ETA: 0:00:17 Adding changed files: 17% |## | ETA: 0:00:17 Adding changed files: 18% |## | ETA: 0:00:17 Adding changed files: 19% |### | ETA: 0:00:17 Adding changed files: 20% |### | ETA: 0:00:17 Adding changed files: 21% |### | ETA: 0:00:16 Adding changed files: 22% || ETA: 0:00:16 Adding changed files: 23% || ETA: 0:00:16 Adding changed files: 25% |# | ETA: 0:00:16 Adding changed files: 26% |# | ETA: 0:00:16 Adding changed files: 27% |# | ETA: 0:00:16 Adding changed files: 28% |## | ETA: 0:00:16 Adding changed files: 29% |## | ETA: 0:00:15 Adding changed files: 30%
[OE-core] [AUH] seatd: upgrading to 0.6.4 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *seatd* to *0.6.4* has Succeeded. Next steps: - apply the patch: git am 0001-seatd-upgrade-0.6.3-0.6.4.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper packages/core2-32-poky-linux/seatd: SRC_URI changed from "git://git.sr.ht/~kennylevinsen/seatd;protocol=https;branch=master file://init" to "git://git.sr.ht/%7Ekennylevinsen/seatd;protocol=https;branch=v0.6 file://init" packages/core2-32-poky-linux/seatd: PKGV changed from 0.6.3 [default] to 0.6.4 [default] packages/core2-32-poky-linux/seatd: PV changed from "0.6.3" to "0.6.4" packages/core2-32-poky-linux/seatd/seatd-dbg: PKGV changed from 0.6.3 [default] to 0.6.4 [default] packages/core2-32-poky-linux/seatd/seatd-dbg: PKGSIZE changed from 246100 to 245776 (-0%) packages/core2-32-poky-linux/seatd/seatd-dbg: PV changed from "0.6.3" to "0.6.4" packages/core2-32-poky-linux/seatd/seatd-dev: PKGV changed from 0.6.3 [default] to 0.6.4 [default] packages/core2-32-poky-linux/seatd/seatd-dev: PV changed from "0.6.3" to "0.6.4" packages/core2-32-poky-linux/seatd/seatd-doc: PKGV changed from 0.6.3 [default] to 0.6.4 [default] packages/core2-32-poky-linux/seatd/seatd-doc: PV changed from "0.6.3" to "0.6.4" packages/core2-32-poky-linux/seatd/seatd-locale: PKGV changed from 0.6.3 [default] to 0.6.4 [default] packages/core2-32-poky-linux/seatd/seatd-locale: PV changed from "0.6.3" to "0.6.4" packages/core2-32-poky-linux/seatd/seatd-src: PKGV changed from 0.6.3 [default] to 0.6.4 [default] packages/core2-32-poky-linux/seatd/seatd-src: PKGSIZE changed from 130029 to 129869 (-0%) packages/core2-32-poky-linux/seatd/seatd-src: PV changed from "0.6.3" to "0.6.4" packages/core2-32-poky-linux/seatd/seatd-staticdev: PKGV changed from 0.6.3 [default] to 0.6.4 [default] packages/core2-32-poky-linux/seatd/seatd-staticdev: PV changed from "0.6.3" to "0.6.4" packages/core2-32-poky-linux/seatd/seatd: PKGV changed from 0.6.3 [default] to 0.6.4 [default] packages/core2-32-poky-linux/seatd/seatd: PV changed from "0.6.3" to "0.6.4" 0001-seatd-upgrade-0.6.3-0.6.4.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162680): https://lists.openembedded.org/g/openembedded-core/message/162680 Mute This Topic: https://lists.openembedded.org/mt/89530592/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] python3-cython: upgrading to 0.29.28 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-cython* to *0.29.28* has Succeeded. Next steps: - apply the patch: git am 0001-python3-cython-upgrade-0.29.27-0.29.28.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper packages/core2-32-poky-linux/python3-cython: PV changed from "0.29.27" to "0.29.28" packages/core2-32-poky-linux/python3-cython: SRC_URI changed from "https://files.pythonhosted.org/packages/source/C/Cython/Cython-0.29.27.tar.gz; to "https://files.pythonhosted.org/packages/source/C/Cython/Cython-0.29.28.tar.gz; packages/core2-32-poky-linux/python3-cython: PKGV changed from 0.29.27 [default] to 0.29.28 [default] packages/core2-32-poky-linux/python3-cython/python3-cython-dbg: PV changed from "0.29.27" to "0.29.28" packages/core2-32-poky-linux/python3-cython/python3-cython-dbg: PKGSIZE changed from 7042460 to 7042468 (+0%) packages/core2-32-poky-linux/python3-cython/python3-cython-dbg: PKGV changed from 0.29.27 [default] to 0.29.28 [default] packages/core2-32-poky-linux/python3-cython/python3-cython-dev: PV changed from "0.29.27" to "0.29.28" packages/core2-32-poky-linux/python3-cython/python3-cython-dev: PKGV changed from 0.29.27 [default] to 0.29.28 [default] packages/core2-32-poky-linux/python3-cython/python3-cython-doc: PV changed from "0.29.27" to "0.29.28" packages/core2-32-poky-linux/python3-cython/python3-cython-doc: PKGV changed from 0.29.27 [default] to 0.29.28 [default] packages/core2-32-poky-linux/python3-cython/python3-cython-locale: PV changed from "0.29.27" to "0.29.28" packages/core2-32-poky-linux/python3-cython/python3-cython-locale: PKGV changed from 0.29.27 [default] to 0.29.28 [default] packages/core2-32-poky-linux/python3-cython/python3-cython-src: PV changed from "0.29.27" to "0.29.28" packages/core2-32-poky-linux/python3-cython/python3-cython-src: PKGSIZE changed from 8530787 to 8532726 (+0%) packages/core2-32-poky-linux/python3-cython/python3-cython-src: PKGV changed from 0.29.27 [default] to 0.29.28 [default] packages/core2-32-poky-linux/python3-cython/python3-cython-staticdev: PV changed from "0.29.27" to "0.29.28" packages/core2-32-poky-linux/python3-cython/python3-cython-staticdev: PKGV changed from 0.29.27 [default] to 0.29.28 [default] packages/core2-32-poky-linux/python3-cython/python3-cython: PV changed from "0.29.27" to "0.29.28" packages/core2-32-poky-linux/python3-cython/python3-cython: PKGSIZE changed from 8521879 to 8522152 (+0%) packages/core2-32-poky-linux/python3-cython/python3-cython: PKGV changed from 0.29.27 [default] to 0.29.28 [default] Changes to packages/core2-32-poky-linux/python3-cython (sysroot): /usr/lib/python3.10/site-packages/Cython-0.29.27.dist-info moved to /usr/lib/python3.10/site-packages/Cython-0.29.28.dist-info Changes to packages/core2-32-poky-linux/python3-cython (sysroot): /usr/lib/python3.10/site-packages/Cython-0.29.27.dist-info moved to /usr/lib/python3.10/site-packages/Cython-0.29.28.dist-info 0001-python3-cython-upgrade-0.29.27-0.29.28.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162686): https://lists.openembedded.org/g/openembedded-core/message/162686 Mute This Topic: https://lists.openembedded.org/mt/89530598/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] python3-jsonschema: upgrading to 4.4.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-jsonschema* to *4.4.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-python3-jsonschema-upgrade-3.2.0-4.4.0.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper Loading cache...done. Loaded 1521 entries from dependency cache. Parsing recipes...done. Parsing of 843 .bb files complete (842 cached, 1 parsed). 1521 targets, 35 skipped, 0 masked, 0 errors. Removing 1 recipes from the core2-32 sysroot...done. Removing 1 recipes from the qemux86 sysroot...done. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.53.1" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "i686-poky-linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "3.4+snapshot-b6dc3fd019a750cfa0f56e80545ec2ae654bd0f0" TUNE_FEATURES= "m32 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:b6dc3fd019a750cfa0f56e80545ec2ae654bd0f0" workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c" Initialising tasks...done. Sstate summary: Wanted 98 Local 91 Mirrors 0 Missed 7 Current 283 (92% match, 98% complete) NOTE: Executing Tasks NOTE: Setscene tasks completed NOTE: Running task 1039 of 1400 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb:do_fetch) NOTE: recipe python3-jsonschema-4.4.0-r0: task do_fetch: Started NOTE: recipe python3-jsonschema-4.4.0-r0: task do_fetch: Succeeded NOTE: Running task 1387 of 1400 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb:do_unpack) NOTE: Running task 1388 of 1400 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb:do_prepare_recipe_sysroot) NOTE: recipe python3-jsonschema-4.4.0-r0: task do_unpack: Started NOTE: recipe python3-jsonschema-4.4.0-r0: task do_prepare_recipe_sysroot: Started NOTE: recipe python3-jsonschema-4.4.0-r0: task do_unpack: Succeeded NOTE: Running task 1389 of 1400 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb:do_patch) NOTE: recipe python3-jsonschema-4.4.0-r0: task do_patch: Started NOTE: recipe python3-jsonschema-4.4.0-r0: task do_patch: Succeeded NOTE: Running task 1390 of 1400 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb:do_deploy_source_date_epoch) NOTE: Running task 1391 of 1400 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb:do_populate_lic) NOTE: recipe python3-jsonschema-4.4.0-r0: task do_prepare_recipe_sysroot: Succeeded NOTE: recipe python3-jsonschema-4.4.0-r0: task do_deploy_source_date_epoch: Started NOTE: recipe python3-jsonschema-4.4.0-r0: task do_populate_lic: Started NOTE: recipe python3-jsonschema-4.4.0-r0: task do_populate_lic: Succeeded NOTE: recipe python3-jsonschema-4.4.0-r0: task do_deploy_source_date_epoch: Succeeded NOTE: Running task 1392 of 1400 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb:do_configure) NOTE: recipe python3-jsonschema-4.4.0-r0: task do_configure: Started NOTE: recipe python3-jsonschema-4.4.0-r0: task do_configure: Succeeded NOTE: Running task 1393 of 1400 (/home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/python/python3-jsonschema_4.4.0.bb:do_compile) NOTE: recipe python3-jsonschema-4.4.0-r0: task do_compile: Started Log data follows: | DEBUG: Executing shell function do_compile | /home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-32-poky-linux/python3-jsonschema/4.4.0-r0/recipe-sysroot-native/usr/bin/python3-native/python3: can't open file '/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-32-poky-linux/python3-jsonschema/4.4.0-r0/jsonschema-4.4.0/setup.py': [Errno 2] No such file or directory | ERROR: 'python3 setup.py bdist_wheel ' execution failed. | WARNING:
[OE-core] [AUH] librsvg: upgrading to 2.52.6 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *librsvg* to *2.52.6* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe librsvg failed. NOTE: Starting bitbake server... NOTE: Reconnecting to bitbake server... NOTE: Retrying server connection (#1)... Loading cache...done. Loaded 1521 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.53.1" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "3.4+snapshot-4e45839df84cd016baeed2821fd558b7b9d40dbc" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:4e45839df84cd016baeed2821fd558b7b9d40dbc" workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c" Initialising tasks...done. Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 21 (100% match, 100% complete) NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 102 tasks of which 99 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds Loading cache...done. Loaded 1521 entries from dependency cache. Parsing recipes...done. Parsing of 844 .bb files complete (842 cached, 2 parsed). 1522 targets, 34 skipped, 0 masked, 0 errors. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.53.1" BUILD_SYS= "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "3.4+snapshot-4e45839df84cd016baeed2821fd558b7b9d40dbc" TUNE_FEATURES= "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp = "tmp-auh-upgrades:4e45839df84cd016baeed2821fd558b7b9d40dbc" workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c" Initialising tasks...done. Sstate summary: Wanted 1 Local 1 Mirrors 0 Missed 0 Current 17 (100% match, 100% complete) NOTE: Executing Tasks NOTE: Tasks Summary: Attempted 83 tasks of which 81 didn't need to be rerun and all succeeded. NOTE: Writing buildhistory NOTE: Writing buildhistory took: 1 seconds DEBUG 5 [Errno 25] Inappropriate ioctl for device Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 0% | | ETA: --:--:-- Adding changed files: 9% |### | ETA: 0:00:01 Adding changed files: 19% |### | ETA: 0:00:00 Adding changed files: 29% |## | ETA: 0:00:00 Adding changed files: 39% |## | ETA: 0:00:00 Adding changed files: 49% |# | ETA: 0:00:00 Adding changed files: 59% |# | ETA: 0:00:00 Adding changed files: 69% |# | ETA: 0:00:00 Adding changed files: 79% || ETA: 0:00:00 Adding changed files: 89% || ETA: 0:00:00 Adding changed files: 99% |### | ETA: 0:00:00 Adding changed files: 100% || Time: 0:00:00 INFO: Extracting current version source... INFO: Extracting upgraded version source... INFO: Fetching https://download.gnome.org/sources//librsvg/2.52/librsvg-2.52.6.tar.xz;name=archive... INFO: Rebasing devtool onto 36c286826b743f368fd3d4873a33e8d2a15aecb0 WARNING: Command 'git rebase 36c286826b743f368fd3d4873a33e8d2a15aecb0' failed: Auto-merging vendor/system-deps/src/lib.rs Auto-merging vendor/system-deps/.cargo-checksum.json CONFLICT (content): Merge conflict in vendor/system-deps/.cargo-checksum.json You will need to resolve conflicts in order to complete the upgrade. INFO: Upgraded source extracted to /home/pokybuild/yocto-worker/auh/build/build/build/workspace/sources/librsvg INFO: New recipe is /home/pokybuild/yocto-worker/auh/build/build/build/workspace/recipes/librsvg/librsvg_2.52.6.bb Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162678): https://lists.openembedded.org/g/openembedded-core/message/162678 Mute This Topic: https://lists.openembedded.org/mt/89530590/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe:
[OE-core] [AUH] rust-llvm: upgrading to 1.59.0 FAILED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rust-llvm* to *1.59.0* has Failed (devtool error). Detailed error information: The following devtool command failed: finish -f rust-llvm /home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust NOTE: Starting bitbake server... Loading cache...done. Loaded 1521 entries from dependency cache. Parsing recipes...done. Parsing of 844 .bb files complete (843 cached, 1 parsed). 1523 targets, 34 skipped, 0 masked, 0 errors. ERROR: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py", line 162, in wrapped return func(fn, *args) File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py", line 187, in parse_config_file return bb.parse.handle(fn, data, include) File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py", line 107, in handle return h['handle'](fn, data, include) File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py", line 118, in handle abs_fn = resolve_file(fn, data) File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py", line 131, in resolve_file raise IOError(errno.ENOENT, "file %s not found" % fn) FileNotFoundError: [Errno 2] file /home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf not found ERROR: Unable to parse /home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf: [Errno 2] file /home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf not found Traceback (most recent call last): File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py", line 162, in wrapped return func(fn, *args) File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py", line 187, in parse_config_file return bb.parse.handle(fn, data, include) File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py", line 107, in handle return h['handle'](fn, data, include) File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/parse_py/ConfHandler.py", line 118, in handle abs_fn = resolve_file(fn, data) File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/parse/__init__.py", line 131, in resolve_file raise IOError(errno.ENOENT, "file %s not found" % fn) FileNotFoundError: [Errno 2] file /home/pokybuild/yocto-worker/auh/build/build/poky/meta/recipes-devtools/rust/conf/layer.conf not found During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/devtool", line 334, in ret = main() File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/devtool", line 321, in main ret = args.func(args, config, basepath, workspace) File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py", line 2108, in finish updated, appendfile, removed = _update_recipe(args.recipename, workspace, rd, args.mode, appendlayerdir, wildcard_version=True, no_remove=False, no_report_remove=removing_original, initial_rev=args.initial_rev, dry_run_outdir=dry_run_outdir, no_overrides=args.no_overrides, force_patch_refresh=args.force_patch_refresh) File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py", line 1814, in _update_recipe updated, appendf, removed = _update_recipe_patch(recipename, workspace, srctree, crd, appendlayerdir, wildcard_version, no_remove, no_report_remove, initial_rev, dry_run_outdir, force_patch_refresh) File "/home/pokybuild/yocto-worker/auh/build/build/poky/scripts/lib/devtool/standard.py", line 1671, in _update_recipe_patch redirect_output=dry_run_outdir) File "/home/pokybuild/yocto-worker/auh/build/build/poky/meta/lib/oe/recipeutils.py", line 705, in bbappend_recipe appendpath, pathok = get_bbappend_path(rd, destlayerdir, wildcardver) File "/home/pokybuild/yocto-worker/auh/build/build/poky/meta/lib/oe/recipeutils.py", line 632, in get_bbappend_path confdata = bb.cookerdata.parse_config_file(destlayerconf, confdata) File "/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/lib/bb/cookerdata.py", line 167, in wrapped raise bb.BBHandledException() bb.BBHandledException Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162681):
[OE-core] [AUH] apt: upgrading to 2.4.0 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *apt* to *2.4.0* has Succeeded. Next steps: - apply the patch: git am 0001-apt-upgrade-2.2.4-2.4.0.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper packages/core2-32-poky-linux/apt/apt-bash-completion: PKGSIZE changed from 7108 to 7513 (+6%) packages/core2-32-poky-linux/apt/apt-bash-completion: PKGV changed from 2.2.4 [default] to 2.4.0 [default] packages/core2-32-poky-linux/apt/apt-bash-completion: PV changed from "2.2.4" to "2.4.0" packages/core2-32-poky-linux/apt/apt-dbg: PKGSIZE changed from 53878028 to 55966752 (+4%) packages/core2-32-poky-linux/apt/apt-dbg: PKGV changed from 2.2.4 [default] to 2.4.0 [default] packages/core2-32-poky-linux/apt/apt-dbg: PV changed from "2.2.4" to "2.4.0" packages/core2-32-poky-linux/apt/apt-dev: PKGSIZE changed from 446186 to 448023 (+0%) packages/core2-32-poky-linux/apt/apt-dev: PKGV changed from 2.2.4 [default] to 2.4.0 [default] packages/core2-32-poky-linux/apt/apt-dev: PV changed from "2.2.4" to "2.4.0" packages/core2-32-poky-linux/apt/apt-doc: PKGV changed from 2.2.4 [default] to 2.4.0 [default] packages/core2-32-poky-linux/apt/apt-doc: PV changed from "2.2.4" to "2.4.0" packages/core2-32-poky-linux/apt/apt-locale: PKGV changed from 2.2.4 [default] to 2.4.0 [default] packages/core2-32-poky-linux/apt/apt-locale: PV changed from "2.2.4" to "2.4.0" packages/core2-32-poky-linux/apt/apt-src: PKGSIZE changed from 2863393 to 2888910 (+1%) packages/core2-32-poky-linux/apt/apt-src: PKGV changed from 2.2.4 [default] to 2.4.0 [default] packages/core2-32-poky-linux/apt/apt-src: PV changed from "2.2.4" to "2.4.0" packages/core2-32-poky-linux/apt/apt-staticdev: PKGV changed from 2.2.4 [default] to 2.4.0 [default] packages/core2-32-poky-linux/apt/apt-staticdev: PV changed from "2.2.4" to "2.4.0" packages/core2-32-poky-linux/apt/apt: PKGSIZE changed from 4027916 to 4085041 (+1%) packages/core2-32-poky-linux/apt/apt: PKGV changed from 2.2.4 [default] to 2.4.0 [default] packages/core2-32-poky-linux/apt/apt: PV changed from "2.2.4" to "2.4.0" packages/core2-32-poky-linux/apt: SRC_URI changed from "http://ftp.debian.org/debian/pool/main/a/apt/apt_2.2.4.tar.xz file://triehash file://0001-Disable-documentation-directory-altogether.patch file://0001-Fix-musl-build.patch file://0001-CMakeLists.txt-avoid-changing-install-paths-based-on.patch file://0001-srvrec-Keep-support-for-older-resolver.patch file://0001-cmake-Do-not-build-po-files.patch file://0001-Hide-fstatat64-and-prlimit64-defines-on-musl.patch file://0001-aptwebserver.cc-Include-array.patch" to "http://ftp.debian.org/debian/pool/main/a/apt/apt_2.4.0.tar.xz file://triehash file://0001-Disable-documentation-directory-altogether.patch file://0001-Fix-musl-build.patch file://0001-CMakeLists.txt-avoid-changing-install-paths-based-on.patch file://0001-cmake-Do-not-build-po-files.patch file://0001-Hide-fstatat64-and-prlimit64-defines-on-musl.patch file://0001-aptwebserver.cc-Include-array.patch file://0001-Do-not-init-tables-from-dpkg-configuration.patch file://0001-Revert- always-run-dpkg-configure-a-at-the-end-of-our.patch" packages/core2-32-poky-linux/apt: PKGV changed from 2.2.4 [default] to 2.4.0 [default] packages/core2-32-poky-linux/apt: PV changed from "2.2.4" to "2.4.0" 0001-apt-upgrade-2.2.4-2.4.0.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162674): https://lists.openembedded.org/g/openembedded-core/message/162674 Mute This Topic: https://lists.openembedded.org/mt/89530585/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] mmc-utils: upgrading to 4303889c8bd9a2357587eb6ebacecb70098a264d SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mmc-utils* to *4303889c8bd9a2357587eb6ebacecb70098a264d* has Succeeded. Next steps: - apply the patch: git am 0001-mmc-utils-upgrade-to-latest-revision.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper packages/core2-32-poky-linux/mmc-utils: PKGV changed from 0.1+gitAUTOINC+4637a7c0df [default] to 0.1+gitAUTOINC+4303889c8b [default] packages/core2-32-poky-linux/mmc-utils: PV changed from "0.1+gitAUTOINC+4637a7c0df" to "0.1+gitAUTOINC+4303889c8b" packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PKGSIZE changed from 230128 to 233864 (+2%) packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PV changed from "0.1+gitAUTOINC+4637a7c0df" to "0.1+gitAUTOINC+4303889c8b" packages/core2-32-poky-linux/mmc-utils/mmc-utils-dev: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-dev: PV changed from "0.1+gitAUTOINC+4637a7c0df" to "0.1+gitAUTOINC+4303889c8b" packages/core2-32-poky-linux/mmc-utils/mmc-utils-doc: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-doc: PV changed from "0.1+gitAUTOINC+4637a7c0df" to "0.1+gitAUTOINC+4303889c8b" packages/core2-32-poky-linux/mmc-utils/mmc-utils-locale: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-locale: PV changed from "0.1+gitAUTOINC+4637a7c0df" to "0.1+gitAUTOINC+4303889c8b" packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PKGSIZE changed from 206469 to 208563 (+1%) packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PV changed from "0.1+gitAUTOINC+4637a7c0df" to "0.1+gitAUTOINC+4303889c8b" packages/core2-32-poky-linux/mmc-utils/mmc-utils-staticdev: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-staticdev: PV changed from "0.1+gitAUTOINC+4637a7c0df" to "0.1+gitAUTOINC+4303889c8b" packages/core2-32-poky-linux/mmc-utils/mmc-utils: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils: PV changed from "0.1+gitAUTOINC+4637a7c0df" to "0.1+gitAUTOINC+4303889c8b" packages/core2-32-poky-linux/mmc-utils/mmc-utils-dbg: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-dev: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-doc: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-locale: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-src: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils-staticdev: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b packages/core2-32-poky-linux/mmc-utils/mmc-utils: PKGV changed from 0.1+git0+4637a7c0df to 0.1+git0+4303889c8b 0001-mmc-utils-upgrade-to-latest-revision.patch Description: Binary data -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162679): https://lists.openembedded.org/g/openembedded-core/message/162679 Mute This Topic: https://lists.openembedded.org/mt/89530591/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] gnu-config: upgrading to c179db1b6f2ae484bfca1e9f8bae273e3319fa7d FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to
*c179db1b6f2ae484bfca1e9f8bae273e3319fa7d* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gnu-config -S
c179db1b6f2ae484bfca1e9f8bae273e3319fa7d
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
NOTE: Reconnecting to bitbake server...
NOTE: Previous bitbake instance shutting down?, waiting to retry...
NOTE: Retrying server connection (#2)...
Loading cache...done.
Loaded 1521 entries from dependency cache.
Removing 1 recipes from the x86_64 sysroot...done.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.53.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.4+snapshot-32b93c61f7b993af40e3ca6c82bb82e732a7b460"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp =
"tmp-auh-upgrades:32b93c61f7b993af40e3ca6c82bb82e732a7b460"
workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c"
Initialising tasks...done.
Sstate summary: Wanted 8 Local 0 Mirrors 0 Missed 8 Current 12 (0% match, 60%
complete)
Removing 6 stale sstate objects for arch x86_64...done.
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 56 tasks of which 51 didn't need to be rerun and
1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
INFO: Extracting current version source...
ERROR: Bitbake Fetcher Error: FetchError('Fetch command export
PSEUDO_DISABLED=1; export ftp_proxy="http://proxy.yocto.io:5187/;; export
FTP_PROXY="http://proxy.yocto.io:5187/;; export
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20211108+gitAUTOINC+191bcb948f-r0/devtooltmp-mme_brej/workdir/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20211108+gitAUTOINC+191bcb948f-r0/devtooltmp-mme_brej/workdir/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20211108+gitAUTOINC+191bcb948f-r0/devtooltmp-mme_brej/workdir/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/
gnu-config/20211108+gitAUTOINC+191bcb948f-r0/devtooltmp-mme_brej/workdir/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20211108+gitAUTOINC+191bcb948f-r0/devtooltmp-mme_brej/workdir/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20211108+gitAUTOINC+191bcb948f-r0/devtooltmp-mme_brej/workdir/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
export HOME="/home/pokybuild"; git -c core.fsyncobjectfiles=0 -c
gc.autoDetach=false checkout -B master 191bcb948f7191c36eefe634336f5fc5c0c4c2be
failed with exit code 128, output:\nfatal: not a git repository (or any of the
parent directories): .git\n', None)
ERROR: Logfile of failure stored in:
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/core2-64-poky-linux/gnu-config/20211108+gitAUTOINC+191bcb948f-r0/devtooltmp-mme_brej/temp/log.do_unpack.2279225
ERROR: Extracting source for gnu-config failed
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162675):
https://lists.openembedded.org/g/openembedded-core/message/162675
Mute This Topic: https://lists.openembedded.org/mt/89530587/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] [AUH] btrfs-tools: upgrading to 5.16.2 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *btrfs-tools* to *5.16.2* has Succeeded. Next steps: - apply the patch: git am 0001-btrfs-tools-upgrade-5.16-5.16.2.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-dbg: PKGV changed from 5.16 [default] to 5.16.2 [default] packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-dbg: PV changed from "5.16" to "5.16.2" packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-dbg: PKGSIZE changed from 16917360 to 16930232 (+0%) packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-dev: PKGV changed from 5.16 [default] to 5.16.2 [default] packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-dev: PV changed from "5.16" to "5.16.2" packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-dev: PKGSIZE changed from 202760 to 202894 (+0%) packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-doc: PKGV changed from 5.16 [default] to 5.16.2 [default] packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-doc: PV changed from "5.16" to "5.16.2" packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-locale: PKGV changed from 5.16 [default] to 5.16.2 [default] packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-locale: PV changed from "5.16" to "5.16.2" packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-src: PKGV changed from 5.16 [default] to 5.16.2 [default] packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-src: PV changed from "5.16" to "5.16.2" packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-src: PKGSIZE changed from 3442859 to 3448898 (+0%) packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-staticdev: PKGV changed from 5.16 [default] to 5.16.2 [default] packages/core2-32-poky-linux/btrfs-tools/btrfs-tools-staticdev: PV changed from "5.16" to "5.16.2" packages/core2-32-poky-linux/btrfs-tools/btrfs-tools: PKGV changed from 5.16 [default] to 5.16.2 [default] packages/core2-32-poky-linux/btrfs-tools/btrfs-tools: PV changed from "5.16" to "5.16.2" packages/core2-32-poky-linux/btrfs-tools/btrfs-tools: PKGSIZE changed from 5992445 to 6000639 (+0%) packages/core2-32-poky-linux/btrfs-tools: PKGV changed from 5.16 [default] to 5.16.2 [default] packages/core2-32-poky-linux/btrfs-tools: PV changed from "5.16" to "5.16.2" packages/core2-32-poky-linux/btrfs-tools: SRC_URI changed from "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;branch=master file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch file://0001-btrfs-progs-kerncompat-add-local-definition-for-alig.patch" to "git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git;branch=master file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch" Changes to packages/core2-32-poky-linux/btrfs-tools (sysroot): /usr/lib/python3.10/site-packages/btrfsutil-5.16.2-py3.10.egg-info was added /usr/lib/python3.10/site-packages/btrfsutil-5.16.2-py3.10.egg-info/dependency_links.txt was added /usr/lib/python3.10/site-packages/btrfsutil-5.16.2-py3.10.egg-info/PKG-INFO was added /usr/lib/python3.10/site-packages/btrfsutil-5.16.2-py3.10.egg-info/SOURCES.txt was added /usr/lib/python3.10/site-packages/btrfsutil-5.16.2-py3.10.egg-info/top_level.txt was added /usr/lib/python3.10/site-packages/btrfsutil-5.16-py3.10.egg-info was removed /usr/lib/python3.10/site-packages/btrfsutil-5.16-py3.10.egg-info/dependency_links.txt was removed /usr/lib/python3.10/site-packages/btrfsutil-5.16-py3.10.egg-info/PKG-INFO was removed /usr/lib/python3.10/site-packages/btrfsutil-5.16-py3.10.egg-info/SOURCES.txt was removed /usr/lib/python3.10/site-packages/btrfsutil-5.16-py3.10.egg-info/top_level.txt was removed 0001-btrfs-tools-upgrade-5.16-5.16.2.patch Description: Binary data Changes to packages/core2-32-poky-linux/btrfs-tools (sysroot): /usr/lib/python3.10/site-packages/btrfsutil-5.16.2-py3.10.egg-info was added /usr/lib/python3.10/site-packages/btrfsutil-5.16.2-py3.10.egg-info/dependency_links.txt was added /usr/lib/python3.10/site-packages/btrfsutil-5.16.2-py3.10.egg-info/PKG-INFO was added /usr/lib/python3.10/site-packages/btrfsutil-5.16.2-py3.10.egg-info/SOURCES.txt was added
[OE-core] [AUH] dbus-test: upgrading to 1.14.0 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dbus-test* to *1.14.0* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade dbus-test -V 1.14.0
NOTE: Starting bitbake server...
Loading cache...done.
Loaded 1521 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.53.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.4+snapshot-76bff7d8238b4b407c05b8867ca4900479188923"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp =
"tmp-auh-upgrades:76bff7d8238b4b407c05b8867ca4900479188923"
workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c"
Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 20 (0% match, 100%
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
Loading cache...done.
Loaded 1521 entries from dependency cache.
Parsing recipes...done.
Parsing of 844 .bb files complete (842 cached, 2 parsed). 1522 targets, 34
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.53.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.4+snapshot-76bff7d8238b4b407c05b8867ca4900479188923"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp =
"tmp-auh-upgrades:76bff7d8238b4b407c05b8867ca4900479188923"
workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c"
Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0%
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
WARNING: Failed to fetch URL
https://dbus.freedesktop.org/releases/dbus/dbus-1.14.0.tar.gz, attempting
MIRRORS if available
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1
failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
INFO: Extracting current version source...
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Fetching https://dbus.freedesktop.org/releases/dbus/dbus-1.14.0.tar.gz...
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export
ftp_proxy="http://proxy.yocto.io:5187/;; export
FTP_PROXY="http://proxy.yocto.io:5187/;; export
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-z2hqva1k/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-z2hqva1k/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-z2hqva1k/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-z2hqva1k/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-z2hqva1k/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-z2hq
va1k/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -P
/home/pokybuild/yocto-worker/auh/build/build/build/downloads
'https://dbus.freedesktop.org/releases/dbus/dbus-1.14.0.tar.gz' --progress=dot
-v failed with exit code 8, no output
ERROR: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any
source.', 'https://dbus.freedesktop.org/releases/dbus/dbus-1.14.0.tar.gz')
ERROR: Logfile of failure stored in:
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-z2hqva1k/work/temp/log.do_fetch.1722068
ERROR: Failed to fetch URL
https://dbus.freedesktop.org/releases/dbus/dbus-1.14.0.tar.gz
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162671):
[OE-core] [AUH] dbus: upgrading to 1.14.0 FAILED
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dbus* to *1.14.0* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade dbus -V 1.14.0
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitbake server...
NOTE: Retrying server connection (#1)...
Loading cache...done.
Loaded 1521 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.53.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.4+snapshot-76bff7d8238b4b407c05b8867ca4900479188923"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp =
"tmp-auh-upgrades:76bff7d8238b4b407c05b8867ca4900479188923"
workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c"
Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 20 (0% match, 100%
complete)
NOTE: Executing Tasks
NOTE: Tasks Summary: Attempted 93 tasks of which 90 didn't need to be rerun and
all succeeded.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
Loading cache...done.
Loaded 1521 entries from dependency cache.
Parsing recipes...done.
Parsing of 844 .bb files complete (842 cached, 2 parsed). 1522 targets, 34
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.53.1"
BUILD_SYS= "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "3.4+snapshot-76bff7d8238b4b407c05b8867ca4900479188923"
TUNE_FEATURES= "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp =
"tmp-auh-upgrades:76bff7d8238b4b407c05b8867ca4900479188923"
workspace= "master:0447aace57d46c4de4d120b430384e99fc3a5e0c"
Initialising tasks...done.
Sstate summary: Wanted 0 Local 0 Mirrors 0 Missed 0 Current 0 (0% match, 0%
complete)
NOTE: No setscene tasks
NOTE: Executing Tasks
WARNING: Failed to fetch URL
https://dbus.freedesktop.org/releases/dbus/dbus-1.14.0.tar.gz, attempting
MIRRORS if available
NOTE: Tasks Summary: Attempted 1 tasks of which 0 didn't need to be rerun and 1
failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 1 seconds
INFO: Extracting current version source...
INFO: Adding local source files to srctree...
INFO: Extracting upgraded version source...
INFO: Fetching https://dbus.freedesktop.org/releases/dbus/dbus-1.14.0.tar.gz...
ERROR: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; export
ftp_proxy="http://proxy.yocto.io:5187/;; export
FTP_PROXY="http://proxy.yocto.io:5187/;; export
PATH="/home/pokybuild/yocto-worker/auh/build/build/build/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/scripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-9xz_zgbt/work/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-9xz_zgbt/work/recipe-sysroot/usr/bin/crossscripts:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-9xz_zgbt/work/recipe-sysroot-native/usr/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-9xz_zgbt/work/recipe-sysroot-native/usr/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-9xz_zgbt/work/recipe-sysroot-native/sbin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-9xz_
zgbt/work/recipe-sysroot-native/bin:/home/pokybuild/yocto-worker/auh/build/build/poky/bitbake/bin:/home/pokybuild/yocto-worker/auh/build/build/build/tmp/hosttools";
export HOME="/home/pokybuild"; /usr/bin/env wget -t 2 -T 30 --passive-ftp -P
/home/pokybuild/yocto-worker/auh/build/build/build/downloads
'https://dbus.freedesktop.org/releases/dbus/dbus-1.14.0.tar.gz' --progress=dot
-v failed with exit code 8, no output
ERROR: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any
source.', 'https://dbus.freedesktop.org/releases/dbus/dbus-1.14.0.tar.gz')
ERROR: Logfile of failure stored in:
/home/pokybuild/yocto-worker/auh/build/build/build/tmp/work/recipetool-9xz_zgbt/work/temp/log.do_fetch.1802420
ERROR: Failed to fetch URL
https://dbus.freedesktop.org/releases/dbus/dbus-1.14.0.tar.gz
Please review the attached files for further information and build/update
failures.
Any problem please file a bug at
https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler
Regards,
The Upgrade Helper
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online
[OE-core] [AUH] kea: upgrading to 2.0.2 SUCCEEDED
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *kea* to *2.0.2* has Succeeded. Next steps: - apply the patch: git am 0001-kea-upgrade-2.0.1-2.0.2.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper 0001-kea-upgrade-2.0.1-2.0.2.patch Description: Binary data packages/core2-32-poky-linux/kea/kea-dbg: FILELIST: removed "/usr/lib/.debug/libkea-http.so.29.0.0 /usr/lib/.debug/libkea-dhcpsrv.so.50.0.0 /usr/lib/.debug/libkea-hooks.so.39.0.0", added "/usr/lib/.debug/libkea-dhcpsrv.so.51.0.0 /usr/lib/.debug/libkea-http.so.30.0.0 /usr/lib/.debug/libkea-hooks.so.40.0.0" packages/core2-32-poky-linux/kea/kea-dbg: PKGV changed from 2.0.1 [default] to 2.0.2 [default] packages/core2-32-poky-linux/kea/kea-dbg: PV changed from "2.0.1" to "2.0.2" packages/core2-32-poky-linux/kea/kea-dbg: PKGSIZE changed from 268707028 to 268722796 (+0%) packages/core2-32-poky-linux/kea/kea-dev: PKGV changed from 2.0.1 [default] to 2.0.2 [default] packages/core2-32-poky-linux/kea/kea-dev: PV changed from "2.0.1" to "2.0.2" packages/core2-32-poky-linux/kea/kea-dev: PKGSIZE changed from 3727663 to 3727892 (+0%) packages/core2-32-poky-linux/kea/kea-doc: PKGV changed from 2.0.1 [default] to 2.0.2 [default] packages/core2-32-poky-linux/kea/kea-doc: PV changed from "2.0.1" to "2.0.2" packages/core2-32-poky-linux/kea/kea-doc: PKGSIZE changed from 1162452 to 1162901 (+0%) packages/core2-32-poky-linux/kea/kea-locale: PKGV changed from 2.0.1 [default] to 2.0.2 [default] packages/core2-32-poky-linux/kea/kea-locale: PV changed from "2.0.1" to "2.0.2" packages/core2-32-poky-linux/kea/kea-src: PKGV changed from 2.0.1 [default] to 2.0.2 [default] packages/core2-32-poky-linux/kea/kea-src: PV changed from "2.0.1" to "2.0.2" packages/core2-32-poky-linux/kea/kea-src: PKGSIZE changed from 8936597 to 8938960 (+0%) packages/core2-32-poky-linux/kea/kea-staticdev: PKGV changed from 2.0.1 [default] to 2.0.2 [default] packages/core2-32-poky-linux/kea/kea-staticdev: PV changed from "2.0.1" to "2.0.2" packages/core2-32-poky-linux/kea/kea: FILELIST: removed "/usr/lib/libkea-dhcpsrv.so.50 /usr/lib/libkea-hooks.so.39 /usr/lib/libkea-http.so.29 /usr/lib/libkea-http.so.29.0.0 /usr/lib/libkea-dhcpsrv.so.50.0.0 /usr/lib/libkea-hooks.so.39.0.0", added "/usr/lib/libkea-http.so.30.0.0 /usr/lib/libkea-http.so.30 /usr/lib/libkea-hooks.so.40.0.0 /usr/lib/libkea-dhcpsrv.so.51.0.0 /usr/lib/libkea-dhcpsrv.so.51 /usr/lib/libkea-hooks.so.40" packages/core2-32-poky-linux/kea/kea: PKGV changed from 2.0.1 [default] to 2.0.2 [default] packages/core2-32-poky-linux/kea/kea: PV changed from "2.0.1" to "2.0.2" packages/core2-32-poky-linux/kea: SRC_URI changed from "http://ftp.isc.org/isc/kea/2.0.1/kea-2.0.1.tar.gz file://kea-dhcp4.service file://kea-dhcp6.service file://kea-dhcp-ddns.service file://kea-dhcp4-server file://kea-dhcp6-server file://kea-dhcp-ddns-server file://fix-multilib-conflict.patch file://fix_pid_keactrl.patch file://0001-src-lib-log-logger_unittest_support.cc-do-not-write-.patch" to "http://ftp.isc.org/isc/kea/2.0.2/kea-2.0.2.tar.gz file://kea-dhcp4.service file://kea-dhcp6.service file://kea-dhcp-ddns.service file://kea-dhcp4-server file://kea-dhcp6-server file://kea-dhcp-ddns-server file://fix-multilib-conflict.patch file://fix_pid_keactrl.patch file://0001-src-lib-log-logger_unittest_support.cc-do-not-write-.patch" packages/core2-32-poky-linux/kea: PKGV changed from 2.0.1 [default] to 2.0.2 [default] packages/core2-32-poky-linux/kea: PV changed from "2.0.1" to "2.0.2" Changes to packages/core2-32-poky-linux/kea (sysroot): /usr/lib/libkea-dhcpsrv.so changed symlink target from libkea-dhcpsrv.so.50.0.0 to libkea-dhcpsrv.so.51.0.0 /usr/lib/libkea-hooks.so changed symlink target from libkea-hooks.so.39.0.0 to libkea-hooks.so.40.0.0 /usr/lib/libkea-http.so changed symlink target from libkea-http.so.29.0.0 to libkea-http.so.30.0.0 /usr/lib/libkea-dhcpsrv.so.50.0.0 moved to /usr/lib/libkea-dhcpsrv.so.51.0.0 /usr/lib/libkea-dhcpsrv.so.50 moved to /usr/lib/libkea-dhcpsrv.so.51 /usr/lib/libkea-hooks.so.39.0.0 moved to /usr/lib/libkea-hooks.so.40.0.0 /usr/lib/libkea-hooks.so.39 moved to /usr/lib/libkea-hooks.so.40 /usr/lib/libkea-http.so.29.0.0 moved to /usr/lib/libkea-http.so.30.0.0
Re: [OE-core] [PATCH 1/2] python3-native: Remove all pyc files
On Thu, 2022-03-03 at 17:14 +, Ross Burton wrote: > On Thu, 3 Mar 2022 at 16:34, Richard Purdie > wrote: > > This removes a further 1600 files from sstate handling and lets python > > create the ones it wants at runtime which is likely much better overall > > for performance. > > Playing devil's advocate: doesn't having them in sstate mean they're > generated once and hardlinked, instead of needing to be generated for > every recipe which runs pythonnative? > > Whilst I can't disagree that 1600 files being dropped from sstate is > good, we're just punting the recompile step to every recipe when it > runs python code. > > I guess the question here is how long does the Python library take to > recompile. Another consideration is that there are many sysroots pulling in python3-native which don't run python and they're only there as there are python scripts being added which means python has to come too. I suspect for that reason it could be a net win but it is a tough call. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162669): https://lists.openembedded.org/g/openembedded-core/message/162669 Mute This Topic: https://lists.openembedded.org/mt/89528765/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] python3-native: Remove all pyc files
On Thu, 3 Mar 2022 at 16:34, Richard Purdie wrote: > This removes a further 1600 files from sstate handling and lets python > create the ones it wants at runtime which is likely much better overall > for performance. Playing devil's advocate: doesn't having them in sstate mean they're generated once and hardlinked, instead of needing to be generated for every recipe which runs pythonnative? Whilst I can't disagree that 1600 files being dropped from sstate is good, we're just punting the recompile step to every recipe when it runs python code. I guess the question here is how long does the Python library take to recompile. Ross -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162668): https://lists.openembedded.org/g/openembedded-core/message/162668 Mute This Topic: https://lists.openembedded.org/mt/89528765/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] python3-native: Remove all pyc files
On 03.03.22 18:11, Konrad Weihmann wrote:
On 03.03.22 17:34, Richard Purdie wrote:
This removes a further 1600 files from sstate handling and lets python
create the ones it wants at runtime which is likely much better overall
for performance.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/python/python3_3.10.2.bb | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3_3.10.2.bb
b/meta/recipes-devtools/python/python3_3.10.2.bb
index b28aa6505a0..7ec443a531f 100644
--- a/meta/recipes-devtools/python/python3_3.10.2.bb
+++ b/meta/recipes-devtools/python/python3_3.10.2.bb
@@ -156,7 +156,12 @@ do_install:append:class-native() {
# Remove the opt-1.pyc and opt-2.pyc files. There are over
3,000 of them
# and the overhead in each recipe-sysroot-native isn't worth
it, particularly
# when they're only used for python called with -O or -OO.
- find ${D} -name *opt-*.pyc -delete
+ #find ${D} -name *opt-*.pyc -delete
This here looks like a leftover - guess that could be removed.
Thx for finally making that happen (I've done the same for quite a while
in an extension in my setup) - I remember there was a bug about pyc
leading to weird staging issues, I opened up like a year or two.
Guess that one could be closed when this is merged
For reference: it's this bug here
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13868
+ # Remove all pyc files. There are a ton of them and it is
probably faster to let
+ # python create the ones it wants at runtime rather than
manage in the sstate
+ # tarballs and sysroot creation.
+ find ${D} -name *.pyc -delete
+
}
do_install:append() {
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162667):
https://lists.openembedded.org/g/openembedded-core/message/162667
Mute This Topic: https://lists.openembedded.org/mt/89528765/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] python3-native: Remove all pyc files
On 03.03.22 17:34, Richard Purdie wrote:
This removes a further 1600 files from sstate handling and lets python
create the ones it wants at runtime which is likely much better overall
for performance.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/python/python3_3.10.2.bb | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3_3.10.2.bb
b/meta/recipes-devtools/python/python3_3.10.2.bb
index b28aa6505a0..7ec443a531f 100644
--- a/meta/recipes-devtools/python/python3_3.10.2.bb
+++ b/meta/recipes-devtools/python/python3_3.10.2.bb
@@ -156,7 +156,12 @@ do_install:append:class-native() {
# Remove the opt-1.pyc and opt-2.pyc files. There are over 3,000 of
them
# and the overhead in each recipe-sysroot-native isn't worth it,
particularly
# when they're only used for python called with -O or -OO.
-find ${D} -name *opt-*.pyc -delete
+#find ${D} -name *opt-*.pyc -delete
This here looks like a leftover - guess that could be removed.
Thx for finally making that happen (I've done the same for quite a while
in an extension in my setup) - I remember there was a bug about pyc
leading to weird staging issues, I opened up like a year or two.
Guess that one could be closed when this is merged
+# Remove all pyc files. There are a ton of them and it is probably
faster to let
+# python create the ones it wants at runtime rather than manage in the
sstate
+# tarballs and sysroot creation.
+find ${D} -name *.pyc -delete
+
}
do_install:append() {
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162666):
https://lists.openembedded.org/g/openembedded-core/message/162666
Mute This Topic: https://lists.openembedded.org/mt/89528765/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/1] go.bbclass: Allow network in do_compile
On Thu, Mar 3, 2022 at 10:13 AM wrote: > > On Thu, Mar 3, 2022 at 04:34 AM, Bruce Ashfield wrote: > > On Wed, Mar 2, 2022 at 4:57 PM Andrei Gherzan wrote: > > > Mar 1, 2022 20:15:52 Bruce Ashfield : > > On Tue, Mar 1, 2022 at 10:54 AM wrote: > > On Tue, Mar 1, 2022 at 02:14 PM, Bruce Ashfield wrote: > > On Tue, Mar 1, 2022 at 6:42 AM Andrei Gherzan wrote: > > > On Tue, 1 Mar 2022, at 01:55, Bruce Ashfield wrote: > > On Mon, Feb 28, 2022 at 8:17 PM Bruce Ashfield via > lists.openembedded.org > wrote: > > > On Mon, Feb 28, 2022 at 6:54 PM Andrei Gherzan wrote: > > > From: Andrei Gherzan > > Compile pulls in the go.mod list requiring network. Without this, do > compile would fail with a similar error to the following: > > dial tcp: lookup proxy.golang.org: Temporary failure in name resolution > > This is something that needs to be carried in your own layers, IMHO it > isn't appropriate for core. > > It isn't about the fetching, it is the entire gap in functionality > that we are missing if go starts fetching dependencies during compile. > > A further thought is that if this is for go.mod issues, there is the > go-mod.bbclass. > > Perhaps enabling it in that class and doing a bbwarn about go fetching > dependencies would be appropriate ? > > Otherwise, someone may not know that this is happening and that a no > network configuration has no chance of working. > > I reckon that is reasonable. I'll personally go down the recipe level to > workaround this change but understanding and agreeing with the reasoning > behind this change, I want to invest a bit into trying to find a proper > solution in the core. Bruce, I know you invested a fair amount of time into > this already. Would you be willing to sync up and see how we can work > together in tackling this? > > Definitely, more ideas are good. In fact, I think there are probably > several approaches that can co-exist, depending on what a > recipe/developer needs. > > I'm in the Eastern time zone here, and will try and grab folks on IRC > to have a level set > > Bruce > > Added Zyga to CC as he is also interested in this as part of his go > development activities. > > Thanks, > Andrei > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II > > The problem in allowing downloads during compile (e.g. by go) is, that it > leads to non-reproducable builds. I'm currently facing the same issue and > would like to have a reproducable go *offline* build. > I would like to propose two ideas to workaround the go-compile fetching issue: > > First: > - Fetch go-dependencies using go.mod file from 'proxy.golang.org' (e.g. by > writing a seperate go fetcher or a wget-fetcher) and unpack the dependencies > into go projects 'vendor' folder. This forces go to compile offline. However, > one have to generate the 'modules.txt' file in the vendor folder 'manually' > during unpack. This is error prone, as there is no official documentation how > this format should look like. Anyway, I've tried this approach and it works > for me. > > Second: > - Fetch go-dependencies using go.mod file from 'proxy.golang.org' (e.g. by > writing a seperate go fetcher) and unpack the dependencies into a local > (workdir) go-path. This seemed a good solution for me as the go-path is well > defined. But for some reason 'go' fetches the zip-files during compile into > it's download-cache AGAIN, even if the source is already unpacked in the > go-path. I'll assume this is required to verify the source files integrity?! > With this approach one have to adapt 'go' to suppress this download behaviour. > > I've been doing offline builds using a constructed vendor/ directory > and generated modules.txt. > > The only difference between what I have working and what you are > suggesting (type 1), is that I've gone directly to the sources and > constructed the vendor directory using the OE git fetcher. That allows > all functionality to continue to work that is part of OEcore, and the > build to continue. Switching out the git fetches for tarballs would > be possible, I just wasn't sure how to use the proxied modules (and I > wanted the history for debug). > > I've never had any issues with the modules.txt, as I generate it at > the same time as the git fetch lines for the SRC_URI. I've also not > been using information from the go.mod directly from go.proxy.org, it > is information I've generated from a clone of the project and dumped > via go mod. There's likely improvements I can do there, but with what > I'm doing, I'm going directly to the source of the projects and doing > clones, which keeps everything clear of the go infrastructure. > > I have a utility that I'm still cleaning up that generates the SRC_URI > lines, as well as the modules.txt, when I resolve a few nagging > issues, I'll make the WIP scripts available. > > Other projects (BSD, etc), have been doing different sorts of >
[OE-core] [PATCH 2/2] python3: Drop opt1 and opt2 pyc files from target
These are only used with python when the -O or -OO options are passed
and I'm not aware of runtime use of that. They otherwise just waste a
ton of space.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/python/python3_3.10.2.bb | 5 +
1 file changed, 5 insertions(+)
diff --git a/meta/recipes-devtools/python/python3_3.10.2.bb
b/meta/recipes-devtools/python/python3_3.10.2.bb
index 7ec443a531f..97e74ceb688 100644
--- a/meta/recipes-devtools/python/python3_3.10.2.bb
+++ b/meta/recipes-devtools/python/python3_3.10.2.bb
@@ -189,6 +189,11 @@ do_install:append() {
# More info: http://benno.id.au/blog/2013/01/15/python-determinism
rm
${D}${libdir}/python${PYTHON_MAJMIN}/test/__pycache__/test_range.cpython*
rm
${D}${libdir}/python${PYTHON_MAJMIN}/test/__pycache__/test_xml_etree.cpython*
+
+# Remove the opt-1.pyc and opt-2.pyc files. They effectively waste
space on embedded
+# style targets as they're only used when python is called with the -O
or -OO options
+# which is rare.
+find ${D} -name *opt-*.pyc -delete
}
do_install:append:class-nativesdk () {
--
2.32.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162664):
https://lists.openembedded.org/g/openembedded-core/message/162664
Mute This Topic: https://lists.openembedded.org/mt/89528766/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/2] python3-native: Remove all pyc files
This removes a further 1600 files from sstate handling and lets python
create the ones it wants at runtime which is likely much better overall
for performance.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/python/python3_3.10.2.bb | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3_3.10.2.bb
b/meta/recipes-devtools/python/python3_3.10.2.bb
index b28aa6505a0..7ec443a531f 100644
--- a/meta/recipes-devtools/python/python3_3.10.2.bb
+++ b/meta/recipes-devtools/python/python3_3.10.2.bb
@@ -156,7 +156,12 @@ do_install:append:class-native() {
# Remove the opt-1.pyc and opt-2.pyc files. There are over 3,000 of
them
# and the overhead in each recipe-sysroot-native isn't worth it,
particularly
# when they're only used for python called with -O or -OO.
-find ${D} -name *opt-*.pyc -delete
+#find ${D} -name *opt-*.pyc -delete
+# Remove all pyc files. There are a ton of them and it is probably
faster to let
+# python create the ones it wants at runtime rather than manage in the
sstate
+# tarballs and sysroot creation.
+find ${D} -name *.pyc -delete
+
}
do_install:append() {
--
2.32.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162663):
https://lists.openembedded.org/g/openembedded-core/message/162663
Mute This Topic: https://lists.openembedded.org/mt/89528765/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] cmake-native: Remove help docs from the native sysroot
This drops the file count for cmake-native from ~3000 to ~1700
which is a decent chunk of files not to be copying to each native
sysroot for no reason.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/cmake/cmake-native_3.22.2.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-devtools/cmake/cmake-native_3.22.2.bb
b/meta/recipes-devtools/cmake/cmake-native_3.22.2.bb
index 335097d3872..8293fe5e561 100644
--- a/meta/recipes-devtools/cmake/cmake-native_3.22.2.bb
+++ b/meta/recipes-devtools/cmake/cmake-native_3.22.2.bb
@@ -46,6 +46,9 @@ do_install() {
install -m 644 ${WORKDIR}/OEToolchainConfig.cmake ${D}${datadir}/cmake/
mkdir -p ${D}${base_prefix}/environment-setup.d
install -m 644 ${WORKDIR}/environment.d-cmake.sh
${D}${base_prefix}/environment-setup.d/cmake.sh
+
+ # Help docs create tons of files in the native sysroot and aren't
needed there
+ rm -rf ${D}${datadir}/cmake-*/Help
}
do_compile[progress] = "percent"
--
2.32.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162662):
https://lists.openembedded.org/g/openembedded-core/message/162662
Mute This Topic: https://lists.openembedded.org/mt/89527172/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core] Listing numbers of files in native populate_sysroot installs
For info for people who've not seen this, you can list the number of files installed by native recipes that are present in the current build with: wc tmp/sstate-control/manifest-x86_64-*native*.populate_sysroot -l | sort -n which on my local build shows: 153 tmp/sstate-control/manifest-x86_64-alsa-lib-native.populate_sysroot 168 tmp/sstate-control/manifest-x86_64-ncurses-native.populate_sysroot 168 tmp/sstate-control/manifest-x86_64-xorgproto-native.populate_sysroot 180 tmp/sstate-control/manifest-x86_64-python3-setuptools-native.populate_sysroot 181 tmp/sstate-control/manifest-x86_64-openssl-native.populate_sysroot 208 tmp/sstate-control/manifest-x86_64-gobject-introspection-native.populate_sysroot 219 tmp/sstate-control/manifest-x86_64-docbook-xml-dtd4-native.populate_sysroot 231 tmp/sstate-control/manifest-x86_64-dpkg-native.populate_sysroot 266 tmp/sstate-control/manifest-x86_64-rpm-native.populate_sysroot 376 tmp/sstate-control/manifest-x86_64-glib-2.0-native.populate_sysroot 426 tmp/sstate-control/manifest-x86_64-perlcross-native.populate_sysroot 466 tmp/sstate-control/manifest-x86_64-meson-native.populate_sysroot 483 tmp/sstate-control/manifest-x86_64-icu-native.populate_sysroot 524 tmp/sstate-control/manifest-x86_64-gtk+3-native.populate_sysroot 585 tmp/sstate-control/manifest-x86_64-autoconf-archive-native.populate_sysroot 600 tmp/sstate-control/manifest-x86_64-python3-pip-native.populate_sysroot 748 tmp/sstate-control/manifest-x86_64-swig-native.populate_sysroot 850 tmp/sstate-control/manifest-x86_64-shared-mime-info-native.populate_sysroot 1945 tmp/sstate-control/manifest-x86_64-docbook-xsl-stylesheets-native.populate_sysroot 2005 tmp/sstate-control/manifest-x86_64-perl-native.populate_sysroot 2362 tmp/sstate-control/manifest-x86_64-python3-native.populate_sysroot 3035 tmp/sstate-control/manifest-x86_64-cmake-native.populate_sysroot 21246 total Removing cmake-native's help files would probably help next... Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162661): https://lists.openembedded.org/g/openembedded-core/message/162661 Mute This Topic: https://lists.openembedded.org/mt/89527138/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] buildhistory.bbclass: create the buildhistory directory when needed
Great, thanks!
Steve Sakoman escreveu no dia quinta, 3/03/2022 à(s)
14:49:
> On Wed, Mar 2, 2022 at 2:07 PM Jose Quaresma
> wrote:
> >
> > Can this patch be backported to dunfell?
>
> I've added it to my test queue.
>
> Steve
>
> >
> > Jose
> >
> > Jose Quaresma via lists.openembedded.org gmail@lists.openembedded.org> escreveu no dia quarta, 2/03/2022 à(s)
> 00:47:
> >>
> >> When the BUILDHISTORY_RESET is enabled we need to move the
> >> content from BUILDHISTORY_DIR to BUILDHISTORY_OLD_DIR but
> >> when we start a clean build in the first run we don't have the
> >> BUILDHISTORY_DIR so the move of files will fail.
> >>
> >> | ERROR: Command execution failed: Traceback (most recent call last):
> >> | File "/xxx/poky/bitbake/lib/bb/command.py", line 110, in
> runAsyncCommand
> >> |commandmethod(self.cmds_async, self, options)
> >> | File "/xxx/poky/bitbake/lib/bb/command.py", line 564, in buildTargets
> >> |command.cooker.buildTargets(pkgs_to_build, task)
> >> | File "/xxx/poky/bitbake/lib/bb/cooker.py", line 1481, in buildTargets
> >> |bb.event.fire(bb.event.BuildStarted(buildname, ntargets),
> self.databuilder.mcdata[mc])
> >> | File "/xxx/home/builder/src/base/poky/bitbake/lib/bb/event.py", line
> 214, in fire
> >> |fire_class_handlers(event, d)
> >> | File "/xxx/poky/bitbake/lib/bb/event.py", line 121, in
> fire_class_handlers
> >> |execute_handler(name, handler, event, d)
> >> | File "/xxx/poky/bitbake/lib/bb/event.py", line 93, in execute_handler
> >> |ret = handler(event)
> >> | File "/xxx/poky/meta/classes/buildhistory.bbclass", line 919, in
> buildhistory_eventhandler
> >> |entries = [ x for x in os.listdir(rootdir) if not
> x.startswith('.') ]
> >> | FileNotFoundError: [Errno 2] No such file or directory:
> '/xxx/buildhistory'
> >>
> >> Signed-off-by: Jose Quaresma
> >> ---
> >> V2: remove the check to see if the directory exists
> >>
> >> meta/classes/buildhistory.bbclass | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/meta/classes/buildhistory.bbclass
> b/meta/classes/buildhistory.bbclass
> >> index 49797a6701..8db79a4829 100644
> >> --- a/meta/classes/buildhistory.bbclass
> >> +++ b/meta/classes/buildhistory.bbclass
> >> @@ -896,6 +896,7 @@ python buildhistory_eventhandler() {
> >> if os.path.isdir(olddir):
> >> shutil.rmtree(olddir)
> >> rootdir = e.data.getVar("BUILDHISTORY_DIR")
> >> +bb.utils.mkdirhier(rootdir)
> >> entries = [ x for x in os.listdir(rootdir) if not
> x.startswith('.') ]
> >> bb.utils.mkdirhier(olddir)
> >> for entry in entries:
> >> --
> >> 2.35.1
> >>
> >>
> >>
> >>
> >
> >
> > --
> > Best regards,
> >
> > José Quaresma
>
--
Best regards,
José Quaresma
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162660):
https://lists.openembedded.org/g/openembedded-core/message/162660
Mute This Topic: https://lists.openembedded.org/mt/89491842/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] python3-native: Drop opt-1 and opt-2 pyc files
Richard Purdie escreveu no dia quinta,
3/03/2022 à(s) 14:37:
> On Thu, 2022-03-03 at 14:28 +, Richard Purdie via
> lists.openembedded.org
> wrote:
> > There are over 3,000 of these in python3-native (of 8,000+ files total)
> and
> > copying them to sysroots all the time seems pointless, particularly since
> > they're only used if python is run with the -O or -OO parameters.
> >
> > Get rid of them and save the overhead. This is particularly pronounced in
> > builds using the api-documentation distro feature.
> >
> > Signed-off-by: Richard Purdie
> > ---
> > meta/recipes-devtools/python/python3_3.10.2.bb | 5 +
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/meta/recipes-devtools/python/python3_3.10.2.bb
> b/meta/recipes-devtools/python/python3_3.10.2.bb
> > index 429839b6226..b28aa6505a0 100644
> > --- a/meta/recipes-devtools/python/python3_3.10.2.bb
> > +++ b/meta/recipes-devtools/python/python3_3.10.2.bb
> > @@ -152,6 +152,11 @@ do_install:append:class-native() {
> > # (these often end up too long for the #! parser in the kernel
> as the
> > # buffer is 128 bytes long).
> > ln -s python3-native/python3 ${D}${bindir}/nativepython3
> > +
> > +# Remove the opt-1.pyc and opt-2.pyc files. There are over
> 3,000 of them
> > +# and the overhead in each recipe-sysroot-native isn't worth
> it, particularly
> > +# when they're only used for python called with -O or -OO.
> > +find ${D} -name *opt-*.pyc -delete
> > }
> >
> > do_install:append() {
> >
>
> This does pose an interesting dilemma. We could just go this far, or
> should we
> remove the remaining pyc files (~1,500 of them) and let python create them
> as
> needed, or do we disable them from python entirely?
>
I think that for native recipes it can be created at runtime as needed.
Jose
> Cheers,
>
> Richard
>
>
>
>
>
>
--
Best regards,
José Quaresma
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162659):
https://lists.openembedded.org/g/openembedded-core/message/162659
Mute This Topic: https://lists.openembedded.org/mt/89525809/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/1] go.bbclass: Allow network in do_compile
On Thu, Mar 3, 2022 at 04:34 AM, Bruce Ashfield wrote: > > On Wed, Mar 2, 2022 at 4:57 PM Andrei Gherzan wrote: > >> >> Mar 1, 2022 20:15:52 Bruce Ashfield : >> >> >>> On Tue, Mar 1, 2022 at 10:54 AM wrote: >>> On Tue, Mar 1, 2022 at 02:14 PM, Bruce Ashfield wrote: On Tue, Mar 1, 2022 at 6:42 AM Andrei Gherzan wrote: On Tue, 1 Mar 2022, at 01:55, Bruce Ashfield wrote: On Mon, Feb 28, 2022 at 8:17 PM Bruce Ashfield via lists.openembedded.org wrote: On Mon, Feb 28, 2022 at 6:54 PM Andrei Gherzan wrote: From: Andrei Gherzan Compile pulls in the go.mod list requiring network. Without this, do compile would fail with a similar error to the following: dial tcp: lookup proxy.golang.org: Temporary failure in name resolution This is something that needs to be carried in your own layers, IMHO it isn't appropriate for core. It isn't about the fetching, it is the entire gap in functionality that we are missing if go starts fetching dependencies during compile. A further thought is that if this is for go.mod issues, there is the go-mod.bbclass. Perhaps enabling it in that class and doing a bbwarn about go fetching dependencies would be appropriate ? Otherwise, someone may not know that this is happening and that a no network configuration has no chance of working. I reckon that is reasonable. I'll personally go down the recipe level to workaround this change but understanding and agreeing with the reasoning behind this change, I want to invest a bit into trying to find a proper solution in the core. Bruce, I know you invested a fair amount of time into this already. Would you be willing to sync up and see how we can work together in tackling this? Definitely, more ideas are good. In fact, I think there are probably several approaches that can co-exist, depending on what a recipe/developer needs. I'm in the Eastern time zone here, and will try and grab folks on IRC to have a level set Bruce Added Zyga to CC as he is also interested in this as part of his go development activities. Thanks, Andrei -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II The problem in allowing downloads during compile (e.g. by go) is, that it leads to non-reproducable builds. I'm currently facing the same issue and would like to have a reproducable go *offline* build. I would like to propose two ideas to workaround the go-compile fetching issue: First: - Fetch go-dependencies using go.mod file from 'proxy.golang.org' (e.g. by writing a seperate go fetcher or a wget-fetcher) and unpack the dependencies into go projects 'vendor' folder. This forces go to compile offline. However, one have to generate the 'modules.txt' file in the vendor folder 'manually' during unpack. This is error prone, as there is no official documentation how this format should look like. Anyway, I've tried this approach and it works for me. Second: - Fetch go-dependencies using go.mod file from 'proxy.golang.org' (e.g. by writing a seperate go fetcher) and unpack the dependencies into a local (workdir) go-path. This seemed a good solution for me as the go-path is well defined. But for some reason 'go' fetches the zip-files during compile into it's download-cache AGAIN, even if the source is already unpacked in the go-path. I'll assume this is required to verify the source files integrity?! With this approach one have to adapt 'go' to suppress this download behaviour. >>> >>> I've been doing offline builds using a constructed vendor/ directory >>> and generated modules.txt. >>> >>> The only difference between what I have working and what you are >>> suggesting (type 1), is that I've gone directly to the sources and >>> constructed the vendor directory using the OE git fetcher. That allows >>> all functionality to continue to work that is part of OEcore, and the >>> build to continue. Switching out the git fetches for tarballs would >>> be possible, I just wasn't sure how to use the proxied modules (and I >>> wanted the history for debug). >>> >>> I've never had any issues with the modules.txt, as I generate it at >>> the same time as the git fetch lines for the SRC_URI. I've also not >>> been using information from the go.mod directly from go.proxy.org, it >>> is information I've generated from a clone of the project and dumped >>> via go mod. There's likely improvements I can do there, but with what >>> I'm doing, I'm going directly to the source of the projects and doing >>> clones, which keeps
Re: [OE-core] [PATCH v2] buildhistory.bbclass: create the buildhistory directory when needed
On Wed, Mar 2, 2022 at 2:07 PM Jose Quaresma wrote:
>
> Can this patch be backported to dunfell?
I've added it to my test queue.
Steve
>
> Jose
>
> Jose Quaresma via lists.openembedded.org
> escreveu no dia quarta,
> 2/03/2022 à(s) 00:47:
>>
>> When the BUILDHISTORY_RESET is enabled we need to move the
>> content from BUILDHISTORY_DIR to BUILDHISTORY_OLD_DIR but
>> when we start a clean build in the first run we don't have the
>> BUILDHISTORY_DIR so the move of files will fail.
>>
>> | ERROR: Command execution failed: Traceback (most recent call last):
>> | File "/xxx/poky/bitbake/lib/bb/command.py", line 110, in runAsyncCommand
>> |commandmethod(self.cmds_async, self, options)
>> | File "/xxx/poky/bitbake/lib/bb/command.py", line 564, in buildTargets
>> |command.cooker.buildTargets(pkgs_to_build, task)
>> | File "/xxx/poky/bitbake/lib/bb/cooker.py", line 1481, in buildTargets
>> |bb.event.fire(bb.event.BuildStarted(buildname, ntargets),
>> self.databuilder.mcdata[mc])
>> | File "/xxx/home/builder/src/base/poky/bitbake/lib/bb/event.py", line 214,
>> in fire
>> |fire_class_handlers(event, d)
>> | File "/xxx/poky/bitbake/lib/bb/event.py", line 121, in fire_class_handlers
>> |execute_handler(name, handler, event, d)
>> | File "/xxx/poky/bitbake/lib/bb/event.py", line 93, in execute_handler
>> |ret = handler(event)
>> | File "/xxx/poky/meta/classes/buildhistory.bbclass", line 919, in
>> buildhistory_eventhandler
>> |entries = [ x for x in os.listdir(rootdir) if not x.startswith('.') ]
>> | FileNotFoundError: [Errno 2] No such file or directory: '/xxx/buildhistory'
>>
>> Signed-off-by: Jose Quaresma
>> ---
>> V2: remove the check to see if the directory exists
>>
>> meta/classes/buildhistory.bbclass | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/meta/classes/buildhistory.bbclass
>> b/meta/classes/buildhistory.bbclass
>> index 49797a6701..8db79a4829 100644
>> --- a/meta/classes/buildhistory.bbclass
>> +++ b/meta/classes/buildhistory.bbclass
>> @@ -896,6 +896,7 @@ python buildhistory_eventhandler() {
>> if os.path.isdir(olddir):
>> shutil.rmtree(olddir)
>> rootdir = e.data.getVar("BUILDHISTORY_DIR")
>> +bb.utils.mkdirhier(rootdir)
>> entries = [ x for x in os.listdir(rootdir) if not
>> x.startswith('.') ]
>> bb.utils.mkdirhier(olddir)
>> for entry in entries:
>> --
>> 2.35.1
>>
>>
>>
>>
>
>
> --
> Best regards,
>
> José Quaresma
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162657):
https://lists.openembedded.org/g/openembedded-core/message/162657
Mute This Topic: https://lists.openembedded.org/mt/89491842/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] python3-native: Drop opt-1 and opt-2 pyc files
On Thu, 2022-03-03 at 14:28 +, Richard Purdie via lists.openembedded.org
wrote:
> There are over 3,000 of these in python3-native (of 8,000+ files total) and
> copying them to sysroots all the time seems pointless, particularly since
> they're only used if python is run with the -O or -OO parameters.
>
> Get rid of them and save the overhead. This is particularly pronounced in
> builds using the api-documentation distro feature.
>
> Signed-off-by: Richard Purdie
> ---
> meta/recipes-devtools/python/python3_3.10.2.bb | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/meta/recipes-devtools/python/python3_3.10.2.bb
> b/meta/recipes-devtools/python/python3_3.10.2.bb
> index 429839b6226..b28aa6505a0 100644
> --- a/meta/recipes-devtools/python/python3_3.10.2.bb
> +++ b/meta/recipes-devtools/python/python3_3.10.2.bb
> @@ -152,6 +152,11 @@ do_install:append:class-native() {
> # (these often end up too long for the #! parser in the kernel as the
> # buffer is 128 bytes long).
> ln -s python3-native/python3 ${D}${bindir}/nativepython3
> +
> +# Remove the opt-1.pyc and opt-2.pyc files. There are over 3,000 of
> them
> +# and the overhead in each recipe-sysroot-native isn't worth it,
> particularly
> +# when they're only used for python called with -O or -OO.
> +find ${D} -name *opt-*.pyc -delete
> }
>
> do_install:append() {
>
This does pose an interesting dilemma. We could just go this far, or should we
remove the remaining pyc files (~1,500 of them) and let python create them as
needed, or do we disable them from python entirely?
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162656):
https://lists.openembedded.org/g/openembedded-core/message/162656
Mute This Topic: https://lists.openembedded.org/mt/89525809/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] python3-native: Drop opt-1 and opt-2 pyc files
There are over 3,000 of these in python3-native (of 8,000+ files total) and
copying them to sysroots all the time seems pointless, particularly since
they're only used if python is run with the -O or -OO parameters.
Get rid of them and save the overhead. This is particularly pronounced in
builds using the api-documentation distro feature.
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/python/python3_3.10.2.bb | 5 +
1 file changed, 5 insertions(+)
diff --git a/meta/recipes-devtools/python/python3_3.10.2.bb
b/meta/recipes-devtools/python/python3_3.10.2.bb
index 429839b6226..b28aa6505a0 100644
--- a/meta/recipes-devtools/python/python3_3.10.2.bb
+++ b/meta/recipes-devtools/python/python3_3.10.2.bb
@@ -152,6 +152,11 @@ do_install:append:class-native() {
# (these often end up too long for the #! parser in the kernel as the
# buffer is 128 bytes long).
ln -s python3-native/python3 ${D}${bindir}/nativepython3
+
+# Remove the opt-1.pyc and opt-2.pyc files. There are over 3,000 of
them
+# and the overhead in each recipe-sysroot-native isn't worth it,
particularly
+# when they're only used for python called with -O or -OO.
+find ${D} -name *opt-*.pyc -delete
}
do_install:append() {
--
2.32.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162655):
https://lists.openembedded.org/g/openembedded-core/message/162655
Mute This Topic: https://lists.openembedded.org/mt/89525809/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/1] go.bbclass: Allow network in do_compile
On Thu, 3 Mar 2022, at 03:34, Bruce Ashfield wrote: > On Wed, Mar 2, 2022 at 4:57 PM Andrei Gherzan wrote: >> >> >> Mar 1, 2022 20:15:52 Bruce Ashfield : >> >> > On Tue, Mar 1, 2022 at 10:54 AM wrote: >> >> >> >> On Tue, Mar 1, 2022 at 02:14 PM, Bruce Ashfield wrote: >> >> >> >> On Tue, Mar 1, 2022 at 6:42 AM Andrei Gherzan wrote: >> >> >> >> >> >> On Tue, 1 Mar 2022, at 01:55, Bruce Ashfield wrote: >> >> >> >> On Mon, Feb 28, 2022 at 8:17 PM Bruce Ashfield via >> >> lists.openembedded.org >> >> wrote: >> >> >> >> >> >> On Mon, Feb 28, 2022 at 6:54 PM Andrei Gherzan wrote: >> >> >> >> >> >> From: Andrei Gherzan >> >> >> >> Compile pulls in the go.mod list requiring network. Without this, do >> >> compile would fail with a similar error to the following: >> >> >> >> dial tcp: lookup proxy.golang.org: Temporary failure in name resolution >> >> >> >> This is something that needs to be carried in your own layers, IMHO it >> >> isn't appropriate for core. >> >> >> >> It isn't about the fetching, it is the entire gap in functionality >> >> that we are missing if go starts fetching dependencies during compile. >> >> >> >> A further thought is that if this is for go.mod issues, there is the >> >> go-mod.bbclass. >> >> >> >> Perhaps enabling it in that class and doing a bbwarn about go fetching >> >> dependencies would be appropriate ? >> >> >> >> Otherwise, someone may not know that this is happening and that a no >> >> network configuration has no chance of working. >> >> >> >> I reckon that is reasonable. I'll personally go down the recipe level to >> >> workaround this change but understanding and agreeing with the reasoning >> >> behind this change, I want to invest a bit into trying to find a proper >> >> solution in the core. Bruce, I know you invested a fair amount of time >> >> into this already. Would you be willing to sync up and see how we can >> >> work together in tackling this? >> >> >> >> Definitely, more ideas are good. In fact, I think there are probably >> >> several approaches that can co-exist, depending on what a >> >> recipe/developer needs. >> >> >> >> I'm in the Eastern time zone here, and will try and grab folks on IRC >> >> to have a level set >> >> >> >> Bruce >> >> >> >> Added Zyga to CC as he is also interested in this as part of his go >> >> development activities. >> >> >> >> Thanks, >> >> Andrei >> >> >> >> >> >> >> >> -- >> >> - Thou shalt not follow the NULL pointer, for chaos and madness await >> >> thee at its end >> >> - "Use the force Harry" - Gandalf, Star Trek II >> >> >> >> The problem in allowing downloads during compile (e.g. by go) is, that it >> >> leads to non-reproducable builds. I'm currently facing the same issue and >> >> would like to have a reproducable go *offline* build. >> >> I would like to propose two ideas to workaround the go-compile fetching >> >> issue: >> >> >> >> First: >> >> - Fetch go-dependencies using go.mod file from 'proxy.golang.org' (e.g. >> >> by writing a seperate go fetcher or a wget-fetcher) and unpack the >> >> dependencies into go projects 'vendor' folder. This forces go to compile >> >> offline. However, one have to generate the 'modules.txt' file in the >> >> vendor folder 'manually' during unpack. This is error prone, as there is >> >> no official documentation how this format should look like. Anyway, I've >> >> tried this approach and it works for me. >> >> >> >> Second: >> >> - Fetch go-dependencies using go.mod file from 'proxy.golang.org' (e.g. >> >> by writing a seperate go fetcher) and unpack the dependencies into a >> >> local (workdir) go-path. This seemed a good solution for me as the >> >> go-path is well defined. But for some reason 'go' fetches the zip-files >> >> during compile into it's download-cache AGAIN, even if the source is >> >> already unpacked in the go-path. I'll assume this is required to verify >> >> the source files integrity?! With this approach one have to adapt 'go' to >> >> suppress this download behaviour. >> >> >> > >> > I've been doing offline builds using a constructed vendor/ directory >> > and generated modules.txt. >> > >> > The only difference between what I have working and what you are >> > suggesting (type 1), is that I've gone directly to the sources and >> > constructed the vendor directory using the OE git fetcher. That allows >> > all functionality to continue to work that is part of OEcore, and the >> > build to continue. Switching out the git fetches for tarballs would >> > be possible, I just wasn't sure how to use the proxied modules (and I >> > wanted the history for debug). >> > >> > I've never had any issues with the modules.txt, as I generate it at >> > the same time as the git fetch lines for the SRC_URI. I've also not >> > been using information from the go.mod directly from go.proxy.org, it >> > is information I've generated from a clone of the project and dumped >> > via go mod. There's likely improvements I can do there, but with what >> > I'm
Re: [OE-core] [PATCH 1/2] cve-check: get_cve_info should open the database read-only
This one is odd...
After scrolling through the log that I can get from a github pipeline
(sorry no runner log available) - I noticed
2022-03-03T05:39:23.2334189Z WARNING: cve-update-db-native-1.0-r0
do_fetch: Failed to fetch CVE data ([Errno 99] Cannot assign requested
address)
2022-03-03T05:39:23.2569941Z NOTE: recipe cve-update-db-native-1.0-r0:
task do_fetch: Succeeded
and then do_cve_check run on that recipe
2022-03-03T05:39:56.6239005Z NOTE: Running task 4428 of 5120
(/opt/build/sources/poky/meta/recipes-core/meta/cve-update-db-native.bb:do_cve_check)
before failing with 2022-03-03T05:39:56.8063851Z Exception:
sqlite3.OperationalError: attempt to write a readonly database
this doesn't look right to me - maybe there's something special about my
settings - I will try to recreate that locally
On 03.03.22 12:27, Ross Burton wrote:
:tableflip:
Thanks, I guess!
Can you share the full bitbake log from that run? I'd like to see what
jobs are running in parallel.
Ross
On Thu, 3 Mar 2022 at 11:10, Konrad Weihmann wrote:
Single from scratch build of core-image-minimal
On 03.03.22 12:07, Ross Burton wrote:
What's the scenario where this is happening? Multiple build
directories using the same DL_DIR? Or was this a single build?
Ross
On Thu, 3 Mar 2022 at 08:10, Konrad Weihmann wrote:
Sadly I encountered this here last night
NOTE: recipe cve-update-db-native-1.0-r0: task do_cve_check: Started
ERROR: cve-update-db-native-1.0-r0 do_cve_check: Error executing a
python function in exec_func_python() autogenerated:
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_func_python() autogenerated', lineno: 2, function:
0001:
*** 0002:do_cve_check(d)
0003:
File: '/opt/build/sources/poky/meta/classes/cve-check.bbclass', lineno:
104, function: do_cve_check
0100:try:
0101:patched_cves = get_patched_cves(d)
0102:except FileNotFoundError:
0103:bb.fatal("Failure in searching patches")
*** 0104:whitelisted, patched, unpatched = check_cves(d,
patched_cves)
0105:if patched or unpatched:
0106:cve_data = get_cve_info(d, patched + unpatched)
0107:cve_write_data(d, patched, unpatched,
whitelisted, cve_data)
0108:else:
File: '/opt/build/sources/poky/meta/classes/cve-check.bbclass', lineno:
198, function: check_cves
0194:else:
0195:vendor = "%"
0196:
0197:# Find all relevant CVE IDs.
*** 0198:for cverow in conn.execute("SELECT DISTINCT ID FROM
PRODUCTS WHERE PRODUCT IS ? AND VENDOR LIKE ?", (product, vendor)):
0199:cve = cverow[0]
0200:
0201:if cve in cve_whitelist:
0202:bb.note("%s-%s has been whitelisted for %s" %
(product, pv, cve))
Exception: sqlite3.OperationalError: attempt to write a readonly database
So it seems your patch doesn't solve the issue
On 23.02.22 13:54, Ross Burton wrote:
All of the function in cve-check should open the database read-only, as
the only writer is the fetch task in cve-update-db. However,
get_cve_info() was failing to do this, which might be causing locking
issues with sqlite.
Signed-off-by: Ross Burton
---
meta/classes/cve-check.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 2d69aeba4b..d715fbf4d8 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -265,7 +265,8 @@ def get_cve_info(d, cves):
import sqlite3
cve_data = {}
-conn = sqlite3.connect(d.getVar("CVE_CHECK_DB_FILE"))
+db_file = d.expand("file:${CVE_CHECK_DB_FILE}?mode=ro")
+conn = sqlite3.connect(db_file, uri=True)
for cve in cves:
for row in conn.execute("SELECT * FROM NVD WHERE ID IS ?", (cve,)):
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162653):
https://lists.openembedded.org/g/openembedded-core/message/162653
Mute This Topic: https://lists.openembedded.org/mt/89339702/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] cve-check: get_cve_info should open the database read-only
:tableflip:
Thanks, I guess!
Can you share the full bitbake log from that run? I'd like to see what
jobs are running in parallel.
Ross
On Thu, 3 Mar 2022 at 11:10, Konrad Weihmann wrote:
>
> Single from scratch build of core-image-minimal
>
> On 03.03.22 12:07, Ross Burton wrote:
> > What's the scenario where this is happening? Multiple build
> > directories using the same DL_DIR? Or was this a single build?
> >
> > Ross
> >
> > On Thu, 3 Mar 2022 at 08:10, Konrad Weihmann wrote:
> >>
> >> Sadly I encountered this here last night
> >>
> >> NOTE: recipe cve-update-db-native-1.0-r0: task do_cve_check: Started
> >> ERROR: cve-update-db-native-1.0-r0 do_cve_check: Error executing a
> >> python function in exec_func_python() autogenerated:
> >>
> >> The stack trace of python calls that resulted in this exception/failure
> >> was:
> >> File: 'exec_func_python() autogenerated', lineno: 2, function:
> >>0001:
> >>*** 0002:do_cve_check(d)
> >>0003:
> >> File: '/opt/build/sources/poky/meta/classes/cve-check.bbclass', lineno:
> >> 104, function: do_cve_check
> >>0100:try:
> >>0101:patched_cves = get_patched_cves(d)
> >>0102:except FileNotFoundError:
> >>0103:bb.fatal("Failure in searching patches")
> >>*** 0104:whitelisted, patched, unpatched = check_cves(d,
> >> patched_cves)
> >>0105:if patched or unpatched:
> >>0106:cve_data = get_cve_info(d, patched + unpatched)
> >>0107:cve_write_data(d, patched, unpatched,
> >> whitelisted, cve_data)
> >>0108:else:
> >> File: '/opt/build/sources/poky/meta/classes/cve-check.bbclass', lineno:
> >> 198, function: check_cves
> >>0194:else:
> >>0195:vendor = "%"
> >>0196:
> >>0197:# Find all relevant CVE IDs.
> >>*** 0198:for cverow in conn.execute("SELECT DISTINCT ID FROM
> >> PRODUCTS WHERE PRODUCT IS ? AND VENDOR LIKE ?", (product, vendor)):
> >>0199:cve = cverow[0]
> >>0200:
> >>0201:if cve in cve_whitelist:
> >>0202:bb.note("%s-%s has been whitelisted for %s" %
> >> (product, pv, cve))
> >> Exception: sqlite3.OperationalError: attempt to write a readonly database
> >>
> >> So it seems your patch doesn't solve the issue
> >>
> >>
> >>
> >> On 23.02.22 13:54, Ross Burton wrote:
> >>> All of the function in cve-check should open the database read-only, as
> >>> the only writer is the fetch task in cve-update-db. However,
> >>> get_cve_info() was failing to do this, which might be causing locking
> >>> issues with sqlite.
> >>>
> >>> Signed-off-by: Ross Burton
> >>> ---
> >>>meta/classes/cve-check.bbclass | 3 ++-
> >>>1 file changed, 2 insertions(+), 1 deletion(-)
> >>>
> >>> diff --git a/meta/classes/cve-check.bbclass
> >>> b/meta/classes/cve-check.bbclass
> >>> index 2d69aeba4b..d715fbf4d8 100644
> >>> --- a/meta/classes/cve-check.bbclass
> >>> +++ b/meta/classes/cve-check.bbclass
> >>> @@ -265,7 +265,8 @@ def get_cve_info(d, cves):
> >>>import sqlite3
> >>>
> >>>cve_data = {}
> >>> -conn = sqlite3.connect(d.getVar("CVE_CHECK_DB_FILE"))
> >>> +db_file = d.expand("file:${CVE_CHECK_DB_FILE}?mode=ro")
> >>> +conn = sqlite3.connect(db_file, uri=True)
> >>>
> >>>for cve in cves:
> >>>for row in conn.execute("SELECT * FROM NVD WHERE ID IS ?",
> >>> (cve,)):
> >>>
> >>>
> >>>
> >>>
> >>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162652):
https://lists.openembedded.org/g/openembedded-core/message/162652
Mute This Topic: https://lists.openembedded.org/mt/89339702/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] [meta-oe][PATCH v2] libsndfile1: bump to version 1.0.31
On Thu, 2022-03-03 at 12:54 +0200, Alexandru Ardelean wrote: > It didn't look [to me] like it would be too bad to me either. > I wasn't sure what the decision would have been (from OE), to > [1]patch-out libopus? or to [2]add libopus? or [3]revert? > But your patch suggests [1] is preferred for now. My reasoning is that: * libopus is in meta-openembedded, I'm not sure we have a strong case for moving it to core. * I was happy to see us move to a recent more up to date version with the CVE patches dropped so reverting seemed like a less attractive option too. I just wasn't sure if patching out libopus would be possible or not. I therefore had a look at a patch to do it and that shows it does seem to be reasonable. > Did you get a chance to test it? > I can run a test on my system with it. > But it may take me 1-2 days. I've turned it into a proper patch and will test it on the autobuilder. > In the meantime, I was a bit busy with this: > https://github.com/libsndfile/libsndfile/pull/812 > > It kind of seems that libsndfile people are talking about maybe > splitting up their configuration. > Let's see. That will be in a future release anyway. Thanks for discussing it with them. If upstream were willing to accept a patch to enable/disable opus, that would be our much preferred way to handle this! Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162651): https://lists.openembedded.org/g/openembedded-core/message/162651 Mute This Topic: https://lists.openembedded.org/mt/89367260/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] libsndfile: Fix missing external library support
The recent upgrade regressed codec support since opus is missing and
this caused several codecs to be disabled. Add a patch to work around
the issue whilst it is discussed with upstream.
Signed-off-by: Richard Purdie
---
.../libsndfile/libsndfile1/noopus.patch | 55 +++
.../libsndfile/libsndfile1_1.0.31.bb | 1 +
2 files changed, 56 insertions(+)
create mode 100644 meta/recipes-multimedia/libsndfile/libsndfile1/noopus.patch
diff --git a/meta/recipes-multimedia/libsndfile/libsndfile1/noopus.patch
b/meta/recipes-multimedia/libsndfile/libsndfile1/noopus.patch
new file mode 100644
index 000..6bcb9324298
--- /dev/null
+++ b/meta/recipes-multimedia/libsndfile/libsndfile1/noopus.patch
@@ -0,0 +1,55 @@
+We don't have opus in OE-Core which causes all the external libs to be
disabled
+silently. The silent issue is discussed in the link below and hints a patch
+to make things configurable may be accepted.
+
+This patch removing the opus piece at least gets most of the functionality
+we previously used back whilst the issue is discussed.
+
+Upstream-Status: Pending [https://github.com/libsndfile/libsndfile/pull/812]
+
+Signed-off-by: Richard Purdie
+
+Index: libsndfile-1.0.31/configure.ac
+===
+--- libsndfile-1.0.31.orig/configure.ac
libsndfile-1.0.31/configure.ac
+@@ -361,13 +361,13 @@ AS_IF([test -n "$PKG_CONFIG"], [
+ enable_external_libs=yes
+ ])
+
+- AS_IF([test
"x$ac_cv_flac$ac_cv_ogg$ac_cv_vorbis$ac_cv_vorbisenc$ac_cv_opus" =
"xyesyesyesyesyes"], [
++ AS_IF([test
"x$ac_cv_flac$ac_cv_ogg$ac_cv_vorbis$ac_cv_vorbisenc" = "xyesyesyesyes"], [
+ HAVE_EXTERNAL_XIPH_LIBS=1
+ enable_external_libs=yes
+
+- EXTERNAL_XIPH_CFLAGS="$FLAC_CFLAGS
$VORBIS_CFLAGS $VORBISENC_CFLAGS $SPEEX_CFLAGS $OPUS_CFLAGS $OGG_CFLAGS "
+- EXTERNAL_XIPH_LIBS="$FLAC_LIBS
$VORBIS_LIBS $VORBISENC_LIBS $SPEEX_LIBS $OPUS_LIBS $OGG_LIBS "
+- EXTERNAL_XIPH_REQUIRE="flac ogg vorbis
vorbisenc opus"
++ EXTERNAL_XIPH_CFLAGS="$FLAC_CFLAGS
$VORBIS_CFLAGS $VORBISENC_CFLAGS $SPEEX_CFLAGS $OGG_CFLAGS "
++ EXTERNAL_XIPH_LIBS="$FLAC_LIBS
$VORBIS_LIBS $VORBISENC_LIBS $SPEEX_LIBS $OGG_LIBS "
++ EXTERNAL_XIPH_REQUIRE="flac ogg vorbis
vorbisenc"
+
+ if test x$ac_cv_speex = "xyes" ; then
+
EXTERNAL_XIPH_REQUIRE="$EXTERNAL_XIPH_REQUIRE speex"
+@@ -716,7 +716,7 @@ AC_MSG_RESULT([
+
+ Experimental code : ... ${enable_experimental:-no}
+ Using ALSA in example programs : .. ${enable_alsa:-no}
+-External FLAC/Ogg/Vorbis/Opus : ... ${enable_external_libs:-no}
++External FLAC/Ogg/Vorbis : ... ${enable_external_libs:-no}
+ Building Octave interface : ... ${OCTAVE_BUILD}
+
+ Tools :
+Index: libsndfile-1.0.31/src/ogg_opus.c
+===
+--- libsndfile-1.0.31.orig/src/ogg_opus.c
libsndfile-1.0.31/src/ogg_opus.c
+@@ -159,7 +159,7 @@
+ #include "sfendian.h"
+ #include "common.h"
+
+-#if HAVE_EXTERNAL_XIPH_LIBS
++#if 0
+
+ #include
+ #include
diff --git a/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.31.bb
b/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.31.bb
index 9f1a106600b..ea14fe29cb5 100644
--- a/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.31.bb
+++ b/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.31.bb
@@ -9,6 +9,7 @@ SECTION = "libs/multimedia"
LICENSE = "LGPL-2.1-only"
SRC_URI =
"https://github.com/libsndfile/libsndfile/releases/download/${PV}/libsndfile-${PV}.tar.bz2
\
+ file://noopus.patch \
"
UPSTREAM_CHECK_URI = "https://github.com/libsndfile/libsndfile/releases/;
--
2.32.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162650):
https://lists.openembedded.org/g/openembedded-core/message/162650
Mute This Topic: https://lists.openembedded.org/mt/89522896/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] cve-check: get_cve_info should open the database read-only
Single from scratch build of core-image-minimal
On 03.03.22 12:07, Ross Burton wrote:
What's the scenario where this is happening? Multiple build
directories using the same DL_DIR? Or was this a single build?
Ross
On Thu, 3 Mar 2022 at 08:10, Konrad Weihmann wrote:
Sadly I encountered this here last night
NOTE: recipe cve-update-db-native-1.0-r0: task do_cve_check: Started
ERROR: cve-update-db-native-1.0-r0 do_cve_check: Error executing a
python function in exec_func_python() autogenerated:
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_func_python() autogenerated', lineno: 2, function:
0001:
*** 0002:do_cve_check(d)
0003:
File: '/opt/build/sources/poky/meta/classes/cve-check.bbclass', lineno:
104, function: do_cve_check
0100:try:
0101:patched_cves = get_patched_cves(d)
0102:except FileNotFoundError:
0103:bb.fatal("Failure in searching patches")
*** 0104:whitelisted, patched, unpatched = check_cves(d,
patched_cves)
0105:if patched or unpatched:
0106:cve_data = get_cve_info(d, patched + unpatched)
0107:cve_write_data(d, patched, unpatched,
whitelisted, cve_data)
0108:else:
File: '/opt/build/sources/poky/meta/classes/cve-check.bbclass', lineno:
198, function: check_cves
0194:else:
0195:vendor = "%"
0196:
0197:# Find all relevant CVE IDs.
*** 0198:for cverow in conn.execute("SELECT DISTINCT ID FROM
PRODUCTS WHERE PRODUCT IS ? AND VENDOR LIKE ?", (product, vendor)):
0199:cve = cverow[0]
0200:
0201:if cve in cve_whitelist:
0202:bb.note("%s-%s has been whitelisted for %s" %
(product, pv, cve))
Exception: sqlite3.OperationalError: attempt to write a readonly database
So it seems your patch doesn't solve the issue
On 23.02.22 13:54, Ross Burton wrote:
All of the function in cve-check should open the database read-only, as
the only writer is the fetch task in cve-update-db. However,
get_cve_info() was failing to do this, which might be causing locking
issues with sqlite.
Signed-off-by: Ross Burton
---
meta/classes/cve-check.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 2d69aeba4b..d715fbf4d8 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -265,7 +265,8 @@ def get_cve_info(d, cves):
import sqlite3
cve_data = {}
-conn = sqlite3.connect(d.getVar("CVE_CHECK_DB_FILE"))
+db_file = d.expand("file:${CVE_CHECK_DB_FILE}?mode=ro")
+conn = sqlite3.connect(db_file, uri=True)
for cve in cves:
for row in conn.execute("SELECT * FROM NVD WHERE ID IS ?", (cve,)):
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162649):
https://lists.openembedded.org/g/openembedded-core/message/162649
Mute This Topic: https://lists.openembedded.org/mt/89339702/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] cve-check: get_cve_info should open the database read-only
What's the scenario where this is happening? Multiple build
directories using the same DL_DIR? Or was this a single build?
Ross
On Thu, 3 Mar 2022 at 08:10, Konrad Weihmann wrote:
>
> Sadly I encountered this here last night
>
> NOTE: recipe cve-update-db-native-1.0-r0: task do_cve_check: Started
> ERROR: cve-update-db-native-1.0-r0 do_cve_check: Error executing a
> python function in exec_func_python() autogenerated:
>
> The stack trace of python calls that resulted in this exception/failure was:
> File: 'exec_func_python() autogenerated', lineno: 2, function:
> 0001:
> *** 0002:do_cve_check(d)
> 0003:
> File: '/opt/build/sources/poky/meta/classes/cve-check.bbclass', lineno:
> 104, function: do_cve_check
> 0100:try:
> 0101:patched_cves = get_patched_cves(d)
> 0102:except FileNotFoundError:
> 0103:bb.fatal("Failure in searching patches")
> *** 0104:whitelisted, patched, unpatched = check_cves(d,
> patched_cves)
> 0105:if patched or unpatched:
> 0106:cve_data = get_cve_info(d, patched + unpatched)
> 0107:cve_write_data(d, patched, unpatched,
> whitelisted, cve_data)
> 0108:else:
> File: '/opt/build/sources/poky/meta/classes/cve-check.bbclass', lineno:
> 198, function: check_cves
> 0194:else:
> 0195:vendor = "%"
> 0196:
> 0197:# Find all relevant CVE IDs.
> *** 0198:for cverow in conn.execute("SELECT DISTINCT ID FROM
> PRODUCTS WHERE PRODUCT IS ? AND VENDOR LIKE ?", (product, vendor)):
> 0199:cve = cverow[0]
> 0200:
> 0201:if cve in cve_whitelist:
> 0202:bb.note("%s-%s has been whitelisted for %s" %
> (product, pv, cve))
> Exception: sqlite3.OperationalError: attempt to write a readonly database
>
> So it seems your patch doesn't solve the issue
>
>
>
> On 23.02.22 13:54, Ross Burton wrote:
> > All of the function in cve-check should open the database read-only, as
> > the only writer is the fetch task in cve-update-db. However,
> > get_cve_info() was failing to do this, which might be causing locking
> > issues with sqlite.
> >
> > Signed-off-by: Ross Burton
> > ---
> > meta/classes/cve-check.bbclass | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
> > index 2d69aeba4b..d715fbf4d8 100644
> > --- a/meta/classes/cve-check.bbclass
> > +++ b/meta/classes/cve-check.bbclass
> > @@ -265,7 +265,8 @@ def get_cve_info(d, cves):
> > import sqlite3
> >
> > cve_data = {}
> > -conn = sqlite3.connect(d.getVar("CVE_CHECK_DB_FILE"))
> > +db_file = d.expand("file:${CVE_CHECK_DB_FILE}?mode=ro")
> > +conn = sqlite3.connect(db_file, uri=True)
> >
> > for cve in cves:
> > for row in conn.execute("SELECT * FROM NVD WHERE ID IS ?",
> > (cve,)):
> >
> >
> >
> >
> >
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162648):
https://lists.openembedded.org/g/openembedded-core/message/162648
Mute This Topic: https://lists.openembedded.org/mt/89339702/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] [meta-oe][PATCH v2] libsndfile1: bump to version 1.0.31
On Thu, Mar 3, 2022 at 12:43 PM Richard Purdie wrote: > > On Tue, 2022-03-01 at 16:30 +0200, Alexandru Ardelean wrote: > > On Tue, Mar 1, 2022 at 4:23 PM Richard Purdie > > wrote: > > > > > > On Mon, 2022-02-28 at 12:32 +0200, Alexandru Ardelean wrote: > > > > On Thu, Feb 24, 2022 at 5:30 PM Alexandru Ardelean > > > > wrote: > > > > > > > > > > It seems that the homepage has moved (for a while now) from > > > > > http://www.mega-nerd.com/libsndfile/ > > > > > to > > > > > https://libsndfile.github.io/libsndfile/ > > > > > > > > > > On Github, the development group seems to include Erik de Castro Lopo > > > > > (the > > > > > original author of libsndfile1). > > > > > Link: https://github.com/orgs/libsndfile/people > > > > > > > > > > All backported CVE patches are in version 1.0.31 (I've checked). > > > > > > > > > > The supported format page [1], mentions that Ogg/Opus is supported > > > > > since > > > > > 1.0.29, however that isn't currently added in this patch. And it may > > > > > require libopus. > > > > > And mp3 is supported at around version 1.1.0, but that version is in > > > > > beta. > > > > > > > > > > This change focuses solely on updating to 1.0.31 and removing all > > > > > backported patches. > > > > > > > > > > [1] https://libsndfile.github.io/libsndfile/formats.html > > > > > > > > Bah... > > > > > > > > No luck with V2 either. > > > > This would require some patch to allow build without libopus support. > > > > Since there is no libopus available, it will not include support for > > > > libvorbis, libflac. > > > > i.e. libsndfile will build, but will say: > > > > > > > > configure: WARNING: *** One or more of the external libraries (ie > > > > libflac, libogg and > > > > configure: WARNING: *** libvorbis) is either missing (possibly only > > > > the development > > > > configure: WARNING: *** headers) or is of an unsupported version. > > > > configure: WARNING: *** > > > > configure: WARNING: *** Unfortunately, for ease of maintenance, the > > > > external libs > > > > configure: WARNING: *** are an all or nothing affair. > > > > > > > > > > > > Seems I forgot to check these extra configurations. > > > > > > > > Please disregard the V2 and apologies for the noise. > > > > > > > > I may try again with a V3, but let's see. > > > > > > > > > Unfortunately we merged this as it passed the automated testing and there > > > was no > > > other review feedback. > > > > Oh. > > Now I feel a bit worse. > > > > It is just the way things sometimes work out. I am pleased you spotted the > issue. > > > > https://git.yoctoproject.org/poky/commit/?id=fd2c86b06963345683ac5dc4f47f9da8e0c8c69d > > > > > > It does make me worry about tests here and means we'll have to find some > > > way to > > > fix this. > > > > The silent nature of this build issue, suggests a few things to move > > forward: > > > > 1. Propose a patch upstream to cause a build failure if this > > configuration isn't complete (i.e. all Xiph libs are enabled or not) > > It's their right to have this all Xiph libs or no Xiph libs support > > matrix. > > 2. For Yocto, we could add libopus, in the meantime OR > > Patch-out libopus in the build > > I had a look at patching out opus in the build and it didn't seem too > difficult, > the patch below seemed to work: > > Index: libsndfile-1.0.31/configure.ac > === > --- libsndfile-1.0.31.orig/configure.ac > +++ libsndfile-1.0.31/configure.ac > @@ -361,13 +361,13 @@ AS_IF([test -n "$PKG_CONFIG"], [ > enable_external_libs=yes > ]) > > - AS_IF([test > "x$ac_cv_flac$ac_cv_ogg$ac_cv_vorbis$ac_cv_vorbisenc$ac_cv_opus" = > "xyesyesyesyesyes"], [ > + AS_IF([test > "x$ac_cv_flac$ac_cv_ogg$ac_cv_vorbis$ac_cv_vorbisenc" = "xyesyesyesyes"], [ > HAVE_EXTERNAL_XIPH_LIBS=1 > enable_external_libs=yes > > - EXTERNAL_XIPH_CFLAGS="$FLAC_CFLAGS > $VORBIS_CFLAGS $VORBISENC_CFLAGS $SPEEX_CFLAGS $OPUS_CFLAGS $OGG_CFLAGS " > - EXTERNAL_XIPH_LIBS="$FLAC_LIBS > $VORBIS_LIBS $VORBISENC_LIBS $SPEEX_LIBS $OPUS_LIBS $OGG_LIBS " > - EXTERNAL_XIPH_REQUIRE="flac ogg > vorbis vorbisenc opus" > + EXTERNAL_XIPH_CFLAGS="$FLAC_CFLAGS > $VORBIS_CFLAGS $VORBISENC_CFLAGS $SPEEX_CFLAGS $OGG_CFLAGS " > + EXTERNAL_XIPH_LIBS="$FLAC_LIBS > $VORBIS_LIBS $VORBISENC_LIBS $SPEEX_LIBS $OGG_LIBS " > + EXTERNAL_XIPH_REQUIRE="flac ogg > vorbis vorbisenc" > > if test x$ac_cv_speex = "xyes" ; then > > EXTERNAL_XIPH_REQUIRE="$EXTERNAL_XIPH_REQUIRE speex" > @@ -716,7
Re: [OE-core] [meta-oe][PATCH v2] libsndfile1: bump to version 1.0.31
On Tue, 2022-03-01 at 16:30 +0200, Alexandru Ardelean wrote:
> On Tue, Mar 1, 2022 at 4:23 PM Richard Purdie
> wrote:
> >
> > On Mon, 2022-02-28 at 12:32 +0200, Alexandru Ardelean wrote:
> > > On Thu, Feb 24, 2022 at 5:30 PM Alexandru Ardelean
> > > wrote:
> > > >
> > > > It seems that the homepage has moved (for a while now) from
> > > > http://www.mega-nerd.com/libsndfile/
> > > > to
> > > > https://libsndfile.github.io/libsndfile/
> > > >
> > > > On Github, the development group seems to include Erik de Castro Lopo
> > > > (the
> > > > original author of libsndfile1).
> > > > Link: https://github.com/orgs/libsndfile/people
> > > >
> > > > All backported CVE patches are in version 1.0.31 (I've checked).
> > > >
> > > > The supported format page [1], mentions that Ogg/Opus is supported since
> > > > 1.0.29, however that isn't currently added in this patch. And it may
> > > > require libopus.
> > > > And mp3 is supported at around version 1.1.0, but that version is in
> > > > beta.
> > > >
> > > > This change focuses solely on updating to 1.0.31 and removing all
> > > > backported patches.
> > > >
> > > > [1] https://libsndfile.github.io/libsndfile/formats.html
> > >
> > > Bah...
> > >
> > > No luck with V2 either.
> > > This would require some patch to allow build without libopus support.
> > > Since there is no libopus available, it will not include support for
> > > libvorbis, libflac.
> > > i.e. libsndfile will build, but will say:
> > >
> > > configure: WARNING: *** One or more of the external libraries (ie
> > > libflac, libogg and
> > > configure: WARNING: *** libvorbis) is either missing (possibly only
> > > the development
> > > configure: WARNING: *** headers) or is of an unsupported version.
> > > configure: WARNING: ***
> > > configure: WARNING: *** Unfortunately, for ease of maintenance, the
> > > external libs
> > > configure: WARNING: *** are an all or nothing affair.
> > >
> > >
> > > Seems I forgot to check these extra configurations.
> > >
> > > Please disregard the V2 and apologies for the noise.
> > >
> > > I may try again with a V3, but let's see.
> >
> >
> > Unfortunately we merged this as it passed the automated testing and there
> > was no
> > other review feedback.
>
> Oh.
> Now I feel a bit worse.
>
It is just the way things sometimes work out. I am pleased you spotted the
issue.
> > https://git.yoctoproject.org/poky/commit/?id=fd2c86b06963345683ac5dc4f47f9da8e0c8c69d
> >
> > It does make me worry about tests here and means we'll have to find some
> > way to
> > fix this.
>
> The silent nature of this build issue, suggests a few things to move forward:
>
> 1. Propose a patch upstream to cause a build failure if this
> configuration isn't complete (i.e. all Xiph libs are enabled or not)
> It's their right to have this all Xiph libs or no Xiph libs support
> matrix.
> 2. For Yocto, we could add libopus, in the meantime OR
> Patch-out libopus in the build
I had a look at patching out opus in the build and it didn't seem too difficult,
the patch below seemed to work:
Index: libsndfile-1.0.31/configure.ac
===
--- libsndfile-1.0.31.orig/configure.ac
+++ libsndfile-1.0.31/configure.ac
@@ -361,13 +361,13 @@ AS_IF([test -n "$PKG_CONFIG"], [
enable_external_libs=yes
])
- AS_IF([test
"x$ac_cv_flac$ac_cv_ogg$ac_cv_vorbis$ac_cv_vorbisenc$ac_cv_opus" =
"xyesyesyesyesyes"], [
+ AS_IF([test
"x$ac_cv_flac$ac_cv_ogg$ac_cv_vorbis$ac_cv_vorbisenc" = "xyesyesyesyes"], [
HAVE_EXTERNAL_XIPH_LIBS=1
enable_external_libs=yes
- EXTERNAL_XIPH_CFLAGS="$FLAC_CFLAGS
$VORBIS_CFLAGS $VORBISENC_CFLAGS $SPEEX_CFLAGS $OPUS_CFLAGS $OGG_CFLAGS "
- EXTERNAL_XIPH_LIBS="$FLAC_LIBS
$VORBIS_LIBS $VORBISENC_LIBS $SPEEX_LIBS $OPUS_LIBS $OGG_LIBS "
- EXTERNAL_XIPH_REQUIRE="flac ogg vorbis
vorbisenc opus"
+ EXTERNAL_XIPH_CFLAGS="$FLAC_CFLAGS
$VORBIS_CFLAGS $VORBISENC_CFLAGS $SPEEX_CFLAGS $OGG_CFLAGS "
+ EXTERNAL_XIPH_LIBS="$FLAC_LIBS
$VORBIS_LIBS $VORBISENC_LIBS $SPEEX_LIBS $OGG_LIBS "
+ EXTERNAL_XIPH_REQUIRE="flac ogg vorbis
vorbisenc"
if test x$ac_cv_speex = "xyes" ; then
EXTERNAL_XIPH_REQUIRE="$EXTERNAL_XIPH_REQUIRE speex"
@@ -716,7 +716,7 @@ AC_MSG_RESULT([
Experimental code : ... ${enable_experimental:-no}
Using ALSA in example programs : .. ${enable_alsa:-no}
-External FLAC/Ogg/Vorbis/Opus : ... ${enable_external_libs:-no}
+External FLAC/Ogg/Vorbis : ...
[OE-core] [PATCH] glslang/spirv: synchronize with the rest of vulkan items
These components are now versioned in sync with vulkan releases:
https://github.com/KhronosGroup/SPIRV-Headers/issues/252
https://github.com/KhronosGroup/SPIRV-Headers/issues/266
"We'll continue tagging the repos contributing with SDK releases, as
that is when all the testing of the various projects is performed
together."
Signed-off-by: Alexander Kanavin
---
.../glslang/{glslang_11.8.0.bb => glslang_1.3.204.0.bb}| 5 +++--
.../{spirv-headers_1.5.4.bb => spirv-headers_1.3.204.0.bb} | 4 ++--
.../{spirv-tools_2022.1.bb => spirv-tools_1.3.204.0.bb}| 7 ---
3 files changed, 9 insertions(+), 7 deletions(-)
rename meta/recipes-graphics/glslang/{glslang_11.8.0.bb =>
glslang_1.3.204.0.bb} (90%)
rename meta/recipes-graphics/spir/{spirv-headers_1.5.4.bb =>
spirv-headers_1.3.204.0.bb} (88%)
rename meta/recipes-graphics/spir/{spirv-tools_2022.1.bb =>
spirv-tools_1.3.204.0.bb} (89%)
diff --git a/meta/recipes-graphics/glslang/glslang_11.8.0.bb
b/meta/recipes-graphics/glslang/glslang_1.3.204.0.bb
similarity index 90%
rename from meta/recipes-graphics/glslang/glslang_11.8.0.bb
rename to meta/recipes-graphics/glslang/glslang_1.3.204.0.bb
index a77d8bdf88..2af406212f 100644
--- a/meta/recipes-graphics/glslang/glslang_11.8.0.bb
+++ b/meta/recipes-graphics/glslang/glslang_1.3.204.0.bb
@@ -8,10 +8,11 @@ HOMEPAGE =
"https://www.khronos.org/opengles/sdk/tools/Reference-Compiler;
LICENSE = "BSD-3-Clause & BSD-2-Clause & MIT & Apache-2.0 &
GPL-3-with-bison-exception"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=2a2b5acd7bc4844964cfda45fe807dc3"
-SRCREV = "c34bb3b6c55f6ab084124ad964be95a699700d34"
+SRCREV = "2742e959347ae2fac58acd0d022c92a0ff1f24bf"
SRC_URI =
"git://github.com/KhronosGroup/glslang.git;protocol=https;branch=master \
file://0001-generate-glslang-pkg-config.patch"
-UPSTREAM_CHECK_GITTAGREGEX = "^(?P\d+(\.\d+)+)$"
+PE = "1"
+UPSTREAM_CHECK_GITTAGREGEX = "sdk-(?P\d+(\.\d+)+)"
S = "${WORKDIR}/git"
inherit cmake python3native
diff --git a/meta/recipes-graphics/spir/spirv-headers_1.5.4.bb
b/meta/recipes-graphics/spir/spirv-headers_1.3.204.0.bb
similarity index 88%
rename from meta/recipes-graphics/spir/spirv-headers_1.5.4.bb
rename to meta/recipes-graphics/spir/spirv-headers_1.3.204.0.bb
index 3144b1eb42..72416b441f 100644
--- a/meta/recipes-graphics/spir/spirv-headers_1.5.4.bb
+++ b/meta/recipes-graphics/spir/spirv-headers_1.3.204.0.bb
@@ -9,9 +9,9 @@ LIC_FILES_CHKSUM =
"file://LICENSE;md5=c938b85bceb8fb26c1a807f28a52ae2d"
SRCREV = "b42ba6d92faf6b4938e6f22ddd186dbdacc98d78"
SRC_URI =
"git://github.com/KhronosGroup/SPIRV-Headers;protocol=https;branch=master"
-UPSTREAM_CHECK_GITTAGREGEX = "^(?P\d+(\.\d+)+)$"
+PE = "1"
+UPSTREAM_CHECK_GITTAGREGEX = "sdk-(?P\d+(\.\d+)+)"
S = "${WORKDIR}/git"
-PV .= "+git${SRCPV}"
inherit cmake
diff --git a/meta/recipes-graphics/spir/spirv-tools_2022.1.bb
b/meta/recipes-graphics/spir/spirv-tools_1.3.204.0.bb
similarity index 89%
rename from meta/recipes-graphics/spir/spirv-tools_2022.1.bb
rename to meta/recipes-graphics/spir/spirv-tools_1.3.204.0.bb
index 24142a4fe0..dc78073717 100644
--- a/meta/recipes-graphics/spir/spirv-tools_2022.1.bb
+++ b/meta/recipes-graphics/spir/spirv-tools_1.3.204.0.bb
@@ -7,9 +7,10 @@ SECTION = "graphics"
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
-SRCREV = "b1877de5cd776117050bd42f08d04b52bce16099"
-SRC_URI =
"git://github.com/KhronosGroup/SPIRV-Tools.git;branch=master;protocol=https"
-UPSTREAM_CHECK_GITTAGREGEX = "^v(?P\d+(\.\d+)+)$"
+SRCREV = "45dd184c790d6bfc78a5a74a10c37e888b1823fa"
+SRC_URI =
"git://github.com/KhronosGroup/SPIRV-Tools.git;branch=stable;protocol=https"
+PE = "1"
+UPSTREAM_CHECK_GITTAGREGEX = "sdk-(?P\d+(\.\d+)+)"
S = "${WORKDIR}/git"
inherit cmake python3native
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162645):
https://lists.openembedded.org/g/openembedded-core/message/162645
Mute This Topic: https://lists.openembedded.org/mt/89522413/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 3/3] glslang/spirv: synchronize with the rest of vulkan items
On Thu, 3 Mar 2022 at 10:58, Jose Quaresma wrote: >> What kind of reference, like a link to some kind of upstream statement? > > > Yes, I think a link is useful. > I only found these issues but nothing official in release notes or somewhere > else. > https://github.com/KhronosGroup/SPIRV-Headers/issues/252 > https://github.com/KhronosGroup/SPIRV-Headers/issues/266 "We'll continue tagging the repos contributing with SDK releases, as that is when all the testing of the various projects is performed together." is the critical bit in there, so I'll just add these and resend. Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162644): https://lists.openembedded.org/g/openembedded-core/message/162644 Mute This Topic: https://lists.openembedded.org/mt/89522063/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 3/3] glslang/spirv: synchronize with the rest of vulkan items
Alexander Kanavin escreveu no dia quinta, 3/03/2022 à(s) 09:53: > On Thu, 3 Mar 2022 at 10:45, Jose Quaresma > wrote: > > > Is it possible to add a reference on the commit message for this change? > > What kind of reference, like a link to some kind of upstream statement? > Yes, I think a link is useful. I only found these issues but nothing official in release notes or somewhere else. https://github.com/KhronosGroup/SPIRV-Headers/issues/252 https://github.com/KhronosGroup/SPIRV-Headers/issues/266 Jose > Alex > -- Best regards, José Quaresma -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162643): https://lists.openembedded.org/g/openembedded-core/message/162643 Mute This Topic: https://lists.openembedded.org/mt/89522063/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 3/3] glslang/spirv: synchronize with the rest of vulkan items
On Thu, 3 Mar 2022 at 10:45, Jose Quaresma wrote: > Is it possible to add a reference on the commit message for this change? What kind of reference, like a link to some kind of upstream statement? Alex -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#162642): https://lists.openembedded.org/g/openembedded-core/message/162642 Mute This Topic: https://lists.openembedded.org/mt/89522063/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 3/3] glslang/spirv: synchronize with the rest of vulkan items
Hi Alexander,
Is it possible to add a reference on the commit message for this change?
Jose
Alexander Kanavin escreveu no dia quinta,
3/03/2022 à(s) 09:33:
> These components are now versioned in sync with vulkan releases.
>
> Signed-off-by: Alexander Kanavin
> ---
> .../glslang/{glslang_11.8.0.bb => glslang_1.3.204.0.bb}| 5 +++--
> .../{spirv-headers_1.5.4.bb => spirv-headers_1.3.204.0.bb} | 4 ++--
> .../{spirv-tools_2022.1.bb => spirv-tools_1.3.204.0.bb}| 7 ---
> 3 files changed, 9 insertions(+), 7 deletions(-)
> rename meta/recipes-graphics/glslang/{glslang_11.8.0.bb =>
> glslang_1.3.204.0.bb} (90%)
> rename meta/recipes-graphics/spir/{spirv-headers_1.5.4.bb =>
> spirv-headers_1.3.204.0.bb} (88%)
> rename meta/recipes-graphics/spir/{spirv-tools_2022.1.bb =>
> spirv-tools_1.3.204.0.bb} (89%)
>
> diff --git a/meta/recipes-graphics/glslang/glslang_11.8.0.bb
> b/meta/recipes-graphics/glslang/glslang_1.3.204.0.bb
> similarity index 90%
> rename from meta/recipes-graphics/glslang/glslang_11.8.0.bb
> rename to meta/recipes-graphics/glslang/glslang_1.3.204.0.bb
> index a77d8bdf88..2af406212f 100644
> --- a/meta/recipes-graphics/glslang/glslang_11.8.0.bb
> +++ b/meta/recipes-graphics/glslang/glslang_1.3.204.0.bb
> @@ -8,10 +8,11 @@ HOMEPAGE = "
> https://www.khronos.org/opengles/sdk/tools/Reference-Compiler;
> LICENSE = "BSD-3-Clause & BSD-2-Clause & MIT & Apache-2.0 &
> GPL-3-with-bison-exception"
> LIC_FILES_CHKSUM =
> "file://LICENSE.txt;md5=2a2b5acd7bc4844964cfda45fe807dc3"
>
> -SRCREV = "c34bb3b6c55f6ab084124ad964be95a699700d34"
> +SRCREV = "2742e959347ae2fac58acd0d022c92a0ff1f24bf"
> SRC_URI = "git://
> github.com/KhronosGroup/glslang.git;protocol=https;branch=master \
> file://0001-generate-glslang-pkg-config.patch"
> -UPSTREAM_CHECK_GITTAGREGEX = "^(?P\d+(\.\d+)+)$"
> +PE = "1"
> +UPSTREAM_CHECK_GITTAGREGEX = "sdk-(?P\d+(\.\d+)+)"
> S = "${WORKDIR}/git"
>
> inherit cmake python3native
> diff --git a/meta/recipes-graphics/spir/spirv-headers_1.5.4.bb
> b/meta/recipes-graphics/spir/spirv-headers_1.3.204.0.bb
> similarity index 88%
> rename from meta/recipes-graphics/spir/spirv-headers_1.5.4.bb
> rename to meta/recipes-graphics/spir/spirv-headers_1.3.204.0.bb
> index 3144b1eb42..72416b441f 100644
> --- a/meta/recipes-graphics/spir/spirv-headers_1.5.4.bb
> +++ b/meta/recipes-graphics/spir/spirv-headers_1.3.204.0.bb
> @@ -9,9 +9,9 @@ LIC_FILES_CHKSUM =
> "file://LICENSE;md5=c938b85bceb8fb26c1a807f28a52ae2d"
>
> SRCREV = "b42ba6d92faf6b4938e6f22ddd186dbdacc98d78"
> SRC_URI = "git://
> github.com/KhronosGroup/SPIRV-Headers;protocol=https;branch=master"
> -UPSTREAM_CHECK_GITTAGREGEX = "^(?P\d+(\.\d+)+)$"
> +PE = "1"
> +UPSTREAM_CHECK_GITTAGREGEX = "sdk-(?P\d+(\.\d+)+)"
> S = "${WORKDIR}/git"
> -PV .= "+git${SRCPV}"
>
> inherit cmake
>
> diff --git a/meta/recipes-graphics/spir/spirv-tools_2022.1.bb
> b/meta/recipes-graphics/spir/spirv-tools_1.3.204.0.bb
> similarity index 89%
> rename from meta/recipes-graphics/spir/spirv-tools_2022.1.bb
> rename to meta/recipes-graphics/spir/spirv-tools_1.3.204.0.bb
> index 24142a4fe0..dc78073717 100644
> --- a/meta/recipes-graphics/spir/spirv-tools_2022.1.bb
> +++ b/meta/recipes-graphics/spir/spirv-tools_1.3.204.0.bb
> @@ -7,9 +7,10 @@ SECTION = "graphics"
> LICENSE = "Apache-2.0"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
>
> -SRCREV = "b1877de5cd776117050bd42f08d04b52bce16099"
> -SRC_URI = "git://
> github.com/KhronosGroup/SPIRV-Tools.git;branch=master;protocol=https"
> -UPSTREAM_CHECK_GITTAGREGEX = "^v(?P\d+(\.\d+)+)$"
> +SRCREV = "45dd184c790d6bfc78a5a74a10c37e888b1823fa"
> +SRC_URI = "git://
> github.com/KhronosGroup/SPIRV-Tools.git;branch=stable;protocol=https"
> +PE = "1"
> +UPSTREAM_CHECK_GITTAGREGEX = "sdk-(?P\d+(\.\d+)+)"
> S = "${WORKDIR}/git"
>
> inherit cmake python3native
> --
> 2.30.2
>
>
>
>
>
--
Best regards,
José Quaresma
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162641):
https://lists.openembedded.org/g/openembedded-core/message/162641
Mute This Topic: https://lists.openembedded.org/mt/89522063/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/3] libsndfile1: correct upstream version check
Signed-off-by: Alexander Kanavin
---
meta/recipes-multimedia/libsndfile/libsndfile1_1.0.31.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.31.bb
b/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.31.bb
index 8430dee103..9f1a106600 100644
--- a/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.31.bb
+++ b/meta/recipes-multimedia/libsndfile/libsndfile1_1.0.31.bb
@@ -10,6 +10,7 @@ LICENSE = "LGPL-2.1-only"
SRC_URI =
"https://github.com/libsndfile/libsndfile/releases/download/${PV}/libsndfile-${PV}.tar.bz2
\
"
+UPSTREAM_CHECK_URI = "https://github.com/libsndfile/libsndfile/releases/;
SRC_URI[md5sum] = "3f3b2a86a032f064ef922a2c8c191f7b"
SRC_URI[sha256sum] =
"a8cfb1c09ea6e90eff4ca87322d4168cdbe5035cb48717b40bf77e751cc02163"
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162638):
https://lists.openembedded.org/g/openembedded-core/message/162638
Mute This Topic: https://lists.openembedded.org/mt/89522061/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 3/3] glslang/spirv: synchronize with the rest of vulkan items
These components are now versioned in sync with vulkan releases.
Signed-off-by: Alexander Kanavin
---
.../glslang/{glslang_11.8.0.bb => glslang_1.3.204.0.bb}| 5 +++--
.../{spirv-headers_1.5.4.bb => spirv-headers_1.3.204.0.bb} | 4 ++--
.../{spirv-tools_2022.1.bb => spirv-tools_1.3.204.0.bb}| 7 ---
3 files changed, 9 insertions(+), 7 deletions(-)
rename meta/recipes-graphics/glslang/{glslang_11.8.0.bb =>
glslang_1.3.204.0.bb} (90%)
rename meta/recipes-graphics/spir/{spirv-headers_1.5.4.bb =>
spirv-headers_1.3.204.0.bb} (88%)
rename meta/recipes-graphics/spir/{spirv-tools_2022.1.bb =>
spirv-tools_1.3.204.0.bb} (89%)
diff --git a/meta/recipes-graphics/glslang/glslang_11.8.0.bb
b/meta/recipes-graphics/glslang/glslang_1.3.204.0.bb
similarity index 90%
rename from meta/recipes-graphics/glslang/glslang_11.8.0.bb
rename to meta/recipes-graphics/glslang/glslang_1.3.204.0.bb
index a77d8bdf88..2af406212f 100644
--- a/meta/recipes-graphics/glslang/glslang_11.8.0.bb
+++ b/meta/recipes-graphics/glslang/glslang_1.3.204.0.bb
@@ -8,10 +8,11 @@ HOMEPAGE =
"https://www.khronos.org/opengles/sdk/tools/Reference-Compiler;
LICENSE = "BSD-3-Clause & BSD-2-Clause & MIT & Apache-2.0 &
GPL-3-with-bison-exception"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=2a2b5acd7bc4844964cfda45fe807dc3"
-SRCREV = "c34bb3b6c55f6ab084124ad964be95a699700d34"
+SRCREV = "2742e959347ae2fac58acd0d022c92a0ff1f24bf"
SRC_URI =
"git://github.com/KhronosGroup/glslang.git;protocol=https;branch=master \
file://0001-generate-glslang-pkg-config.patch"
-UPSTREAM_CHECK_GITTAGREGEX = "^(?P\d+(\.\d+)+)$"
+PE = "1"
+UPSTREAM_CHECK_GITTAGREGEX = "sdk-(?P\d+(\.\d+)+)"
S = "${WORKDIR}/git"
inherit cmake python3native
diff --git a/meta/recipes-graphics/spir/spirv-headers_1.5.4.bb
b/meta/recipes-graphics/spir/spirv-headers_1.3.204.0.bb
similarity index 88%
rename from meta/recipes-graphics/spir/spirv-headers_1.5.4.bb
rename to meta/recipes-graphics/spir/spirv-headers_1.3.204.0.bb
index 3144b1eb42..72416b441f 100644
--- a/meta/recipes-graphics/spir/spirv-headers_1.5.4.bb
+++ b/meta/recipes-graphics/spir/spirv-headers_1.3.204.0.bb
@@ -9,9 +9,9 @@ LIC_FILES_CHKSUM =
"file://LICENSE;md5=c938b85bceb8fb26c1a807f28a52ae2d"
SRCREV = "b42ba6d92faf6b4938e6f22ddd186dbdacc98d78"
SRC_URI =
"git://github.com/KhronosGroup/SPIRV-Headers;protocol=https;branch=master"
-UPSTREAM_CHECK_GITTAGREGEX = "^(?P\d+(\.\d+)+)$"
+PE = "1"
+UPSTREAM_CHECK_GITTAGREGEX = "sdk-(?P\d+(\.\d+)+)"
S = "${WORKDIR}/git"
-PV .= "+git${SRCPV}"
inherit cmake
diff --git a/meta/recipes-graphics/spir/spirv-tools_2022.1.bb
b/meta/recipes-graphics/spir/spirv-tools_1.3.204.0.bb
similarity index 89%
rename from meta/recipes-graphics/spir/spirv-tools_2022.1.bb
rename to meta/recipes-graphics/spir/spirv-tools_1.3.204.0.bb
index 24142a4fe0..dc78073717 100644
--- a/meta/recipes-graphics/spir/spirv-tools_2022.1.bb
+++ b/meta/recipes-graphics/spir/spirv-tools_1.3.204.0.bb
@@ -7,9 +7,10 @@ SECTION = "graphics"
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=3b83ef96387f14655fc854ddc3c6bd57"
-SRCREV = "b1877de5cd776117050bd42f08d04b52bce16099"
-SRC_URI =
"git://github.com/KhronosGroup/SPIRV-Tools.git;branch=master;protocol=https"
-UPSTREAM_CHECK_GITTAGREGEX = "^v(?P\d+(\.\d+)+)$"
+SRCREV = "45dd184c790d6bfc78a5a74a10c37e888b1823fa"
+SRC_URI =
"git://github.com/KhronosGroup/SPIRV-Tools.git;branch=stable;protocol=https"
+PE = "1"
+UPSTREAM_CHECK_GITTAGREGEX = "sdk-(?P\d+(\.\d+)+)"
S = "${WORKDIR}/git"
inherit cmake python3native
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162640):
https://lists.openembedded.org/g/openembedded-core/message/162640
Mute This Topic: https://lists.openembedded.org/mt/89522063/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 2/3] libarchive: correct upstream version check
Signed-off-by: Alexander Kanavin
---
meta/recipes-extended/libarchive/libarchive_3.6.0.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-extended/libarchive/libarchive_3.6.0.bb
b/meta/recipes-extended/libarchive/libarchive_3.6.0.bb
index 31bc82515a..f078c8ad03 100644
--- a/meta/recipes-extended/libarchive/libarchive_3.6.0.bb
+++ b/meta/recipes-extended/libarchive/libarchive_3.6.0.bb
@@ -33,6 +33,7 @@ PACKAGECONFIG[zstd] = "--with-zstd,--without-zstd,zstd,"
EXTRA_OECONF += "--enable-largefile"
SRC_URI = "http://libarchive.org/downloads/libarchive-${PV}.tar.gz;
+UPSTREAM_CHECK_URI = "http://libarchive.org/;
SRC_URI[sha256sum] =
"a36613695ffa2905fdedc997b6df04a3006ccfd71d747a339b78aa8412c3d852"
--
2.30.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162639):
https://lists.openembedded.org/g/openembedded-core/message/162639
Mute This Topic: https://lists.openembedded.org/mt/89522062/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] cve-check: get_cve_info should open the database read-only
Sadly I encountered this here last night
NOTE: recipe cve-update-db-native-1.0-r0: task do_cve_check: Started
ERROR: cve-update-db-native-1.0-r0 do_cve_check: Error executing a
python function in exec_func_python() autogenerated:
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_func_python() autogenerated', lineno: 2, function:
0001:
*** 0002:do_cve_check(d)
0003:
File: '/opt/build/sources/poky/meta/classes/cve-check.bbclass', lineno:
104, function: do_cve_check
0100:try:
0101:patched_cves = get_patched_cves(d)
0102:except FileNotFoundError:
0103:bb.fatal("Failure in searching patches")
*** 0104:whitelisted, patched, unpatched = check_cves(d,
patched_cves)
0105:if patched or unpatched:
0106:cve_data = get_cve_info(d, patched + unpatched)
0107:cve_write_data(d, patched, unpatched,
whitelisted, cve_data)
0108:else:
File: '/opt/build/sources/poky/meta/classes/cve-check.bbclass', lineno:
198, function: check_cves
0194:else:
0195:vendor = "%"
0196:
0197:# Find all relevant CVE IDs.
*** 0198:for cverow in conn.execute("SELECT DISTINCT ID FROM
PRODUCTS WHERE PRODUCT IS ? AND VENDOR LIKE ?", (product, vendor)):
0199:cve = cverow[0]
0200:
0201:if cve in cve_whitelist:
0202:bb.note("%s-%s has been whitelisted for %s" %
(product, pv, cve))
Exception: sqlite3.OperationalError: attempt to write a readonly database
So it seems your patch doesn't solve the issue
On 23.02.22 13:54, Ross Burton wrote:
All of the function in cve-check should open the database read-only, as
the only writer is the fetch task in cve-update-db. However,
get_cve_info() was failing to do this, which might be causing locking
issues with sqlite.
Signed-off-by: Ross Burton
---
meta/classes/cve-check.bbclass | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/meta/classes/cve-check.bbclass b/meta/classes/cve-check.bbclass
index 2d69aeba4b..d715fbf4d8 100644
--- a/meta/classes/cve-check.bbclass
+++ b/meta/classes/cve-check.bbclass
@@ -265,7 +265,8 @@ def get_cve_info(d, cves):
import sqlite3
cve_data = {}
-conn = sqlite3.connect(d.getVar("CVE_CHECK_DB_FILE"))
+db_file = d.expand("file:${CVE_CHECK_DB_FILE}?mode=ro")
+conn = sqlite3.connect(db_file, uri=True)
for cve in cves:
for row in conn.execute("SELECT * FROM NVD WHERE ID IS ?", (cve,)):
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#162637):
https://lists.openembedded.org/g/openembedded-core/message/162637
Mute This Topic: https://lists.openembedded.org/mt/89339702/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] Binutils: Avoid Race condition in as.info
On Wed, 2022-03-02 at 21:57 -0800, Pgowda wrote:
> The race condition in binutils/gas folder was introduced with the
> following patch. The patch avoids recursive make into the doc folder.
> It would speed up the build process slightly. However, the as.info
> is installed twice which resulted in the race condition sometimes.
> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=bde299e063de090bf36c1fe51874d1e9f4d94c3c
>
> On debugging the code, it was found that the issue was related to
> install-data-local. On further analysis, there is already a patch in
> binutils that removes install-data-local.
> On applying the patch as.info is installed once as expected and there’s
> no possibility of any race condition.
> https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=9a84a44d5df4618dd616137fa755bd71b7eacc5f
>
> Upstream-Status: Backport
> [https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=9a84a44d5df4618dd616137fa755bd71b7eacc5f]
>
> [YOCTO #14725]
>
> Signed-off-by: pgowda
> ---
> .../binutils/binutils-2.38.inc| 1 +
> .../0013-Avoid-as-info-race-condition.patch | 75 +++
> 2 files changed, 76 insertions(+)
> create mode 100644
> meta/recipes-devtools/binutils/binutils/0013-Avoid-as-info-race-condition.patch
Thanks for tracking that down, it will be good to fix this one as we've seen it
fail a few times. Note that the Upstream-Status in the patch below was
incorrect, it needed to be Backport like it is above.
I've fixed it in the patch I've queued for testing so no need to resend.
Cheers,
Richard
>
> diff --git a/meta/recipes-devtools/binutils/binutils-2.38.inc
> b/meta/recipes-devtools/binutils/binutils-2.38.inc
> index 6d4415048a..4ce74f94bf 100644
> --- a/meta/recipes-devtools/binutils/binutils-2.38.inc
> +++ b/meta/recipes-devtools/binutils/binutils-2.38.inc
> @@ -31,5 +31,6 @@ SRC_URI = "\
> file://0010-Fix-rpath-in-libtool-when-sysroot-is-enabled.patch \
> file://0011-sync-with-OE-libtool-changes.patch \
> file://0012-Check-for-clang-before-checking-gcc-version.patch \
> + file://0013-Avoid-as-info-race-condition.patch \
> "
> S = "${WORKDIR}/git"
> diff --git
> a/meta/recipes-devtools/binutils/binutils/0013-Avoid-as-info-race-condition.patch
>
> b/meta/recipes-devtools/binutils/binutils/0013-Avoid-as-info-race-condition.patch
> new file mode 100644
> index 00..8edc12d5a9
> --- /dev/null
> +++
> b/meta/recipes-devtools/binutils/binutils/0013-Avoid-as-info-race-condition.patch
> @@ -0,0 +1,75 @@
> +From 9a84a44d5df4618dd616137fa755bd71b7eacc5f Mon Sep 17 00:00:00 2001
> +From: Mike Frysinger
> +Date: Sun, 23 Jan 2022 12:44:24 -0500
> +Subject: [PATCH] gas: drop old cygnus install hack
> +
> +This was needed when gas was using the automake cygnus option, but
> +this was removed years ago by Simon in d0ac1c44885daf68f631befa37e
> +("Bump to autoconf 2.69 and automake 1.15.1"). So delete it here.
> +The info pages are already & still installed by default w/out it.
> +
> +Upstream-Status: Pending
> +
> +Signed-off-by: Khem Raj
> +---
> + gas/Makefile.in | 14 +-
> + gas/doc/local.mk | 4
> + 2 files changed, 5 insertions(+), 13 deletions(-)
> +
> +diff --git a/gas/Makefile.in b/gas/Makefile.in
> +index 8f0a56fd8d6..67dac53f68c 100644
> +--- a/gas/Makefile.in
> b/gas/Makefile.in
> +@@ -1854,7 +1854,7 @@ info: info-recursive
> +
> + info-am: $(INFO_DEPS) info-local
> +
> +-install-data-am: install-data-local install-info-am install-man
> ++install-data-am: install-info-am install-man
> +
> + install-dvi: install-dvi-recursive
> +
> +@@ -2008,10 +2008,10 @@ uninstall-man: uninstall-man1
> + distclean-DEJAGNU distclean-compile distclean-generic \
> + distclean-hdr distclean-libtool distclean-tags dvi dvi-am html \
> + html-am html-local info info-am info-local install install-am \
> +-install-data install-data-am install-data-local install-dvi \
> +-install-dvi-am install-exec install-exec-am install-exec-local \
> +-install-html install-html-am install-info install-info-am \
> +-install-man install-man1 install-pdf install-pdf-am install-ps \
> ++install-data install-data-am install-dvi install-dvi-am \
> ++install-exec install-exec-am install-exec-local install-html \
> ++install-html-am install-info install-info-am install-man \
> ++install-man1 install-pdf install-pdf-am install-ps \
> + install-ps-am install-strip installcheck installcheck-am \
> + installdirs installdirs-am maintainer-clean \
> + maintainer-clean-aminfo maintainer-clean-generic mostlyclean \
> +@@ -2211,10 +2211,6 @@ doc/asconfig.texi: doc/$(CONFIG).texi
> doc/$(am__dirstamp)
> + $(AM_V_GEN)cp $(srcdir)/doc/$(CONFIG).texi doc/asconfig.texi
> + $(AM_V_at)chmod u+w doc/asconfig.texi
> +
> +-# We want install to imply install-info as per GNU standards, despite the
> +-# cygnus option.
> +-install-data-local: install-info
> +-
> + #
