Bug 808165

Summary:	sys-process/below-0.6.3 - error: failed to run custom build command for below v0.3.0 (/var/tmp/portage/sys-process/below-0.3.0/wor
Product:	Gentoo Linux	Reporter:	Toralf Förster <toralf>
Component:	Current packages	Assignee:	Daniel Hodges <hodges.daniel.scott>
Status:	CONFIRMED ---
Severity:	normal	CC:	flow, proxy-maint
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=890638 https://bugs.gentoo.org/show_bug.cgi?id=908995
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge-info.txt emerge-history.txt environment etc.portage.tar.bz2 sys-process:below-0.3.0:20210813-215001.log temp.tar.bz2

Description Toralf Förster gentoo-dev

2021-08-14 07:22:34 UTC

     Running `/var/tmp/portage/sys-process/below-0.3.0/work/below-0.3.0/target/release/build/below-fa440833ec5ffec8/build-script-build`
error: failed to run custom build command for `below v0.3.0 (/var/tmp/portage/sys-process/below-0.3.0/work/below-0.3.0/below)`

Caused by:
  process didn't exit successfully: `/var/tmp/portage/sys-process/below-0.3.0/work/below-0.3.0/target/release/build/below-fa440833ec5ffec8/build-script-build` (exit status: 101)
  --- stderr

  -------------------------------------------------------------------

  This is an unstable amd64 chroot image at a tinderbox (==build bot)
  name: 17.1_hardened-j3-20210812-230008

  -------------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-11.2.0 *
clang version 12.0.1
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm/12/bin
/usr/lib/llvm/12
12.0.1
Python 3.9.6
Available Ruby profiles:
  [1]   ruby26 (with Rubygems)
  [2]   ruby30 (with Rubygems) *
Available Rust versions:
  [1]   rust-bin-1.54.0
  [2]   rust-1.54.0 *
The Glorious Glasgow Haskell Compilation System, version 8.10.4

  HEAD of ::gentoo
commit 7f547865db08197a8c240868d0dd04736b1f5f56
Author: Repository mirror & CI <repomirrorci@gentoo.org>
Date:   Fri Aug 13 21:08:29 2021 +0000

    2021-08-13 21:08:28 UTC

emerge -qpvO sys-process/below
[ebuild  N    ] sys-process/below-0.3.0  USE="-debug"

Comment 1 Toralf Förster gentoo-dev

2021-08-14 07:22:35 UTC

Created attachment 732829 [details]
emerge-info.txt

Comment 2 Toralf Förster gentoo-dev

2021-08-14 07:22:37 UTC

Created attachment 732832 [details]
emerge-history.txt

Comment 3 Toralf Förster gentoo-dev

2021-08-14 07:22:38 UTC

Created attachment 732835 [details]
environment

Comment 4 Toralf Förster gentoo-dev

2021-08-14 07:22:39 UTC

Created attachment 732838 [details]
etc.portage.tar.bz2

Comment 5 Toralf Förster gentoo-dev

2021-08-14 07:22:41 UTC

Created attachment 732841 [details]
sys-process:below-0.3.0:20210813-215001.log

Comment 6 Toralf Förster gentoo-dev

2021-08-14 07:22:43 UTC

Created attachment 732844 [details]
temp.tar.bz2

Comment 7 Agostino Sarubbo gentoo-dev

2023-01-26 07:35:57 UTC

usr-merge_tinderbox has reproduced this issue with version 0.6.3 - Updating summary.

Comment 8 Georgy Yakovlev archtester

2023-01-26 20:35:10 UTC

I see both rust and rust-bin in the history. could have happened that -bin was with rustfmt and thus satisfying the dep,  and other one got installed without it.
in toralf's portage conf I see
dev-lang/rust-bin                        clippy rls rustfmt

but I don't see one for rust (non bin)
and in the log file I see he installs rust-bin first
and then installs rust (and eselect will select it)

so this issue is caused by mismatched flags on rust and rust-bin, one of those satisfies virtual/rust[rustfmt] but other one without rustfmt is actually eselected at build time.


idk how ago's tinderbox reproduced this, it had to hit exact same situation.

more likely it hit this:
https://github.com/libbpf/libbpf-rs/issues/337

but we'll never know, as there are no logs or configuration attached, and bug matching algo is unknown.