------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop-abi32+64-20200505-162645 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-10.1.0 * clang version 10.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/10/bin /usr/lib/llvm/10 10.0.0 Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python3.8 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * The following VMs are available for generation-2: *) IcedTea JDK 3.15.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm The Glorious Glasgow Haskell Compilation System, version 8.0.2 timestamp(s) of HEAD at this tinderbox image: /var/db/repos/gentoo Fri 08 May 2020 01:35:25 PM UTC emerge -qpvO dev-libs/boost [ebuild U ] dev-libs/boost-1.73.0 [1.72.0-r1] USE="bzip2 icu nls threads zlib -context -debug -doc -lzma -mpi -numpy -python -static-libs -tools -zstd" ABI_X86="32 (64) (-x32)" PYTHON_TARGETS="python2_7 python3_7 -python3_6 -python3_8"
Created attachment 636864 [details] emerge-info.txt
Created attachment 636866 [details] dev-libs:boost-1.73.0:20200508-150856.log.bz2
Created attachment 636868 [details] emerge-history.txt
Created attachment 636870 [details] etc.portage.tbz2
Created attachment 636872 [details] logs.tbz2
I dare say leatherman installing boost headers is leatherman bug.
what's the right place for boost plugins (or the right flag to depend on with boost)?
(In reply to Matthew Thode ( prometheanfire ) from comment #7) > what's the right place for boost plugins (or the right flag to depend on > with boost)? I don't know. But is it really a boost plugin? It looks to be a vendored part of boost, that's now present in boost itself. However, the boost version seems incompatible, or at least facter fails to build against it.
commit acbf60f136e19fd2ad42bf35e886d0f14a82cf84 Author: Matthew Thode <prometheanfire@gentoo.org> Date: Sat May 30 12:15:13 2020 -0500 dev-libs/leatherman: 1.12.0 stable amd64/x86 with cleanup Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Matthew Thode <prometheanfire@gentoo.org> *rubs eyes*
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1767004bbffe39fca63e3e1aeee361c4bdea4004 commit 1767004bbffe39fca63e3e1aeee361c4bdea4004 Author: Matthew Thode <prometheanfire@gentoo.org> AuthorDate: 2020-05-30 20:36:11 +0000 Commit: Matthew Thode <prometheanfire@gentoo.org> CommitDate: 2020-05-30 20:36:22 +0000 dev-libs/leatherman: remove installing vendored boost library Closes: https://bugs.gentoo.org/721652 Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Matthew Thode <prometheanfire@gentoo.org> .../{leatherman-1.12.0.ebuild => leatherman-1.12.0-r1.ebuild} | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3273bd78c5e306521b58b727aefb3216f8decab8 commit 3273bd78c5e306521b58b727aefb3216f8decab8 Author: Matthew Thode <prometheanfire@gentoo.org> AuthorDate: 2020-05-31 16:47:29 +0000 Commit: Matthew Thode <prometheanfire@gentoo.org> CommitDate: 2020-05-31 16:47:45 +0000 dev-libs/leatherman: fix build (avoid vendored boost nowide) Bug: https://bugs.gentoo.org/721652 Closes: https://bugs.gentoo.org/726406 Package-Manager: Portage-2.3.99, Repoman-2.3.22 Signed-off-by: Matthew Thode <prometheanfire@gentoo.org> dev-libs/leatherman/leatherman-1.12.0-r1.ebuild | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
This still triggers an error. I believe dev-libs/boost-1.73.0 needs !<dev-libs/leatherman-1.12.0-r1 to RDEPEND so portage will bypass the error.
build.log? Does that mean you could reproduce the file collision with leatherman versions 1.3.0 and 1.11.0?
(In reply to Andreas Sturmlechner from comment #13) > build.log? > > Does that mean you could reproduce the file collision with leatherman > versions 1.3.0 and 1.11.0? Yes this is what I mean. It is only fixed in 1.12.0-r1.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ae40d64c19a54f027470b7cee8698353e35b6969 commit ae40d64c19a54f027470b7cee8698353e35b6969 Author: Robin H. Johnson <robbat2@gentoo.org> AuthorDate: 2020-06-23 19:21:22 +0000 Commit: Robin H. Johnson <robbat2@gentoo.org> CommitDate: 2020-06-23 19:22:30 +0000 dev-libs/boost: block old leatherman due to collision Closes: https://bugs.gentoo.org/721652 Signed-off-by: Robin H. Johnson <robbat2@gentoo.org> dev-libs/boost/boost-1.73.0.ebuild | 1 + 1 file changed, 1 insertion(+)
