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.
Binary updates are VERY useful for virtual machines.
On 4/3/21 10:03 PM, 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.
Binary updates are VERY useful for virtual machines.
Unfortunately, there hasn't really been a resolution on this issue.
I think it's reasonable that if portage accesses a package on a binary
server and decides it's not eligible, it should report the reason for rejecting it.
Is it possible to make requests for improvements in gentoo?
On 9/6/21 3:48 PM, n952162 wrote:
On 4/3/21 10:03 PM, 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.
Binary updates are VERY useful for virtual machines.
Unfortunately, there hasn't really been a resolution on this issue.
I think it's reasonable that if portage accesses a package on a binary
server and decides it's not eligible, it should report the reason for
rejecting it.
Is it possible to make requests for improvements in gentoo?
In the current case, llvm-common came across as binary, thunderbird
and firefox are also listed as a *binary* update, but llvm is an
*ebuild*. Neither host (binary server) nor the client (updating
system) have any USE flags defined for llvm. I know of no way to
figure out what went wrong.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 128:57:48 |
Calls: | 6,734 |
Files: | 12,256 |
Messages: | 5,362,543 |