Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.gentoo.user > #116225 > unrolled thread

[gentoo-user] Emerge --resume --skipfirst

Back to article view | Back to linux.gentoo.user

Contents

  [gentoo-user] Emerge --resume --skipfirst Peter Humphrey <peter@prh.myzen.co.uk> - 2026-04-27 18:40 +0200
    Re: [gentoo-user] Emerge --resume --skipfirst Bryan Gardiner <bog@khumba.net> - 2026-04-27 19:40 +0200
    Re: [gentoo-user] Emerge --resume --skipfirst Philipp Ludwig <gentoo@philippludwig.net> - 2026-04-27 21:30 +0200
      Re: [gentoo-user] Emerge --resume --skipfirst Dale <rdalek1967@gmail.com> - 2026-04-27 22:50 +0200
        Re: [gentoo-user] Emerge --resume --skipfirst Peter Humphrey <peter@prh.myzen.co.uk> - 2026-04-28 10:30 +0200
          Re: [gentoo-user] Emerge --resume --skipfirst Peter Humphrey <peter@prh.myzen.co.uk> - 2026-04-28 12:00 +0200
            Re: [gentoo-user] Emerge --resume --skipfirst Philipp Ludwig <gentoo@philippludwig.net> - 2026-04-28 14:20 +0200
              Re: [gentoo-user] Emerge --resume --skipfirst Peter Humphrey <peter@prh.myzen.co.uk> - 2026-04-28 16:20 +0200
                Re: [gentoo-user] Emerge --resume --skipfirst Dale <rdalek1967@gmail.com> - 2026-04-28 17:00 +0200
                  Re: [gentoo-user] Emerge --resume --skipfirst Peter Humphrey <peter@prh.myzen.co.uk> - 2026-04-28 22:50 +0200
                    Re: [gentoo-user] Emerge --resume --skipfirst Dale <rdalek1967@gmail.com> - 2026-04-28 23:40 +0200
                      Re: [gentoo-user] Emerge --resume --skipfirst Alexis <flexibeast@gmail.com> - 2026-04-29 02:30 +0200
                        Re: [gentoo-user] Emerge --resume --skipfirst Dale <rdalek1967@gmail.com> - 2026-04-29 02:50 +0200
                          Re: [gentoo-user] Emerge --resume --skipfirst Michael <confabulate@kintzios.com> - 2026-04-29 11:30 +0200
                      Re: [gentoo-user] Emerge --resume --skipfirst Peter Humphrey <peter@prh.myzen.co.uk> - 2026-04-29 11:40 +0200

#116225 — [gentoo-user] Emerge --resume --skipfirst

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.

-- 
Regards,
Peter.

[toc] | [next] | [standalone]

#116226

Hi Peter,

On Mon, 27 Apr 2026 17:37:26 +0100
Peter Humphrey <peter@prh.myzen.co.uk> 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

[toc] | [prev] | [next] | [standalone]

#116227

If you are in the mood for a hack, add --keep-going to the
EMERGE_DEFAULT_OPTS.
Then, in a case like "i actually don't want to compile this
huge package", you can just kill the respective compilation
process; emerge registers this a a failed compilation
and keeps going with the remaining packages.

Note: This is not recommended by any dev, so try at your own risk.

On 4/27/26 18:37, Peter Humphrey 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.
> 

[toc] | [prev] | [next] | [standalone]

#116228

On 4/27/26 2:18 PM, Philipp Ludwig wrote:
> If you are in the mood for a hack, add --keep-going to the
> EMERGE_DEFAULT_OPTS.
> Then, in a case like "i actually don't want to compile this
> huge package", you can just kill the respective compilation
> process; emerge registers this a a failed compilation
> and keeps going with the remaining packages.
>
> Note: This is not recommended by any dev, so try at your own risk.
>

I actually added this to my options in make.conf long ago and it works 
very well.  If I start a emerge and a package fails and I'm napping or 
not watching it, it just continues on and lets me know at the end what 
failed.

In the situation that the OP is in, just doing a CTRL C and then 
restarting the emerge should skip that first package just fine.  So as a 
user who has used this setting for a long time, it does work well.

Dale

:-)  :-)

[toc] | [prev] | [next] | [standalone]

#116229

