From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] portage has 0 debugging support for binary emerges
Date: Sat, 3 Apr 2021 23:31:55 +0100 [thread overview]
Message-ID: <20210403233155.0f8b2498@digimed.co.uk> (raw)
In-Reply-To: <35d70a24-3471-cab3-8681-7229cbbc28d9@web.de>
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
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"?
--
Neil Bothwick
An infinite number of monkeys pounding away on keyboards will
eventually produce a report showing that Windows is more secure,
and has a lower TCO, than linux.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-03 22:32 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 [this message]
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
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=20210403233155.0f8b2498@digimed.co.uk \
--to=neil@digimed.co.uk \
--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