[ ok ] * Using python3.13 to build (via PYTHON_COMPAT iteration) >>> Unpacking source... >>> Unpacking tdesktop-5.10.0-full.tar.gz to /var/tmp/portage/net-im/telegram-desktop-5.10.0/work >>> Source unpacked in /var/tmp/portage/net-im/telegram-desktop-5.10.0/work >>> Preparing source in /var/tmp/portage/net-im/telegram-desktop-5.10.0/work/tdesktop-5.10.0-full ... sed: can't read Telegram/Telegram/lib_webview/webview/platform/linux/webview_linux_compositor.h: No such file or directory * Source directory (CMAKE_USE_DIR): "/var/tmp/portage/net-im/telegram-desktop-5.10.0/work/tdesktop-5.10.0-full" * Build directory (BUILD_DIR): "/var/tmp/portage/net-im/telegram-desktop-5.10.0/work/tdesktop-5.10.0-full_build" ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_desktop_plasma-20250105-003003 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-14 * clang version 19.1.6 llvm-config: 19.1.6 Python 3.12.8 go version go1.23.4 linux/amd64 [1] php8.3 * Available Ruby profiles: [1] ruby32 (with Rubygems) * Available Rust versions: [1] rust-bin-1.77.1 [2] rust-bin-1.83.0 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 17.0.13_p11 [openjdk-bin-17] *) Eclipse Temurin JDK 21.0.5_p11 [openjdk-bin-21] 3) Eclipse Temurin JDK 8.432_p06 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-17 [3] openjdk-bin-21 system-vm HEAD of ::gentoo commit 436007e8e92dc92ca99dbd74f0359990c7e37b42 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Jan 7 08:48:41 2025 +0000 2025-01-07 08:48:40 UTC emerge -qpvO =net-im/telegram-desktop-5.10.0 [ebuild N ] net-im/telegram-desktop-5.10.0 USE="X dbus fonts jemalloc libdispatch qt6 screencast wayland -enchant -webkit"
Created attachment 916057 [details] emerge-info.txt
Created attachment 916058 [details] emerge-history.txt
Created attachment 916059 [details] environment
Created attachment 916060 [details] etc.clang.tar.xz
Created attachment 916061 [details] etc.portage.tar.xz
Created attachment 916062 [details] logs.tar.xz
Created attachment 916063 [details] net-im:telegram-desktop-5.10.0:20250107-093642.log
Created attachment 916064 [details] qlist-info.txt.xz
Created attachment 916065 [details] temp.tar.xz
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1289641a284e4a3566601a0c96fe8b3788cdab99 commit 1289641a284e4a3566601a0c96fe8b3788cdab99 Author: Esteve Varela Colominas <esteve.varela@gmail.com> AuthorDate: 2025-01-07 18:31:32 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2025-01-07 19:51:52 +0000 net-im/telegram-desktop: Fix sed operation Closes: https://bugs.gentoo.org/947663 Signed-off-by: Esteve Varela Colominas <esteve.varela@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> ...telegram-desktop-5.10.0.ebuild => telegram-desktop-5.10.0-r1.ebuild} | 2 +- ...elegram-desktop-5.9.0-r1.ebuild => telegram-desktop-5.9.0-r2.ebuild} | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Since the build was failing under certain USE, did this really need the revbump?
(In reply to Zdenek Sojka from comment #11) > Since the build was failing under certain USE, did this really need the > revbump? There wasn't a 'die' there, so I think in some cases, you may have had it build but linked against wayland_compositor_quick automagically which could lead to a broken binpkg. Think of the case where USE=-... but you have the dependencies available for it. (It wasn't failing on the sed itself in toralf's log, rather later on with the target.)
Thank you for the explanation, Sam!