On Monday, 27 April 2026 21:39:54 British Summer Time Dale wrote:
> On 4/27/26 2:18 PM, Philipp Ludwig wrote:
> > If you are in the mood for a hack, add --keep-going to the
> > EMERGE_DEFAULT_OPTS.
> > Then, in a case like "i actually don't want to compile this
> > huge package", you can just kill the respective compilation
> > process; emerge registers this a a failed compilation
> > and keeps going with the remaining packages.
> > 
> > Note: This is not recommended by any dev, so try at your own risk.
> 
> I actually added this to my options in make.conf long ago and it works
> very well.  If I start a emerge and a package fails and I'm napping or
> not watching it, it just continues on and lets me know at the end what
> failed.
> 
> In the situation that the OP is in, just doing a CTRL C and then
> restarting the emerge should skip that first package just fine.  So as a
> user who has used this setting for a long time, it does work well.

The option is in my make.conf, but I hadn't thought of that way of resuming an 
emerge.

You learn something new every day, it seems.

-- 
Regards,
Peter.

[toc] | [prev] | [next] | [standalone]

#116230

On Tuesday, 28 April 2026 09:27:05 British Summer Time Peter Humphrey wrote:
> On Monday, 27 April 2026 21:39:54 British Summer Time Dale wrote:

> > In the situation that the OP is in, just doing a CTRL C and then
> > restarting the emerge should skip that first package just fine.  So as a
> > user who has used this setting for a long time, it does work well.
> 
> The option is in my make.conf, but I hadn't thought of that way of resuming
> an emerge.

Er...Now that I've woken up a bit, what exactly is that way? What command 
should I give to emerge? Remember that it's an 'emerge -e @world' that was 
interrupted.

-- 
Regards,
Peter.

[toc] | [prev] | [next] | [standalone]

#116231

The idea was that with --keep-going you would not abort an emerge
(as outlined in your original mail) but just abort the specific package
compilation process (in this case, google-chrome).
emerge would then just skip this particular package.

Am 2026-04-28 11:51, schrieb Peter Humphrey:
> On Tuesday, 28 April 2026 09:27:05 British Summer Time Peter Humphrey 
> wrote:
>> On Monday, 27 April 2026 21:39:54 British Summer Time Dale wrote:
> 
>> > In the situation that the OP is in, just doing a CTRL C and then
>> > restarting the emerge should skip that first package just fine.  So as a
>> > user who has used this setting for a long time, it does work well.
>> 
>> The option is in my make.conf, but I hadn't thought of that way of 
>> resuming
>> an emerge.
> 
> Er...Now that I've woken up a bit, what exactly is that way? What 
> command
> should I give to emerge? Remember that it's an 'emerge -e @world' that 
> was
> interrupted.

[toc] | [prev] | [next] | [standalone]

#116232

On Tuesday, 28 April 2026 13:10:31 British Summer Time Philipp Ludwig wrote:
> The idea was that with --keep-going you would not abort an emerge
> (as outlined in your original mail) but just abort the specific package
> compilation process (in this case, google-chrome).
> emerge would then just skip this particular package.

Yes, I see that. My question was: once the -e @world had been interrupted, 
what command should I give it to resume. I know about --resume --skipfirst, 
which is how I started this thread.

-- 
Regards,
Peter.

[toc] | [prev] | [next] | [standalone]

#116233

On 4/28/26 9:12 AM, Peter Humphrey wrote:
> On Tuesday, 28 April 2026 13:10:31 British Summer Time Philipp Ludwig wrote:
>> The idea was that with --keep-going you would not abort an emerge
>> (as outlined in your original mail) but just abort the specific package
>> compilation process (in this case, google-chrome).
>> emerge would then just skip this particular package.
> Yes, I see that. My question was: once the -e @world had been interrupted,
> what command should I give it to resume. I know about --resume --skipfirst,
> which is how I started this thread.
>


Just do a emerge --resume and that's it.  It will apply the --skipfirst 
from make.conf.

Now that I think about this, I think it is --keep-going that I have in 
make.conf.  Be right back.  Yep.  I got the two confused for some 
reason.  I don't have --skipfirst in make.conf but do have 
--keep-going.  So, if you stop emerge and want to skip Chrome, just 
emerge --resume --skipfirst and it should skip Chrome.  Just make sure 
that only Chrome is actively compiling.  Sometimes two packages will be 
working at the same time.  If you have two or more compiling at the same 
time, I'm not sure how emerge will handle that.  I don't think I've ever 
ran into that before.  :/

