Re: Emerge --resume --skipfirst

Hi Peter,

On Mon, 27 Apr 2026 17:37:26 +0100
Peter Humphrey <[email protected]> wrote:

> Greetings,
> 
> I remember a dev remarking not long ago that this, the subject, had
> been superseded. Well, I had cause to use it today.
> 
> After wrestling with a maze of USE conflicts after the latest sync, I
> decided to cut the Gordian knot with an 'emerge -e @world'.
> 
> All was going smoothly until I noticed it was compiling Chromium;
> that's when I remembered installing that to test a website. It took
> 13 hours. So I aborted the emerge. What I should have done next is to
> 'emerge --resume --skipfirst' and uninstall chromium later. I hadn't
> the presence of mind, though, so I uninstalled chromium straight away
> and had to restart the -e @world from the beginning.
> 
> Ho hum.

If your installed packages are clean (recently depcleaned, no packages
that are installed but not available), then you can resume a "-e"
rebuild like this:

Check /var/log/emerge.log to find the UNIX timestamp the first package
in your initial rebuild started at, the number at the start of the
line.  Then plug that into this command:

    emerge -av1 $(eix-installed-after -b -e <TIMESTAMP>)

Plus you can filter packages out of eix-installed-after's output as
needed, if there are builds you want to defer, or unavailable ebuilds,
etc.

Cheers,
Bryan