emerge world: How to continue on errors.

Message

mshmsh · Post by **mshmsh** » Sat Jul 22, 2006 1:32 pm

I am trying to do emerge -uDNp world.
Some package is failing. (libmpeg3)
But since this is world, i'd like the emerge to continue building other packages that are not dependent on this.
How do I this?

Thanks,
Shyam

Post by **NeddySeagoon** » Sat Jul 22, 2006 1:42 pm

mshmsh,

Code: Select all

emerge --resume --skipfirst

will contine the emerge, skipping the broken packages.
It will attempt to emerge all of the remaining packages and may fail again if something needs the package that was skipped.

mshmsh · Post by **mshmsh** » Sat Jul 22, 2006 1:48 pm

Thanks, Let me try this...

Shyam

devsk · Post by **devsk** » Mon Aug 14, 2006 6:24 am

NeddySeagoon wrote:mshmsh,
Code: Select all
emerge --resume --skipfirst
will contine the emerge, skipping the broken packages.
It will attempt to emerge all of the remaining packages and may fail again if something needs the package that was skipped.

Does this work with 'emerge -e world' as well i.e. can I do 'emerge -e --resume --skipfirst world'?

Post by **NeddySeagoon** » Mon Aug 14, 2006 10:06 am

devsk,

It works but not in the way you describe.

Code: Select all

emerge -e world

creates the package list to be processed and starts building packages. When it breaks,

Code: Select all

emerge --resume

causes emerge to continue by repeating the package that failed, using the package list calculated above. This is useful if you had a download problem thats been fixed, or turned the machine off, so you could sleep. Nothing is skipped.

Code: Select all

emerge --resume --skipfirst

discards the package that failed and contines with the next one in the list.
You can do this as many times as you need to, providing you do not run an emerge that calculates a new package list.

Enverex · Post by **Enverex** » Mon Aug 14, 2006 12:04 pm

Yeah, Portage really needs this feature. If I'm leaving something going overnight I normally end up doing this...

emerge --sync; emerge -NDu world; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst; emerge --resume --skipfirst

PLEASE will someone add a "continue on fail" option to Portage? Just because Cedega or Skype fails there is no reason why the rest of the system shouldn't get updated still.

po0f · Post by **po0f** » Mon Aug 14, 2006 12:55 pm

It's not a good idea to do that. If a package fails, you'll likely want to know the error. If it's an important enough package, say glibc, you want to resolve the error before continuing. Blindly resuming an emerge may break your system.

Enverex · Post by **Enverex** » Mon Aug 14, 2006 12:59 pm

po0f wrote:It's not a good idea to do that. If a package fails, you'll likely want to know the error. If it's an important enough package, say glibc, you want to resolve the error before continuing. Blindly resuming an emerge may break your system.

I'll find out what failed when I wake up (by doing 'emerge -NDup world' and looking at the output). If there was something like an upgrade of GCC from 3.4 to 4.1 then sure I likely wouldn't do it but for normal purposes it's fine. It's normally high level packages that fail, not toolchain programs.

po0f · Post by **po0f** » Mon Aug 14, 2006 1:13 pm

This is how I upgrade my box: I'll sync the tree, and emerge -uDNpv system. If I like what I see, I'll emerge -uDN system and fix whatever errors crop up. After that's done, I'll emerge -uDNpv world and look at the package list. Then, I'll go through and upgrade world a chunk at a time.

It might be a more verbose way of upgrading a system, but then I like to know exactly what's going on with my system.

devsk · Post by **devsk** » Mon Aug 14, 2006 8:39 pm

NeddySeagoon wrote:devsk,

It works but not in the way you describe.

yeah, I figured that works. Now I do this typically:

Code: Select all

\rm /tmp/emerge-progress.log
emerge -e world || until emerge --resume --skipfirst; do echo "Skipping a package" >> /tmp/emerge-progress.log; echo "" >> /tmp/emerge-progress.log;  tail -5 /var/log/emerge.log >> /tmp/emerge-progress.log; done

this avoids the need to babysit it and also points out if there are corrections and reruns of 'emerge -e world' required by just looking at the file /tmp/emerge-progress.log.