It seems emerge has so many options, it's hard to keep them all 
straight.  ;-)

Dale

:-)  :-)

[toc] | [prev] | [next] | [standalone]

#116235

On Tuesday, 28 April 2026 15:58:08 British Summer Time Dale wrote:

> Now that I think about this, I think it is --keep-going that I have in
> make.conf.  Be right back.  Yep.  I got the two confused for some
> reason.  I don't have --skipfirst in make.conf but do have
> --keep-going.  So, if you stop emerge and want to skip Chrome, just
> emerge --resume --skipfirst and it should skip Chrome.  Just make sure
> that only Chrome is actively compiling.  Sometimes two packages will be
> working at the same time.  If you have two or more compiling at the same
> time, I'm not sure how emerge will handle that.  I don't think I've ever
> ran into that before.  :/

You may remember that I started this thread with an observation that --resume 
--skipfirst has been superseded, but that's what I needed to do.

Full circle...

-- 
Regards,
Peter.

[toc] | [prev] | [next] | [standalone]

#116236

On 4/28/26 3:47 PM, Peter Humphrey wrote:
> On Tuesday, 28 April 2026 15:58:08 British Summer Time Dale wrote:
>
>> Now that I think about this, I think it is --keep-going that I have in
>> make.conf.  Be right back.  Yep.  I got the two confused for some
>> reason.  I don't have --skipfirst in make.conf but do have
>> --keep-going.  So, if you stop emerge and want to skip Chrome, just
>> emerge --resume --skipfirst and it should skip Chrome.  Just make sure
>> that only Chrome is actively compiling.  Sometimes two packages will be
>> working at the same time.  If you have two or more compiling at the same
>> time, I'm not sure how emerge will handle that.  I don't think I've ever
>> ran into that before.  :/
> You may remember that I started this thread with an observation that --resume
> --skipfirst has been superseded, but that's what I needed to do.
>
> Full circle...
>


I'm not aware of anything changing.  Are there any docs for these 
changes?  I wish they would post on this list when things changes.

I miss the newsletter they used to do a long time ago.  It was good for 
announcing things like this.

Dale

:-)  :-)

[toc] | [prev] | [next] | [standalone]

#116237

Dale <rdalek1967@gmail.com> writes:

>> You may remember that I started this thread with an observation 
>> that --resume
>> --skipfirst has been superseded, but that's what I needed to 
>> do.
>>
>> Full circle...
>>
>
> I'm not aware of anything changing.  Are there any docs for 
> these
> changes?  I wish they would post on this list when things 
> changes.

Yes, i'd be interested in a link to the referenced dev's comments; 
i'm not aware of any such change(s) myself, and it's the sort of 
thing that would probably come up on the Web forums (which is the 
primary place people seek support[a]). There's nothing in the 
emerge(1) man page entries for `--resume` and `--skipfirst` to 
indicate that they've been superseded by some other approach, or 
just generally deprecated.


Alexis.

[a] i much prefer mailing lists over Web forums myself, for 
various reasons, but my experience is that nowadays, the majority 
of users have the reverse preference, and strongly so.

[toc] | [prev] | [next] | [standalone]

#116238

On 4/28/26 7:20 PM, Alexis wrote:
> Dale <rdalek1967@gmail.com> writes:
>
>>> You may remember that I started this thread with an observation
>>> that --resume
>>> --skipfirst has been superseded, but that's what I needed to
>>> do.
>>>
>>> Full circle...
>>>
>> I'm not aware of anything changing.  Are there any docs for
>> these
>> changes?  I wish they would post on this list when things
>> changes.
> Yes, i'd be interested in a link to the referenced dev's comments;
> i'm not aware of any such change(s) myself, and it's the sort of
> thing that would probably come up on the Web forums (which is the
> primary place people seek support[a]). There's nothing in the
> emerge(1) man page entries for `--resume` and `--skipfirst` to
> indicate that they've been superseded by some other approach, or
> just generally deprecated.
>
>
> Alexis.
>
> [a] i much prefer mailing lists over Web forums myself, for
> various reasons, but my experience is that nowadays, the majority
> of users have the reverse preference, and strongly so.
>


Well, I think a dev posted something here on this list a while back 
about something that might be added to Gentoo.  I like it when they post 
something about changes because unless you read the docs every time 
there is a upgrade and remember enough to notice any changes, how else 
you going to know something changed?  I'll admit, I subscribe to the dev 
mailing list because that does give me a heads up to some changes.  I 
don't think changes to emerge is ever posted there.  I do on occasion 
see a discussion about adding a feature to emerge but rarely see 
anything about whether it was added or not.

Even if it was just a post to this list that was a short description and 
a link to a wiki, forum thread or the details itself, that would be a 
big help.  I guess that no one wants to volunteer to do the job that is 
in the know about the changes tho.

Dale

:-)  :-)

[toc] | [prev] | [next] | [standalone]

#116239

[Multipart message — attachments visible in raw view] — view raw

On Wednesday, 29 April 2026 01:39:38 British Summer Time Dale wrote:
> On 4/28/26 7:20 PM, Alexis wrote:
> > Dale <rdalek1967@gmail.com> writes:
> >>> You may remember that I started this thread with an observation
> >>> that --resume
> >>> --skipfirst has been superseded, but that's what I needed to
> >>> do.
> >>> 
> >>> Full circle...
> >> 
> >> I'm not aware of anything changing.  Are there any docs for
> >> these
> >> changes?  I wish they would post on this list when things
> >> changes.
> > 
> > Yes, i'd be interested in a link to the referenced dev's comments;
> > i'm not aware of any such change(s) myself, and it's the sort of
> > thing that would probably come up on the Web forums (which is the
> > primary place people seek support[a]). There's nothing in the
> > emerge(1) man page entries for `--resume` and `--skipfirst` to
> > indicate that they've been superseded by some other approach, or
> > just generally deprecated.
> > 
> > 
> > Alexis.
> > 
> > [a] i much prefer mailing lists over Web forums myself, for
> > various reasons, but my experience is that nowadays, the majority
> > of users have the reverse preference, and strongly so.
> 
> Well, I think a dev posted something here on this list a while back
> about something that might be added to Gentoo.  I like it when they
> post something about changes because unless you read the docs every
> time there is a upgrade and remember enough to notice any changes,
> how else you going to know something changed?  I'll admit, I
> subscribe to the dev mailing list because that does give me a heads
> up to some changes.  I don't think changes to emerge is ever posted
> there.  I do on occasion see a discussion about adding a feature to
> emerge but rarely see anything about whether it was added or not.
> 
> Even if it was just a post to this list that was a short description
> and a link to a wiki, forum thread or the details itself, that would
> be a big help.  I guess that no one wants to volunteer to do the job
> that is in the know about the changes tho.
> 
> Dale
> 
> :-)  :-)

I don't know if anything has changed in emerge's options.

Peter wrote above:

"... I started this thread with an observation that --resume --skipfirst 
has been superseded"  

What I understand Peter was referring to as being superseded is NOT any 
emerge options, but his original list of packages being processed by 
emerge.  This took place when he restarted 'emerge -e' afresh, after 
cancelling Chromium's mammoth compilation.  This action created a new 
list of packages by emerge, including packages Peter had just emerged.

The manual states this quite useful feature about the '--resume' option, 
which however would not resolve Peter's problem:

"A resume list will persist until it has been completed in entirety or 
until another aborted merge list replaces it.  The resume history is 
capable of storing two merge lists.  After one resume list completes, it 
is possible to invoke --resume once again in order to resume an older 
list."

Since in this case both 'emerge -e' lists are identical this clever 
feature won't help.

I think a better solution, other than manually excluding packages 
already emerged (plus Chromium), would be to apply something similar to 
Bryan's suggestion posted earlier.  Use some incantation of eix to 
filter packages before the Chromium emerge took place AND after the 
second 'emerge -e' was run, then exclude this generated list from a new 
emerge -e @world.

[toc] | [prev] | [next] | [standalone]

#116240

On Tuesday, 28 April 2026 22:30:03 British Summer Time Dale wrote:

> I'm not aware of anything changing.  Are there any docs for these
> changes?  I wish they would post on this list when things changes.

I don't think any particular change was meant; just the general development of 
portage.

-- 
Regards,
Peter.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.gentoo.user

csiph-web