Re: [gentoo-user] portage has 0 debugging support for binary emerges

[n952162]

On 4/4/21 10:56 AM, Neil Bothwick wrote:
> On Sun, 4 Apr 2021 10:33:15 +0200, n952162 wrote:
>
>> [ebuild   R    ]    dev-libs/libuv-1.40.0:0/1::gentoo USE="-static-libs"
>> 0 KiB
>>
>> I'm not sure where the static-libs USE flag comes from, it's not in
>> /etc/portage/package.use.
> The flag is defined in the ebuild and defaults to off.
>
>> I don't follow the "0 KiB"
> It's the size of the files portage needs to download to install this. As
> you have already installed it, the source files are in your $DISTDIR so
> there's nothing to download.
>
>

Thank you.

After re-running quickpkg, I still get no "binary"s in the emerge output
dependency tree.

I now have this:

02/var/cache/distfiles>ll *rust*
-rw-r--r-- 1 root root     50278 Apr  3 14:30 eselect-rust-20200419.tar.bz2
-rw-r--r-- 1 root root 117764080 Apr  3 14:30
rust-1.45.1-x86_64-unknown-linux-gnu.tar.xz
-rw-r--r-- 1 root root 127200200 Apr  3 14:29
rust-1.46.0-x86_64-unknown-linux-gnu.tar.xz
-rw-r--r-- 1 root root 101868452 Apr  3 14:30 rustc-1.46.0-src.tar.xz
-rw-r--r-- 1 root root 104143736 Apr  3 14:29 rustc-1.47.0-src.tar.xz

02/var/cache/distfiles>cd ../binpkgs


22/var/cache/binpkgs>ll */*rust*
-rw-r----- 1 root root    15249 Apr  4 11:36
app-eselect/eselect-rust-20200419.tbz2
-rw-r----- 1 root root 95134383 Apr  4 11:29 dev-lang/rust-1.47.0-r2.tbz2
-rw-r----- 1 root root    17542 Apr  4 11:46 virtual/rust-1.47.0.tbz2

and:

[ebuild     U  ] virtual/rust-1.47.0::gentoo [1.46.0::gentoo] 0 KiB
[ebuild     U  ]    dev-lang/rust-1.47.0-r2:stable/1.47::gentoo
[1.46.0:stable/1.46::gentoo] USE="-clippy -debug (-doc) (-libressl)
(-miri) (-nightly) (-parallel-compiler) -rls -rustfmt
(-system-bootstrap) (-system-llvm) -test% -wasm" CPU_FLAGS_X86="sse2"
LLVM_TARGETS="(X86) -AArch64 -AMDGPU -ARM -AVR% -BPF -Hexagon -Lanai
-MSP430 -Mips -NVPTX -PowerPC -RISCV -Sparc -SystemZ -WebAssembly
-XCore" 0 KiB

No USE flags associated with "rust" on server or client.

I would expect that it would have "binary" instead of "ebuild" if it
were to come from the server.

I reran the emaint commands.

Here's the command:

+ emerge -p --getbinpkg y -v --tree --deep --update --noreplace
--changed-use --newuse --changed-deps --verbose-conflicts --keep-going
--with-bdeps=y --backtrack=100 @world

Relevant lines from /etc/portage/make.conf:

PORTAGE_BINHOST="http:///xxx//packages"
FEATURES="getbinpkg"

(I guess the FEATURES definition is redundant).

Yesterday, I successfully binary-updated a vm from a different server,
and another vm on that same (other) server is updating now, successfully
pulling in binary packages.