Project MESSAGE: PDF support: yes [ ok ] ./build: /usr/share/bashdb/bashdb-main.inc: No such file or directory ./build: warning: cannot start debugger; debugging mode disabled ./build: line 3: qcollectiongenerator: command not found mv: cannot stat 'engauge.qch': No such file or directory ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_plasma-20201228-133206 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.2.0 * clang version 11.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/11/bin /usr/lib/llvm/11 11.0.0 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.9 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) Available Ruby profiles: [1] ruby25 (with Rubygems) [2] ruby26 (with Rubygems) [3] ruby27 (with Rubygems) * Available Rust versions: [1] rust-1.48.0 * The following VMs are available for generation-2: 1) OpenJDK 8.272_p10 [openjdk-8] *) AdoptOpenJDK 8.272_p10 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-8 [2] openjdk-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.8.4 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Fri Jan 8 11:05:24 AM UTC 2021 emerge -qpvO media-gfx/engauge [ebuild N ] media-gfx/engauge-10.6 USE="pdf -doc -examples -jpeg2k"
Created attachment 681895 [details] emerge-info.txt
Created attachment 681898 [details] emerge-history.txt
Created attachment 681901 [details] environment
Created attachment 681904 [details] etc.portage.tbz2
Created attachment 681907 [details] media-gfx:engauge-10.6:20210108-111543.log
Created attachment 801514 [details, diff] Patch to exclude the errornous functions
Created attachment 801517 [details] updated ebuild file
Alternatively, instead of removing the call to qcollectiongenerator like in my patch, one could also modify qthelp package to expose the executable by placing a link from /usr/lib64/qt5/bin/qcollectiongenerator to /usr/bin/qcollectiongenerator
(In reply to ilovekiruna from comment #8) > Alternatively, instead of removing the call to qcollectiongenerator like in > my patch, one could also modify qthelp package to expose the executable by > placing a link from /usr/lib64/qt5/bin/qcollectiongenerator to > /usr/bin/qcollectiongenerator or add the dependency to qtchooser which exposes the executable in /usr/bin/
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3d7418c0a4913d81e601b1fb50cd32e072ea4453 commit 3d7418c0a4913d81e601b1fb50cd32e072ea4453 Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2022-10-16 14:26:47 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2022-10-16 14:28:31 +0000 media-gfx/engauge: Fix src_install by generating engauge.qch in ebuild Closes: https://bugs.gentoo.org/655372 Closes: https://bugs.gentoo.org/764452 Closes: https://bugs.gentoo.org/847244 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> media-gfx/engauge/engauge-12.1.ebuild | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
