On 06/22/2016 09:39 AM, Dan Douglas wrote: > On Tue, Jun 21, 2016 at 10:04 AM, Neil Bothwick <n...@digimed.co.uk> wrote: >> On Tue, 21 Jun 2016 09:39:42 -0500, Dan Douglas wrote: >> >>> Is something misconfigured on my end or is this just a long-standing >>> bug? I at least need a way to either recover the list of packages >>> manually or force portage to continue on because any failure prevents >>> updating a system. >> >> Have you tried the --keep-going option? It causes emerge to automatically >> continue with what it can after a failed build. > > --keep-going is in EMERGE_DEFAULT_OPTS so the problem is only when > that fails for whatever reason, --resume (with or without > --skip-first) always fails too. Usually a package that I already know > is broken and am working on but is already installed wants to be > rebuilt will trigger this. The problem is portage doesn't seem to care > whether any packages in the current resume list actually depend on the > failing package and this can prevent important installations from > finishing. >
I've had the exact same thing happen a couple of times recently and got around it by running the original command but adding the failed package to the --exclude list. AFAIU (I maybe wrong) the result of both commands should be the same so it sounds like a bug to me.
