public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: n952162 <n952162@web.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage has 0 debugging support for binary emerges
Date: Mon, 6 Sep 2021 15:48:18 +0200	[thread overview]
Message-ID: <56a7028f-4047-2d67-eb5a-2e9f14aac573@web.de> (raw)
In-Reply-To: <35d70a24-3471-cab3-8681-7229cbbc28d9@web.de>

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?





  parent reply	other threads:[~2021-09-06 13:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03 20:03 [gentoo-user] portage has 0 debugging support for binary emerges n952162
2021-04-03 22:31 ` Neil Bothwick
2021-04-04  8:33   ` n952162
2021-04-04  8:56     ` Neil Bothwick
2021-04-04 10:37       ` n952162
2021-04-04 13:41         ` n952162
2021-04-05 21:11           ` Daniel Frey
2021-09-06 13:48 ` n952162 [this message]
2021-09-06 16:26   ` n952162
2021-09-06 17:57     ` n952162

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56a7028f-4047-2d67-eb5a-2e9f14aac573@web.de \
    --to=n952162@web.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox