|
[PATCH v3] boost: revert 1.72.0 regression
Andrew Geissler
https://www.boost.org/users/history/version_1_72_0.html documents a
"Known Issue" and has a revert patch for an issue that causes code to fail to compile that includes the coroutine function. Without this patch, code which includes the asymmetric_coroutine.hpp will fail to compile. Signed-off-by: Andrew Geissler <geissonator@...> v2: added Signed-off-by to patch added Upstream-Status tag v3: moved Upstream-status tag to the patch file --- meta/recipes-support/boost/boost_1.72.0.bb | 1 + ...001-revert-cease-dependence-on-range.patch | 53 +++++++++++++++++++ 2 files changed, 54 insertions(+) create mode 100644 meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch diff --git a/meta/recipes-support/boost/boost_1.72.0.bb b/meta/recipes-support/boost/boost_1.72.0.bb index 5e9e0d87d7..0b7badbc76 100644 --- a/meta/recipes-support/boost/boost_1.72.0.bb +++ b/meta/recipes-support/boost/boost_1.72.0.bb @@ -7,4 +7,5 @@ SRC_URI += "file://arm-intrinsics.patch \ file://0001-Apply-boost-1.62.0-no-forced-flags.patch.patch \ file://0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch \ file://0001-dont-setup-compiler-flags-m32-m64.patch \ + file://0001-revert-cease-dependence-on-range.patch \ " diff --git a/meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch b/meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch new file mode 100644 index 0000000000..d6d09a23a5 --- /dev/null +++ b/meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch @@ -0,0 +1,53 @@ +From 436e1dbe6fcd31523d261d18ad011392f1d6fbbc Mon Sep 17 00:00:00 2001 +From: Oliver Kowalke <oliver.kowalke@...> +Date: Sun, 1 Dec 2019 20:40:28 +0100 +Subject: [PATCH] Revert "Cease dependence on Range" + +This reverts commit 0c556bb59241e682bbcd3f572815149c5a9b17db. + +see #44 (One test fails to compile after boostorg/coroutine submodule updated) + +Upstream-Status: Backport [https://github.com/boostorg/coroutine/commit/9c73b2f7c1759a9508ba8780b38dc15f07f1a447] + +Signed-off-by: Andrew Geissler <geissonator@...> +--- + boost/coroutine/asymmetric_coroutine.hpp | 12 +++--------- + 1 file changed, 3 insertions(+), 9 deletions(-) + +diff --git a/boost/coroutine/asymmetric_coroutine.hpp b/boost/coroutine/asymmetric_coroutine.hpp +index ea96981..640896f 100644 +--- a/boost/coroutine/asymmetric_coroutine.hpp ++++ b/boost/coroutine/asymmetric_coroutine.hpp +@@ -14,6 +14,7 @@ + #include <boost/assert.hpp> + #include <boost/config.hpp> + #include <boost/move/move.hpp> ++#include <boost/range.hpp> + #include <boost/throw_exception.hpp> + #include <boost/utility/explicit_operator_bool.hpp> + +@@ -2354,19 +2355,12 @@ end( push_coroutine< R > & c) + + } + +-// forward declaration of Boost.Range traits to break dependency on it +-template<typename C, typename Enabler> +-struct range_mutable_iterator; +- +-template<typename C, typename Enabler> +-struct range_const_iterator; +- + template< typename Arg > +-struct range_mutable_iterator< coroutines::push_coroutine< Arg >, void > ++struct range_mutable_iterator< coroutines::push_coroutine< Arg > > + { typedef typename coroutines::push_coroutine< Arg >::iterator type; }; + + template< typename R > +-struct range_mutable_iterator< coroutines::pull_coroutine< R >, void > ++struct range_mutable_iterator< coroutines::pull_coroutine< R > > + { typedef typename coroutines::pull_coroutine< R >::iterator type; }; + + } +-- +2.24.1 + -- 2.21.0 (Apple Git-122)
|
|
|
|
[PATCH 2/2] packagegroup-go-sdk-target: Add go to packagegroup
This ensures that we have go compiler installed into image along with
runtime Signed-off-by: Khem Raj <raj.khem@...> --- meta/recipes-core/packagegroups/packagegroup-go-sdk-target.bb | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/recipes-core/packagegroups/packagegroup-go-sdk-target.bb b/meta/recipes-core/packagegroups/packagegroup-go-sdk-target.bb index 86c71900ec..9a52b0781c 100644 --- a/meta/recipes-core/packagegroups/packagegroup-go-sdk-target.bb +++ b/meta/recipes-core/packagegroups/packagegroup-go-sdk-target.bb @@ -3,6 +3,7 @@ SUMMARY = "Target packages for the Go SDK" inherit packagegroup goarch RDEPENDS_${PN} = " \ + go \ go-runtime \ go-runtime-dev \ go-runtime-staticdev \ -- 2.26.2
|
|
|
|
[PATCH 1/2] go: Rely on go-runtime to provide needed modules
go compiler is including go/src/cmd modules in -dev package which is in
conflict with go-runtime-dev which provides exact same copy of this module along with other runtime modules, as a result when both go-dev and go-runtime-dev are included in image then it results in rootfs failures, here lets make go depend on go-runtime and dont install the cmd module here explicitly. Signed-off-by: Khem Raj <raj.khem@...> --- meta/recipes-devtools/go/go-target.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-devtools/go/go-target.inc b/meta/recipes-devtools/go/go-target.inc index 316bf6f038..8e44247031 100644 --- a/meta/recipes-devtools/go/go-target.inc +++ b/meta/recipes-devtools/go/go-target.inc @@ -34,12 +34,12 @@ do_install() { install -m 0755 $f ${D}${libdir}/go/bin/ ln -sf ../${baselib}/go/bin/$name ${D}${bindir}/ done + rm -rf ${D}${libdir}/go/src } PACKAGES = "${PN} ${PN}-dev" FILES_${PN} = "${libdir}/go/bin ${libdir}/go/pkg/tool/${TARGET_GOTUPLE} ${bindir}" -FILES_${PN}-dev = "${libdir}/go" -RDEPENDS_${PN}-dev = "perl bash" +RDEPENDS_${PN} = "go-runtime" INSANE_SKIP_${PN} = "ldflags" BBCLASSEXTEND = "nativesdk" -- 2.26.2
|
|
|
|
[master][dunfell][PATCH] scripts/install-buildtools: bump to 3.1 release by default
Tim Orling <timothy.t.orling@...>
By default, use the extended buildtools installer from the
Yocto Project 3.1 "dunfell" release. Signed-off-by: Tim Orling <timothy.t.orling@...> --- scripts/install-buildtools | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/install-buildtools b/scripts/install-buildtools index 9da364981e5..c6b3a1eed72 100755 --- a/scripts/install-buildtools +++ b/scripts/install-buildtools @@ -56,9 +56,9 @@ logger = scriptutils.logger_create(PROGNAME, stream=sys.stdout) DEFAULT_INSTALL_DIR = os.path.join(os.path.split(scripts_path)[0],'buildtools') DEFAULT_BASE_URL = 'http://downloads.yoctoproject.org/releases/yocto' -DEFAULT_RELEASE = 'yocto-3.1_M3' -DEFAULT_INSTALLER_VERSION = '3.0+snapshot' -DEFAULT_BUILDDATE = "20200315" +DEFAULT_RELEASE = 'yocto-3.1' +DEFAULT_INSTALLER_VERSION = '3.1' +DEFAULT_BUILDDATE = '' # Python version sanity check if not (sys.version_info.major == 3 and sys.version_info.minor >= 4): -- 2.24.0
|
|
|
|
✗ patchtest: failure for boost: revert 1.72.0 regression
Patchwork
== Series Details ==
Series: boost: revert 1.72.0 regression Revision: 1 URL : https://patchwork.openembedded.org/series/23828/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures: * Issue Added patch file is missing Upstream-Status in the header [test_upstream_status_presence_format] Suggested fix Add Upstream-Status: <Valid status> to the header of meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch Standard format Upstream-Status: <Valid status> Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], Submitted [where] If you believe any of these test results are incorrect, please reply to the mailing list (openembedded-core@...) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...). --- Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
|
|
|
|
[PATCH v2] boost: revert 1.72.0 regression
Andrew Geissler
https://www.boost.org/users/history/version_1_72_0.html documents a
"Known Issue" and has a revert patch for an issue that causes code to fail to compile that includes the coroutine function. Without this patch, code which includes the asymmetric_coroutine.hpp will fail to compile. Upstream-Status: Backport [https://github.com/boostorg/coroutine/commit/9c73b2f7c1759a9508ba8780b38dc15f07f1a447] Signed-off-by: Andrew Geissler <geissonator@...> v2: added Signed-off-by to patch added Upstream-Status tag --- meta/recipes-support/boost/boost_1.72.0.bb | 1 + ...001-revert-cease-dependence-on-range.patch | 51 +++++++++++++++++++ 2 files changed, 52 insertions(+) create mode 100644 meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch diff --git a/meta/recipes-support/boost/boost_1.72.0.bb b/meta/recipes-support/boost/boost_1.72.0.bb index 5e9e0d87d7..0b7badbc76 100644 --- a/meta/recipes-support/boost/boost_1.72.0.bb +++ b/meta/recipes-support/boost/boost_1.72.0.bb @@ -7,4 +7,5 @@ SRC_URI += "file://arm-intrinsics.patch \ file://0001-Apply-boost-1.62.0-no-forced-flags.patch.patch \ file://0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch \ file://0001-dont-setup-compiler-flags-m32-m64.patch \ + file://0001-revert-cease-dependence-on-range.patch \ " diff --git a/meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch b/meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch new file mode 100644 index 0000000000..e11f0cf527 --- /dev/null +++ b/meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch @@ -0,0 +1,51 @@ +From 436e1dbe6fcd31523d261d18ad011392f1d6fbbc Mon Sep 17 00:00:00 2001 +From: Oliver Kowalke <oliver.kowalke@...> +Date: Sun, 1 Dec 2019 20:40:28 +0100 +Subject: [PATCH] Revert "Cease dependence on Range" + +This reverts commit 0c556bb59241e682bbcd3f572815149c5a9b17db. + +see #44 (One test fails to compile after boostorg/coroutine submodule updated) + +Signed-off-by: Andrew Geissler <geissonator@...> +--- + boost/coroutine/asymmetric_coroutine.hpp | 12 +++--------- + 1 file changed, 3 insertions(+), 9 deletions(-) + +diff --git a/boost/coroutine/asymmetric_coroutine.hpp b/boost/coroutine/asymmetric_coroutine.hpp +index ea96981..640896f 100644 +--- a/boost/coroutine/asymmetric_coroutine.hpp ++++ b/boost/coroutine/asymmetric_coroutine.hpp +@@ -14,6 +14,7 @@ + #include <boost/assert.hpp> + #include <boost/config.hpp> + #include <boost/move/move.hpp> ++#include <boost/range.hpp> + #include <boost/throw_exception.hpp> + #include <boost/utility/explicit_operator_bool.hpp> + +@@ -2354,19 +2355,12 @@ end( push_coroutine< R > & c) + + } + +-// forward declaration of Boost.Range traits to break dependency on it +-template<typename C, typename Enabler> +-struct range_mutable_iterator; +- +-template<typename C, typename Enabler> +-struct range_const_iterator; +- + template< typename Arg > +-struct range_mutable_iterator< coroutines::push_coroutine< Arg >, void > ++struct range_mutable_iterator< coroutines::push_coroutine< Arg > > + { typedef typename coroutines::push_coroutine< Arg >::iterator type; }; + + template< typename R > +-struct range_mutable_iterator< coroutines::pull_coroutine< R >, void > ++struct range_mutable_iterator< coroutines::pull_coroutine< R > > + { typedef typename coroutines::pull_coroutine< R >::iterator type; }; + + } +-- +2.24.1 + -- 2.21.0 (Apple Git-122)
|
|
|
|
Re: [PATCH 2/2] boost: revert 1.72.0 regression
Alexander Kanavin
You need to sign-off the patch as yourself. Upstream-Status: should be Backport [link to github commit] Alex
On Tue, 21 Apr 2020 at 21:31, Andrew Geissler <geissonator@...> wrote: The patch needs an Upstream-Status. Is it a backport (then the link to repo needs to be provided)?Thanks for the quick review Alexander. My understanding is that boost released 1.72.0 and then found this regression so they provide a link to this patch on their 1.72.0 release page.
|
|
|
|
AUH monthly stats, manual resend
Auto Upgrade Helper
Recipe upgrade statistics:
* Failed (devtool error): 38 build-compare, 2019.08.14-new-commits-available, Paul Eggleton <paul.eggleton@...> python3-gitdb, 4.0.2, Oleksandr Kravchuk <open.source@...> systemd-boot, 245.4, Chen Qi <Qi.Chen@...> automake, 1.16.2, Robert Yang <liezhi.yang@...> ovmf, edk2-stable202002, Ricardo Neri <ricardo.neri-calderon@...> coreutils, 8.32, Chen Qi <Qi.Chen@...> bind, 9.16.2, Armin Kuster <akuster808@...> libdnf, 0.47.0, Alexander Kanavin <alex.kanavin@...> libva-utils, 2.7.1, Anuj Mittal <anuj.mittal@...> gobject-introspection, 1.64.1, Alexander Kanavin <alex.kanavin@...> perl, 5.30.2, Alexander Kanavin <alex.kanavin@...> libevdev, 1.9.0, Anuj Mittal <anuj.mittal@...> libyaml, 0.2.3, Alexander Kanavin <alex.kanavin@...> python3-numpy, 1.18.2, Oleksandr Kravchuk <open.source@...> ghostscript, 9.52, Hongxu Jia <hongxu.jia@...> gettext, 0.20.2, Robert Yang <liezhi.yang@...> rpm, 4.15.1, Mark Hatle <mark.hatle@...> alsa-topology-conf, 1.2.2, Tanu Kaskinen <tanuk@...> e2fsprogs, 1.45.6, Robert Yang <liezhi.yang@...> alsa-lib, 1.2.2, Tanu Kaskinen <tanuk@...> xcb-proto, 1.14, Armin Kuster <akuster808@...> libxcb, 1.14, Armin Kuster <akuster808@...> llvm, 10.0.0, Khem Raj <raj.khem@...> libdrm, 2.4.101, Otavio Salvador <otavio.salvador@...> rt-tests, 1.8, Alexander Kanavin <alex.kanavin@...> sysklogd, 2.1.2, Chen Qi <Qi.Chen@...> apt, 2.0.2, Aníbal Limón <limon.anibal@...> webkitgtk, 2.28.1, Alexander Kanavin <alex.kanavin@...> mc, 4.8.24, Ross Burton <ross.burton@...> lttng-tools, 2.12.0, Richard Purdie <richard.purdie@...> alsa-ucm-conf, 1.2.2, Tanu Kaskinen <tanuk@...> meson, 0.54.0rc1, Alexander Kanavin <alex.kanavin@...> jquery, 3.5.0, Joshua Watt <JPEWhacker@...> cmake, 3.17.1, Pascal Bach <pascal.bach@...> logrotate, 3.16.0, Yi Zhao <yi.zhao@...> glib-2.0, 2.64.2, Anuj Mittal <anuj.mittal@...> ppp, 2.4.8, Hongxu Jia <hongxu.jia@...> kmscube, git-new-commits-available, Carlos Rafael Giani <dv@...> * Failed(do_compile): 32 avahi-ui, 0.8, Yi Zhao <yi.zhao@...> xkeyboard-config, 2.29, Armin Kuster <akuster808@...> go, 1.14.2, Khem Raj <raj.khem@...> strace, 5.6, Robert Yang <liezhi.yang@...> gtk+3, 3.24.18, Ross Burton <ross.burton@...> git, 2.26.1, Robert Yang <liezhi.yang@...> stress-ng, 0.11.07, Anuj Mittal <anuj.mittal@...> rpcsvc-proto, 1.4.1, Khem Raj <raj.khem@...> pulseaudio, 13.99.1, Tanu Kaskinen <tanuk@...> epiphany, 3.36.1, Alexander Kanavin <alex.kanavin@...> libnotify, 0.7.9, Anuj Mittal <anuj.mittal@...> alsa-utils, 1.2.2, Tanu Kaskinen <tanuk@...> libunwind, 1.4.0, Bruce Ashfield <bruce.ashfield@...> avahi, 0.8, Yi Zhao <yi.zhao@...> wpebackend-fdo, 1.6.0, Alexander Kanavin <alex.kanavin@...> vulkan-headers, 1.2.135.0, Anuj Mittal <anuj.mittal@...> glib-networking, 2.64.2, Anuj Mittal <anuj.mittal@...> elfutils, 0.179, Hongxu Jia <hongxu.jia@...> libcap, 2.33, Yi Zhao <yi.zhao@...> connman, 1.38, Changhyeok Bae <changhyeok.bae@...> libxcrypt, 4.4.16, Khem Raj <raj.khem@...> gcr, 3.36.0, Alexander Kanavin <alex.kanavin@...> clutter-1.0, 1.26.4, Ross Burton <ross.burton@...> gptfdisk, 1.0.5, Alexander Kanavin <alex.kanavin@...> go-runtime, 1.14.2, Khem Raj <raj.khem@...> mesa, 20.0.4, Otavio Salvador <otavio.salvador@...> vulkan-loader, 1.2.135.0, Anuj Mittal <anuj.mittal@...> vulkan-demos, git-new-commits-available, Ross Burton <ross.burton@...> vte, 0.60.1, Anuj Mittal <anuj.mittal@...> rng-tools, 6.10, Anuj Mittal <anuj.mittal@...> u-boot, 2020.04, Marek Vasut <marek.vasut@...> vulkan-tools, 1.2.135.0, Anuj Mittal <anuj.mittal@...> * Succeeded: 65 ruby, 2.7.1, Ross Burton <ross.burton@...> man-pages, 5.06, Hongxu Jia <hongxu.jia@...> piglit, 1.0-new-commits-available, Ross Burton <ross.burton@...> asciidoc, 8.6.10, Yi Zhao <yi.zhao@...> python3-testtools, 2.4.0, Oleksandr Kravchuk <open.source@...> libusb1, 1.0.23, Anuj Mittal <anuj.mittal@...> atk, 2.36.0, Tim Orling <timothy.t.orling@...> adwaita-icon-theme, 3.36.0, Ross Burton <ross.burton@...> python3-smmap, 3.0.1, Oleksandr Kravchuk <open.source@...> vala, 0.48.3, Alexander Kanavin <alex.kanavin@...> librepo, 1.11.3, Alexander Kanavin <alex.kanavin@...> lttng-modules, 2.12.0, Richard Purdie <richard.purdie@...> hwlatdetect, 1.8, Alexander Kanavin <alex.kanavin@...> msmtp, 1.8.8, Alexander Kanavin <alex.kanavin@...> createrepo-c, 0.15.9, Alexander Kanavin <alex.kanavin@...> xz, 5.2.5, Denys Dmytriyenko <denys@...> at-spi2-core, 2.36.0, Tim Orling <timothy.t.orling@...> python3-subunit, 1.4.0, Oleksandr Kravchuk <open.source@...> libxcrypt-compat, 4.4.16, Khem Raj <raj.khem@...> acpica, 20200326, Ross Burton <ross.burton@...> libva, 2.7.0, Anuj Mittal <anuj.mittal@...> python3-setuptools, 46.1.3, Oleksandr Kravchuk <open.source@...> cogl-1.0, 1.22.6, Ross Burton <ross.burton@...> ccache, 3.7.9, Robert Yang <liezhi.yang@...> man-db, 2.9.1, Hongxu Jia <hongxu.jia@...> gawk, 5.1.0, Chen Qi <Qi.Chen@...> libdazzle, 3.36.0, Alexander Kanavin <alex.kanavin@...> sudo, 1.8.31p1, Chen Qi <Qi.Chen@...> python3-mako, 1.1.2, Oleksandr Kravchuk <open.source@...> puzzles, 0.0-new-commits-available, Anuj Mittal <anuj.mittal@...> bison, 3.5.4, Chen Qi <Qi.Chen@...> btrfs-tools, 5.6, Alexander Kanavin <alex.kanavin@...> python3-pygobject, 3.36.0, Oleksandr Kravchuk <open.source@...> python3-pygments, 2.6.1, Oleksandr Kravchuk <open.source@...> u-boot-tools, 2020.04, Marek Vasut <marek.vasut@...> x264, r2991-new-commits-available, Anuj Mittal <anuj.mittal@...> diffoscope, 141, Joshua Watt <JPEWhacker@...> alsa-plugins, 1.2.2, Tanu Kaskinen <tanuk@...> dnf, 4.2.21, Alexander Kanavin <alex.kanavin@...> at-spi2-atk, 2.34.2, Tim Orling <timothy.t.orling@...> libical, 3.0.8, Ross Burton <ross.burton@...> ell, 0.31, Oleksandr Kravchuk <open.source@...> python3-pbr, 5.4.5, Oleksandr Kravchuk <open.source@...> kmod, 27, Chen Qi <Qi.Chen@...> libsolv, 0.7.11, Anuj Mittal <anuj.mittal@...> python3-git, 3.1.1, Oleksandr Kravchuk <open.source@...> gnutls, 3.6.13, Armin Kuster <akuster808@...> libtirpc, 1.2.6, Anuj Mittal <anuj.mittal@...> libcomps, 0.1.15, Alexander Kanavin <alex.kanavin@...> mtools, 4.0.24, Anuj Mittal <anuj.mittal@...> libwpe, 1.6.0, Alexander Kanavin <alex.kanavin@...> python3-pycairo, 1.19.1, Oleksandr Kravchuk <open.source@...> dtc, 1.6.0, Alexander Kanavin <alex.kanavin@...> lttng-ust, 2.12.0, Richard Purdie <richard.purdie@...> dpkg, 1.20.0, Aníbal Limón <limon.anibal@...> libinput, 1.15.5, Ross Burton <ross.burton@...> libsecret, 0.20.3, Alexander Kanavin <alex.kanavin@...> alsa-tools, 1.2.2, Tanu Kaskinen <tanuk@...> libsoup-2.4, 2.70.0, Anuj Mittal <anuj.mittal@...> less, 557, Yi Zhao <yi.zhao@...> xorgproto, 2020.1, Armin Kuster <akuster808@...> xserver-xorg, 1.20.8, Armin Kuster <akuster808@...> iproute2, 5.6.0, Changhyeok Bae <changhyeok.bae@...> liburcu, 0.12.0, Alexander Kanavin <alex.kanavin@...> ed, 1.16, Alexander Kanavin <alex.kanavin@...> TOTAL: attempted=135 succeeded=65(48.15%) failed=70(51.85%) Recipe upgrade statistics per Maintainer: Alexander Kanavin <alex.kanavin: attempted=25 succeeded=14(56.00%) failed=11(44.00%) Denys Dmytriyenko <denys: attempted=1 succeeded=1(100.00%) failed=0(0.00%) Mark Hatle <mark.hatle: attempted=1 succeeded=0(0.00%) failed=1(100.00%) Joshua Watt <JPEWhacker: attempted=2 succeeded=1(50.00%) failed=1(50.00%) Otavio Salvador <otavio.salvador: attempted=2 succeeded=0(0.00%) failed=2(100.00%) Changhyeok Bae <changhyeok.bae: attempted=2 succeeded=1(50.00%) failed=1(50.00%) Richard Purdie <richard.purdie: attempted=3 succeeded=2(66.67%) failed=1(33.33%) Carlos Rafael Giani <dv: attempted=1 succeeded=0(0.00%) failed=1(100.00%) Paul Eggleton <paul.eggleton: attempted=1 succeeded=0(0.00%) failed=1(100.00%) Armin Kuster <akuster808: attempted=7 succeeded=3(42.86%) failed=4(57.14%) Pascal Bach <pascal.bach: attempted=1 succeeded=0(0.00%) failed=1(100.00%) Oleksandr Kravchuk <open.source: attempted=13 succeeded=11(84.62%) failed=2(15.38%) Yi Zhao <yi.zhao: attempted=6 succeeded=2(33.33%) failed=4(66.67%) Ricardo Neri <ricardo.neri-calderon: attempted=1 succeeded=0(0.00%) failed=1(100.00%) Marek Vasut <marek.vasut: attempted=2 succeeded=1(50.00%) failed=1(50.00%) Anuj Mittal <anuj.mittal: attempted=19 succeeded=8(42.11%) failed=11(57.89%) Ross Burton <ross.burton: attempted=11 succeeded=7(63.64%) failed=4(36.36%) Bruce Ashfield <bruce.ashfield: attempted=1 succeeded=0(0.00%) failed=1(100.00%) Aníbal Limón <limon.anibal: attempted=2 succeeded=1(50.00%) failed=1(50.00%) Tim Orling <timothy.t.orling: attempted=3 succeeded=3(100.00%) failed=0(0.00%) Tanu Kaskinen <tanuk: attempted=7 succeeded=2(28.57%) failed=5(71.43%) Robert Yang <liezhi.yang: attempted=6 succeeded=1(16.67%) failed=5(83.33%) Khem Raj <raj.khem: attempted=6 succeeded=1(16.67%) failed=5(83.33%) Chen Qi <Qi.Chen: attempted=7 succeeded=4(57.14%) failed=3(42.86%) Hongxu Jia <hongxu.jia: attempted=5 succeeded=2(40.00%) failed=3(60.00%)
|
|
|
|
This is a test mail from AUH, please ignore
Auto Upgrade Helper
|
|
|
|
OpenEmbedded developers virtual happy hour
Philip Balister
We (the OpenEmbedded board, with help from Automotive Grade Linux who
are providing the meeting "space") would like to invite you a a virtual happy hour on April 29 at Noon EDT, 6PM CET (Is that the right TZ) We'd like to come and show off their projects and give us all a chance to say hello since so many of our chances to meet in person are not happening for the foreseeable future. We would also like to discuss what kind of events we should host in the future to help build the community. Topic: OpenEmbedded Developer Happpy Hour Time: Apr 29, 2020 06:00 PM Amsterdam, Berlin, Rome, Stockholm, Vienna Join Zoom Meeting https://zoom.us/j/94557245630 Meeting ID: 945 5724 5630
|
|
|
|
Re: [PATCH 2/2] boost: revert 1.72.0 regression
Andrew Geissler
The patch needs an Upstream-Status. Is it a backport (then the link to repo needs to be provided)?Thanks for the quick review Alexander. My understanding is that boost released 1.72.0 and then found this regression so they provide a link to this patch on their 1.72.0 release page. Here's a link to the upstream revert commit: https://github.com/boostorg/coroutine/commit/9c73b2f7c1759a9508ba8780b38dc15f07f1a447 I saw an automated response from patchwork asking for a Signed-off-by tag for the patch but since the upstream commit does not have it, not sure what to do?
|
|
|
|
✗ patchtest: failure for "boost: switch over to sourcefo..." and 1 more
Patchwork
== Series Details ==
Series: "boost: switch over to sourcefo..." and 1 more Revision: 1 URL : https://patchwork.openembedded.org/series/23826/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures: * Issue A patch file has been added, but does not have a Signed-off-by tag [test_signed_off_by_presence] Suggested fix Sign off the added patch file (meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch) * Issue Added patch file is missing Upstream-Status in the header [test_upstream_status_presence_format] Suggested fix Add Upstream-Status: <Valid status> to the header of meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch Standard format Upstream-Status: <Valid status> Valid status Pending, Accepted, Backport, Denied, Inappropriate [reason], Submitted [where] If you believe any of these test results are incorrect, please reply to the mailing list (openembedded-core@...) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...). --- Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
|
|
|
|
Re: [PATCH 2/2] boost: revert 1.72.0 regression
Alexander Kanavin
The patch needs an Upstream-Status. Is it a backport (then the link to repo needs to be provided)? Alex
On Tue, 21 Apr 2020 at 18:12, Andrew Geissler <geissonator@...> wrote: https://www.boost.org/users/history/version_1_72_0.html documents a
|
|
|
|
[PATCH 2/2] boost: revert 1.72.0 regression
Andrew Geissler
https://www.boost.org/users/history/version_1_72_0.html documents a
"Known Issue" and has a revert patch for an issue that causes code to fail to compile that includes the coroutine function. Without this patch, code which includes the asymmetric_coroutine.hpp will fail to compile. Signed-off-by: Andrew Geissler <geissonator@...> --- meta/recipes-support/boost/boost_1.72.0.bb | 1 + ...001-revert-cease-dependence-on-range.patch | 49 +++++++++++++++++++ 2 files changed, 50 insertions(+) create mode 100644 meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch diff --git a/meta/recipes-support/boost/boost_1.72.0.bb b/meta/recipes-support/boost/boost_1.72.0.bb index 5e9e0d87d7..0b7badbc76 100644 --- a/meta/recipes-support/boost/boost_1.72.0.bb +++ b/meta/recipes-support/boost/boost_1.72.0.bb @@ -7,4 +7,5 @@ SRC_URI += "file://arm-intrinsics.patch \ file://0001-Apply-boost-1.62.0-no-forced-flags.patch.patch \ file://0001-Don-t-set-up-arch-instruction-set-flags-we-do-that-o.patch \ file://0001-dont-setup-compiler-flags-m32-m64.patch \ + file://0001-revert-cease-dependence-on-range.patch \ " diff --git a/meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch b/meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch new file mode 100644 index 0000000000..a6002074ab --- /dev/null +++ b/meta/recipes-support/boost/files/0001-revert-cease-dependence-on-range.patch @@ -0,0 +1,49 @@ +From 436e1dbe6fcd31523d261d18ad011392f1d6fbbc Mon Sep 17 00:00:00 2001 +From: Oliver Kowalke <oliver.kowalke@...> +Date: Sun, 1 Dec 2019 20:40:28 +0100 +Subject: [PATCH] Revert "Cease dependence on Range" + +This reverts commit 0c556bb59241e682bbcd3f572815149c5a9b17db. + +see #44 (One test fails to compile after boostorg/coroutine submodule updated) +--- + boost/coroutine/asymmetric_coroutine.hpp | 12 +++--------- + 1 file changed, 3 insertions(+), 9 deletions(-) + +diff --git a/boost/coroutine/asymmetric_coroutine.hpp b/boost/coroutine/asymmetric_coroutine.hpp +index ea96981..640896f 100644 +--- a/boost/coroutine/asymmetric_coroutine.hpp ++++ b/boost/coroutine/asymmetric_coroutine.hpp +@@ -14,6 +14,7 @@ + #include <boost/assert.hpp> + #include <boost/config.hpp> + #include <boost/move/move.hpp> ++#include <boost/range.hpp> + #include <boost/throw_exception.hpp> + #include <boost/utility/explicit_operator_bool.hpp> + +@@ -2354,19 +2355,12 @@ end( push_coroutine< R > & c) + + } + +-// forward declaration of Boost.Range traits to break dependency on it +-template<typename C, typename Enabler> +-struct range_mutable_iterator; +- +-template<typename C, typename Enabler> +-struct range_const_iterator; +- + template< typename Arg > +-struct range_mutable_iterator< coroutines::push_coroutine< Arg >, void > ++struct range_mutable_iterator< coroutines::push_coroutine< Arg > > + { typedef typename coroutines::push_coroutine< Arg >::iterator type; }; + + template< typename R > +-struct range_mutable_iterator< coroutines::pull_coroutine< R >, void > ++struct range_mutable_iterator< coroutines::pull_coroutine< R > > + { typedef typename coroutines::pull_coroutine< R >::iterator type; }; + + } +-- +2.24.1 + -- 2.21.0 (Apple Git-122)
|
|
|
|
[PATCH 1/2] boost: switch over to sourceforge
Andrew Geissler
dl.binary has a monthly download limit. The issue is documented in
https://github.com/boostorg/boost/issues/299 Yocto has backup/caching for issues like this but it's best to not contribute to that download limit if the same file is hosted over at sourceforge. Signed-off-by: Andrew Geissler <geissonator@...> --- meta/recipes-support/boost/boost-1.72.0.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-support/boost/boost-1.72.0.inc b/meta/recipes-support/boost/boost-1.72.0.inc index 55a095bf1c..3a7ea2c06e 100644 --- a/meta/recipes-support/boost/boost-1.72.0.inc +++ b/meta/recipes-support/boost/boost-1.72.0.inc @@ -11,7 +11,7 @@ BOOST_VER = "${@"_".join(d.getVar("PV").split("."))}" BOOST_MAJ = "${@"_".join(d.getVar("PV").split(".")[0:2])}" BOOST_P = "boost_${BOOST_VER}" -SRC_URI = "https://dl.bintray.com/boostorg/release/${PV}/source/${BOOST_P}.tar.bz2" +SRC_URI = "${SOURCEFORGE_MIRROR}/project/boost/boost/${PV}/${BOOST_P}.tar.bz2" SRC_URI[md5sum] = "cb40943d2a2cb8ce08d42bc48b0f84f0" SRC_URI[sha256sum] = "59c9b274bc451cf91a9ba1dd2c7fdcaf5d60b1b3aa83f2c9fa143417cc660722" -- 2.21.0 (Apple Git-122)
|
|
|
|
✗ patchtest: failure for "oeqa/selftest: Add test for co..." and 1 more
Patchwork
== Series Details ==
Series: "oeqa/selftest: Add test for co..." and 1 more Revision: 1 URL : https://patchwork.openembedded.org/series/23824/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the proposed series by patchtest resulting in the following failures: * Issue Errors in your Python code were encountered [test_pylint] Suggested fix Correct the lines introduced by your patch Output Please, fix the listed issues: meta/lib/oeqa/selftest/cases/sysroot.py does not exist If you believe any of these test results are incorrect, please reply to the mailing list (openembedded-core@...) raising your concerns. Otherwise we would appreciate you correcting the issues and submitting a new version of the patchset if applicable. Please ensure you add/increment the version number when sending the new version (i.e. [PATCH] -> [PATCH v2] -> [PATCH v3] -> ...). --- Guidelines: https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe
|
|
|
|
[PATCH 2/2] staging: Fix overlapping file failures
Richard Purdie
If there are different providers of a file and they are swiched when the
recipe isn't machine specific, we can get tracebacks due to the overlapping files. The issue is that the previous provider isn't uninstalled since the system can't tell whether some later task needs them. By tracking which tasks we depend upon, the code can now choose to uninstall more things since a later task can reinstall if/as needed. The code here was to protect against code with two different tasks running in parallel which is still protected agaisnt. [YOCTO #13702] Signed-off-by: Richard Purdie <richard.purdie@...> --- meta/classes/staging.bbclass | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/meta/classes/staging.bbclass b/meta/classes/staging.bbclass index 5dab42745f7..5b04f88b2d8 100644 --- a/meta/classes/staging.bbclass +++ b/meta/classes/staging.bbclass @@ -277,11 +277,13 @@ python extend_recipe_sysroot() { start = None configuredeps = [] + owntaskdeps = [] for dep in taskdepdata: data = taskdepdata[dep] if data[1] == mytaskname and data[0] == pn: start = dep - break + elif data[0] == pn: + owntaskdeps.append(data[1]) if start is None: bb.fatal("Couldn't find ourself in BB_TASKDEPDATA?") @@ -427,7 +429,7 @@ python extend_recipe_sysroot() { # Was likely already uninstalled continue potential.append(l) - # We need to ensure not other task needs this dependency. We hold the sysroot + # We need to ensure no other task needs this dependency. We hold the sysroot # lock so we ca search the indexes to check if potential: for i in glob.glob(depdir + "/index.*"): @@ -435,6 +437,11 @@ python extend_recipe_sysroot() { continue with open(i, "r") as f: for l in f: + if l.startswith("TaskDeps:"): + prevtasks = l.split()[1:] + if mytaskname in prevtasks: + # We're a dependency of this task so we can clear items out the sysroot + break l = l.strip() if l in potential: potential.remove(l) @@ -588,6 +595,7 @@ python extend_recipe_sysroot() { os.symlink(manifests[dep], depdir + "/" + c + ".complete") with open(taskindex, "w") as f: + f.write("TaskDeps: " + " ".join(owntaskdeps) + "\n") for l in sorted(installed): f.write(l + "\n") -- 2.25.1
|
|
|
|
[PATCH 1/2] oeqa/selftest: Add test for conflicting sysroot provider
Richard Purdie
sysroot-test depends on virtual/sysroot-test which we build for one machine,
switch machine, switch provider of virtual/sysroot-test and check that the sysroot is correctly cleaned up. The files in the two providers overlap so can cause errors if the sysroot code doesn't function correctly. Yes, sysroot-test should be machine specific really to avoid this, however the sysroot cleanup should also work. This adds a test for bug: [YOCTO #13702] Signed-off-by: Richard Purdie <richard.purdie@...> --- .../sysroot-test/sysroot-test-arch1_1.0.bb | 12 ++++++ .../sysroot-test/sysroot-test-arch2_1.0.bb | 12 ++++++ .../sysroot-test/sysroot-test_1.0.bb | 4 ++ meta/lib/oeqa/selftest/cases/sysroot.py | 37 +++++++++++++++++++ 4 files changed, 65 insertions(+) create mode 100644 meta-selftest/recipes-test/sysroot-test/sysroot-test-arch1_1.0.bb create mode 100644 meta-selftest/recipes-test/sysroot-test/sysroot-test-arch2_1.0.bb create mode 100644 meta-selftest/recipes-test/sysroot-test/sysroot-test_1.0.bb create mode 100644 meta/lib/oeqa/selftest/cases/sysroot.py diff --git a/meta-selftest/recipes-test/sysroot-test/sysroot-test-arch1_1.0.bb b/meta-selftest/recipes-test/sysroot-test/sysroot-test-arch1_1.0.bb new file mode 100644 index 00000000000..0b4ed2ef052 --- /dev/null +++ b/meta-selftest/recipes-test/sysroot-test/sysroot-test-arch1_1.0.bb @@ -0,0 +1,12 @@ +LICENSE = "CLOSED" + +PROVIDES = "virtual/sysroot-test" +INHIBIT_DEFAULT_DEPS = "1" +PACKAGE_ARCH = "${MACHINE_ARCH}" + +TESTSTRING ?= "1" + +do_install() { + install -d ${D}${includedir} + echo "# test ${TESTSTRING}" > ${D}${includedir}/sysroot-test.h +} \ No newline at end of file diff --git a/meta-selftest/recipes-test/sysroot-test/sysroot-test-arch2_1.0.bb b/meta-selftest/recipes-test/sysroot-test/sysroot-test-arch2_1.0.bb new file mode 100644 index 00000000000..f8b50acda2c --- /dev/null +++ b/meta-selftest/recipes-test/sysroot-test/sysroot-test-arch2_1.0.bb @@ -0,0 +1,12 @@ +LICENSE = "CLOSED" + +PROVIDES = "virtual/sysroot-test" +INHIBIT_DEFAULT_DEPS = "1" +PACKAGE_ARCH = "${MACHINE_ARCH}" + +TESTSTRING ?= "2" + +do_install() { + install -d ${D}${includedir} + echo "# test ${TESTSTRING}" > ${D}${includedir}/sysroot-test.h +} \ No newline at end of file diff --git a/meta-selftest/recipes-test/sysroot-test/sysroot-test_1.0.bb b/meta-selftest/recipes-test/sysroot-test/sysroot-test_1.0.bb new file mode 100644 index 00000000000..bec0eecb980 --- /dev/null +++ b/meta-selftest/recipes-test/sysroot-test/sysroot-test_1.0.bb @@ -0,0 +1,4 @@ +SUMMARY = "Virtual provider sysroot test" +LICENSE = "CLOSED" +INHIBIT_DEFAULT_DEPS = "1" +DEPENDS = "virtual/sysroot-test" diff --git a/meta/lib/oeqa/selftest/cases/sysroot.py b/meta/lib/oeqa/selftest/cases/sysroot.py new file mode 100644 index 00000000000..6e34927c909 --- /dev/null +++ b/meta/lib/oeqa/selftest/cases/sysroot.py @@ -0,0 +1,37 @@ +# +# SPDX-License-Identifier: MIT +# + +import uuid + +from oeqa.selftest.case import OESelftestTestCase +from oeqa.utils.commands import bitbake + +class SysrootTests(OESelftestTestCase): + def test_sysroot_cleanup(self): + """ + Build sysroot test which depends on virtual/sysroot-test for one machine, + switch machine, switch provider of virtual/sysroot-test and check that the + sysroot is correctly cleaned up. The files in the two providers overlap + so can cause errors if the sysroot code doesn't function correctly. + Yes, sysroot-test should be machine specific really to avoid this, however + the sysroot cleanup should also work [YOCTO #13702]. + """ + + uuid1 = uuid.uuid4() + uuid2 = uuid.uuid4() + + self.write_config(""" +PREFERRED_PROVIDER_virtual/sysroot-test = "sysroot-test-arch1" +MACHINE = "qemux86" +TESTSTRING_pn-sysroot-test-arch1 = "%s" +TESTSTRING_pn-sysroot-test-arch2 = "%s" +""" % (uuid1, uuid2)) + bitbake("sysroot-test") + self.write_config(""" +PREFERRED_PROVIDER_virtual/sysroot-test = "sysroot-test-arch2" +MACHINE = "qemux86copy" +TESTSTRING_pn-sysroot-test-arch1 = "%s" +TESTSTRING_pn-sysroot-test-arch2 = "%s" +""" % (uuid1, uuid2)) + bitbake("sysroot-test") -- 2.25.1
|
|
|
|
Yocto Project Status WW15'20
Stephen Jolley
Current Dev Position: YP 3.1 Being released Next Deadline: YP 3.1 release date 2020/4/24
Next Team Meetings:
Key Status/Updates:
YP 3.1 Dates:
YP 3.2 Milestone Dates:
Planned upcoming dot releases:
Tracking Metrics:
The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at: https://wiki.yoctoproject.org/wiki/TSC
The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status
[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]
Thanks,
Stephen K. Jolley Yocto Project Program Manager ( Cell: (208) 244-4460 * Email: sjolley.yp.pm@...
|
|
|
|
Re: [oe][zeus][PATCH] git: Security Advisory - git - CVE-2020-5260
Anuj Mittal
On Tue, 2020-04-21 at 07:14 -0700, akuster wrote:
It affects both. There's a patch on list for master too: https://lists.openembedded.org/g/openembedded-core/message/137255 Thanks, Anuj
|
|
|