[gentoo-user] emerge --update : how to keep it going?

[Helmut Jarausch]

Hi,
this is nuissance all the time.

Updating a machine which hasn't been updated for a long(er) time I try

emerge -vup --changed-use --deep --tree --with-bdeps y @system
@world >/root/UPD

But many times this stops prematurely with messages like

emerge: there are no ebuilds to satisfy
">=app-text/poppler-bindings-0.5.0"

How can I keep emerge going and tell me these message all at once in
the end?

Many thanks for hint,
Helmut.

[Michael Mol]

--keep-going

:)

[Francisco Ares]

2012/11/30 Helmut Jarausch <jara...@igpm.rwth-aachen.de>

Check the option --keep-going , but you will not have all messages at the end, as far as I remember. If so, you can redirect the output to a file.

Francisco

--
"If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have one idea and we exchange these ideas, then each of us will have two ideas." - George Bernard Shaw

[Dale]

This should help. From man emerge:

--keep-going [ y | n ]
Continue as much as possible after an error. When an error occurs,
dependencies are recalculated for remaining packages and any with
unsatisfied dependencies are automatically dropped. Also see the
related --skipfirst option.

You can also add that to make.conf if you want that all the time. There
are times when emerge can't continue but if it can, it will.

Dale

:-) :-)

--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!

[Yohan Pereira]

On Friday 30 Nov 2012 13:26:07 Helmut Jarausch wrote:
>=app-text/poppler-bindings-0.5.0"
>
> How can I keep emerge going and tell me these message all at once in
> the end?

Maybe --keep-going ?
:)
--

- Yohan Pereira

The difference between a Miracle and a Fact is exactly the difference
between a mermaid and a seal.
-- Mark Twain

[2sb...@gmail.com]

Get
ANGRY
and
--keep-going
:)

> Many thanks for hint,
> Helmut.

yw

[Michael Orlitzky]

Now all we need is,

emerge --i-dont-care

for when you have 100 packages ready to be updated and one stupid ruby
package has conflicting dependencies.

[Keith Dart]

Re , Helmut Jarausch said:
> How can I keep emerge going and tell me these message all at once in
> the end?

The --keep-going option, plus this in your make.conf:

PORTAGE_ELOG_SYSTEM="echo save"

Then emerge the elogv program. Use that to view all the emerge logs at
the end.


-- Keith


--

-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Keith Dart <ke...@dartworks.biz>
public key: ID: 19017044
<http://www.dartworks.biz/>
=====================================================================

[Helmut Jarausch]

Many thanks to all who helped me.

I didn't think of --keep-going having an effect if --pretend is active.
Helmut.

[2sb...@gmail.com]

>
> Now all we need is,
>
> emerge --i-dont-care
>
> for when you have 100 packages ready to be updated and one stupid ruby
> package has conflicting dependencies.

I doubt if there is point to runaway from problms. In your case I'd say "keep
calm and --keep-going" :)

[Volker Armin Hemmann]

--keep-going does not help you, if the emerge does not start because of
missing dep/slot conflict/blocking/masking whatever...

--
#163933

[Graham Murray]

Volker Armin Hemmann <volke...@googlemail.com> writes:

> --keep-going does not help you, if the emerge does not start because of
> missing dep/slot conflict/blocking/masking whatever...

Though it would be nice if there was some flag, probably mainly of use
with either ' -u @world' or --resume, to tell portage to get on and
merge what it can and leave any masked packages or those which would
generate blockers or conflicts.

[Mark Knecht]

emerge -fDuN @world

will both check/resolve dependencies as well as insure that all files
required to do the build are downloaded. I typically run this command
prior to emerging anything as I dislike coming back and hour later and
finding the emerge didn't finish because a file either couldn't be
downloaded or its manifest didn't check out.

Just an alternative way to do things.

HTH,
Mark

[Volker Armin Hemmann]

that doesn't solve the problem I mentioned above.

--
#163933

[Alan McKinnon]

That is a terribly bad idea, and you need to have a fairly deep
understanding of IT theory to see it (which is why so few people see
it). I don't know which camp you are in.

The command is to emerge world, and it's supposed to be determinate,
i.e. when it's ready to start you can tell what it's going to do, and
that should be what you told it to do, no more and no less[1]

the command is
"emerge world"
not
"emerge the-bits-of-world-you-think-you-can-deal-with"

If portage cannot emerge world and fully obey what root told it to do,
then portage correctly refuses to continue. It could not possibly be
any other way, as eg all automated build tools (puppet, chef and
friends, even flameeyes's sandbox) break horribly if you do it any
other way. Life is hard enough dealing with build failures without
adding portage do somethign different to what it was told into the mix.

[1] "determinate" excludes build failures, as those are not predictable.
Dep graph failures happen before the meaty work begins.



--
Alan McKinnon
alan.m...@gmail.com

[kwk...@hkbn.net]

While there are good reasons not to implement it in portage itself, you
can implement it with a bit of help from shell scripts telling portage
what to do.

Do an "emerge -uDpv world", use sed or awk or whatever to replace the
beginning [ebuild ...] and whatever come after the package
name&version, and finally loop "emerge -1 =${package}" for each package
in that list. Now provided you discard the return value of emerge, if
such ${package} will give you something that portage doesn't think is a
good idea (e.g. unsatisfiable dependencies), the loop will go on to the
next package instead of completely halting.

The shell script is thus left as an exercise.

The usual warning applies:- it can be done doesn't necessarily mean it
is a good idea to do it.

Kerwin.