Run-time dependency libudev found: NO (tried cmake) meson.build:172:2: ERROR: Invalid version of dependency, need 'libudev' ['>= 228'] found '220'. A full log can be found at /var/tmp/portage/x11-wm/mutter-3.32.2/work/mutter-3.32.2-build/meson-logs/meson-log.txt * ERROR: x11-wm/mutter-3.32.2::gentoo failed (configure phase): ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome-20191021-012725 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * clang: clang version 9.0.0 (tags/RELEASE_900/final) Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/9/bin llvm: 9.0.0 Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.38.0 * java-config: The following VMs are available for generation-2: 1) IcedTea JDK 3.13.0 [icedtea-8] *) IcedTea JDK 3.13.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-8 [2] icedtea-bin-8 system-vm repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Sat, 26 Oct 2019 15:25:45 +0000 emerge -qpvO x11-wm/mutter [ebuild N ] x11-wm/mutter-3.32.2 USE="elogind introspection udev -gles2 -screencast -systemd -test -wayland" INPUT_DEVICES="-wacom"
Created attachment 594066 [details] emerge-info.txt
Created attachment 594068 [details] emerge-history.txt
Created attachment 594070 [details] environment
Created attachment 594072 [details] etc.portage.tbz2
Created attachment 594074 [details] logs.tbz2
Created attachment 594076 [details] temp.tbz2
Created attachment 594078 [details] x11-wm:mutter-3.32.2:20191026-162212.log
would you have eudev installed, by any chance?
(In reply to Rémi Cardona from comment #8) > would you have eudev installed, by any chance? The already attached emerge-history.txt denies this.
I'm not sure how your emerge-history.txt file is supposed to work, but it shows virtual/libudev-232 being installed, with no actual provider (eudev, udev, systemd) being installed. Also the version 232 was removed the day after you reported this bug, because it (wrongly) allowed older eudev here. I think you did have eudev as your virtual/libudev provider, but this is now fixed (not allowing unusable eudev) in later versions of that virtual. I believe we can close this as fixed.
(In reply to Ben Kohler from comment #10) > I'm not sure how your emerge-history.txt file is supposed to work, but it > shows virtual/libudev-232 being installed, with no actual provider (eudev, > udev, systemd) being installed. It is created immediately after the failed emerge operation. No virtual/* package is not explictely emerged. Well, if it is replicatable we'll see it.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5f9ff4da7857ae9d968551fb4f1af497996b4d5c commit 5f9ff4da7857ae9d968551fb4f1af497996b4d5c Author: Mart Raudsepp <leio@gentoo.org> AuthorDate: 2020-01-31 19:53:32 +0000 Commit: Mart Raudsepp <leio@gentoo.org> CommitDate: 2020-01-31 19:53:32 +0000 x11-wm/mutter: ensure suitable udev provider from virtual/libudev dep virtul/libudev-232-r0 was broken by assuming older eudev provides >=232 libudev pkg-config version, but it didn't. -r1 and subsequent revisions fixed it. Depend on them to ensure some old eudev using system gets eudev upgraded before mutter. Closes: https://bugs.gentoo.org/698612 Package-Manager: Portage-2.3.84, Repoman-2.3.20 Signed-off-by: Mart Raudsepp <leio@gentoo.org> x11-wm/mutter/mutter-3.32.2.ebuild | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
