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

[n952162]

On 4/4/21 12:31 AM, Neil Bothwick wrote:
> On Sat, 3 Apr 2021 22:03:46 +0200, n952162 wrote:
>
>> I find no clue why the binary packages on my server aren't being picked
>> up.  The --debug option  (and --verbose, naturally) has no additional
>> information.  Running the --getbinpkgonly stops immediately, saying 0
>> packages are selected.
>>
>> I found one problem: on my server, my apache log file had a 302 fetch
>> error for /var/cache/binpkgs/Packages.  I touched it a few hours into
>> the future and started getting a 200 for it.  But still no emerge would
>> fetch a binary (even though there ARE good candidates).  On a guess, I
>> touched all the files in binpkgs an hour into the future, but that
>> didn't help.
> Have you tried "emaint --check binhost" followed by "emaint --fix
> binhost"?
>

Thank you, that was exactly the kind of tip I was hoping for.
Unfortunately, in this case, it didn't help:


$ sudo emaint --check binhost
Password:
Emaint: check binhost           [
<=>                                         ]

$sudo emaint --fix binhost
Emaint: fix binhost        100%
[============================================>]


It is likely a dependency issue, but one package that I checked had:

  * neither server or client USE flags
  * the CPU_FLAGS match
  * the required package exists on the server

E.g.:

[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.

I don't follow the "0 KiB"

Okay, here's the status of the server, I'm a little confused by it now
... like what is rustc?  And why do I have different versions in binpkgs
and distfiles?

[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]

$ cd /var/cache

$ ls -l  */rust*
-rw-r--r-- 1 root root 117764080 Apr  3 14:30
distfiles/rust-1.45.1-x86_64-unknown-linux-gnu.tar.xz
-rw-r--r-- 1 root root 127200200 Apr  3 14:29
distfiles/rust-1.46.0-x86_64-unknown-linux-gnu.tar.xz
-rw-r--r-- 1 root root 101868452 Apr  3 14:30
distfiles/rustc-1.46.0-src.tar.xz
-rw-r--r-- 1 root root 104143736 Apr  3 14:29
distfiles/rustc-1.47.0-src.tar.xz

$ ls -l binpkgs/*/rust*
-rw-r----- 1 root root 95131159 Apr  3 22:30
binpkgs/dev-lang/rust-1.47.0-r2.tbz2
-rw-r----- 1 root root    17542 Apr  3 22:30
binpkgs/virtual/rust-1.47.0.tbz2

$ cd /var/db

$ ls -ld pkg/dev-lang/rust-1.47.0-r2/
drwxr-xr-x 2 root root 4096 Feb  2 14:07 pkg/dev-lang/rust-1.47.0-r2/

# (I can't imagine that I ever intentionally emerged rust-bin)

$ ls -ld repos/gentoo/dev-lang/rust
rust/     rust-bin/

$ ls -l repos/gentoo/dev-lang/rust/
total 140
-rw-r--r-- 1 root root 29908 Feb 25 00:39 Manifest
drwxr-xr-x 2 root root  4096 Mar  1 17:00 files
-rw-r--r-- 1 root root  1083 Mar 31  2020 metadata.xml
-rw-r--r-- 1 root root 17326 Jan 31 01:43 rust-1.46.0.ebuild
-rw-r--r-- 1 root root 18735 Feb 25 00:39 rust-1.47.0-r2.ebuild
-rw-r--r-- 1 root root 18059 Jan 31 01:43 rust-1.48.0.ebuild
-rw-r--r-- 1 root root 18104 Feb  5 20:39 rust-1.49.0.ebuild
-rw-r--r-- 1 root root 18277 Feb 12 01:09 rust-1.50.0.ebuild

I'll run quickpkg again and report ...