public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tastytea <tastytea+gentoo@tastytea.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] For what is emerge waiting for...?
Date: Sun, 5 Apr 2020 23:03:50 +0200	[thread overview]
Message-ID: <20200405230350.5e38b117@ventiloplattform.tastytea.de> (raw)
In-Reply-To: <653170283.20200405221357@xss.de>

[-- Attachment #1: Type: text/plain, Size: 873 bytes --]

On Sun, 5 Apr 2020 22:13:57 +0200 
Stefan Schmiedl <s@xss.de> wrote:

> "tuxic@posteo.de" <tuxic@posteo.de>, 05.04.2020, 21:58:
> 
> > if emerge encounters a have-to-use-one-core-onlu ebiuld and that one
> > is not constantlu writing to the disk I would expect one core busy
> > at least.  
> 
> > But no...nothing...as I said: All cores on holidays...:)  
> 
> I ran into this a few times when some host was unresponsive,
> so a package could not be downloaded, hence emerge did not
> have anything to build.
> 
> Check with htop's tree view or "ps faux" if emerge
> has a wget child process.
> 
> s.

The fetch process writes a log to /var/log/emerge-fetch.log. If
fetching a package is the problem, you should see it there.

tastytea

-- 
Get my PGP key with `gpg --locate-keys tastytea@tastytea.de` or at
<https://tastytea.de/tastytea.asc>.

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2020-04-05 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05 19:10 [gentoo-user] For what is emerge waiting for...? tuxic
2020-04-05 19:38 ` Neil Bothwick
2020-04-05 19:54   ` tuxic
2020-04-05 19:41 ` Dale
2020-04-05 19:58   ` tuxic
2020-04-05 20:13     ` Stefan Schmiedl
2020-04-05 21:03       ` tastytea [this message]
2020-04-05 21:45 ` [gentoo-user] " Nikos Chantziaras

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=20200405230350.5e38b117@ventiloplattform.tastytea.de \
    --to=tastytea+gentoo@tastytea.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