Host machine cpu: x86_64 ../systemd-249/meson.build:38:3: ERROR: Object <[BooleanHolder] holds [bool]: False> of type bool does not support the `+` operator. A full log can be found at /var/tmp/portage/sys-fs/udev-249-r3/work/systemd-249-abi_x86_64.amd64/meson-logs/meson-log.txt * ERROR: sys-fs/udev-249-r3::gentoo failed (configure phase): * (no error message) ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome-j4-20211115-195452 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.2.0 * /usr/lib/llvm/13 13.0.0 Python 3.9.8 Available Rust versions: [1] rust-1.56.1 * php cli: HEAD of ::gentoo commit 1b324e35e6c419e1fdd955584a3a73a4ef330db1 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Mon Nov 15 19:51:35 2021 +0000 2021-11-15 19:51:31 UTC emerge -qpvO sys-fs/udev [ebuild R ] sys-fs/udev-249-r3 USE="acl (split-usr) -kmod* (-selinux) -test" ABI_X86="(64) -32 (-x32)"
Created attachment 751458 [details] emerge-info.txt
Created attachment 751462 [details] emerge-history.txt
Created attachment 751466 [details] environment
Created attachment 751470 [details] etc.portage.tar.bz2
Created attachment 751474 [details] logs.tar.bz2
Created attachment 751478 [details] sys-fs:udev-249-r3:20211115-225530.log
Created attachment 751482 [details] temp.tar.bz2
Maybe we should just pick up the latest point release (although very little with udev has changed) rather than adding yet another copy of the same patch for this (and we can drop the duplicate linux-headers patches then too).
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1f391b0c8868b6ab3e12dc59a66ef6a6af0e0a1f commit 1f391b0c8868b6ab3e12dc59a66ef6a6af0e0a1f Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2021-11-18 20:50:25 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2021-11-18 20:51:01 +0000 sys-fs/udev: add 249.6 Closes: https://bugs.gentoo.org/823954 Signed-off-by: Mike Gilbert <floppym@gentoo.org> sys-fs/udev/Manifest | 2 + sys-fs/udev/udev-249.6.ebuild | 296 ++++++++++++++++++++++++++++++++++++++++++ sys-fs/udev/udev-9999.ebuild | 5 +- 3 files changed, 301 insertions(+), 2 deletions(-)
*** Bug 827835 has been marked as a duplicate of this bug. ***
I just ran into this today, BGO's search didn't turn this bug up (as usual) and I submitted #827835 which subsequently got marked as a dupe of this bug. If ~arch meson and udev-249 are incompatible, shouldn't one block the other?
(In reply to Michael Moon from comment #11) > I just ran into this today, BGO's search didn't turn this bug up (as usual) > and I submitted #827835 which subsequently got marked as a dupe of this bug. > > If ~arch meson and udev-249 are incompatible, shouldn't one block the other? There's usually very little value in going around modifying every ~arch thing given the risk of forgetting to clean it up if it's a build time only issue. In this case, for something like udev? Might be worth it, but I'd rather just stable the newer fixed version. I'll file the bug when I'm back at PC.
(In reply to Sam James from comment #12) > (In reply to Michael Moon from comment #11) > > I just ran into this today, BGO's search didn't turn this bug up (as usual) > > and I submitted #827835 which subsequently got marked as a dupe of this bug. > > > > If ~arch meson and udev-249 are incompatible, shouldn't one block the other? > > There's usually very little value in going around modifying every ~arch > thing given the risk of forgetting to clean it up if it's a build time only > issue. > > In this case, for something like udev? Might be worth it, but I'd rather > just stable the newer fixed version. I'll file the bug when I'm back at PC. bug 827853
