Bug 301640 – force emerge @preserved-rebuild even if some packages are lacking

• Status: CONFIRMED
• Product: Portage Development

[Description Helmut Jarausch 2010-01-20 16:26:39 UTC]

Hi,
sometimes some packages cannot be re-emerged (currently e.g.
app-office/kexi)
In that case emerge @preserved-rebuild cannot be persuaded to do
any other upgrades (currently nearly 100 packages due to a new jpeg
library)
It would be nice if there were an option to tell emerge to re-emerge
anything that can be done (not depending on those packages which cannot
be re-emerged currently)

I am using portage-2.2_rc61

[Comment 1 Zac Medico 2010-01-21 05:46:15 UTC]

We can do this by tagging the set's atoms as "optional".

[Comment 2 Erik Zeek 2010-10-23 14:00:37 UTC]

(In reply to comment #0)
> It would be nice if there were an option to tell emerge to re-emerge
> anything that can be done (not depending on those packages which cannot
> be re-emerged currently)

Isn't that what --keep-going does?  I've used it for this in the past.

[Comment 3 Zac Medico 2010-10-23 14:07:08 UTC]

(In reply to comment #2)
> Isn't that what --keep-going does?  I've used it for this in the past.

No, not exactly. What's really needed is a way to cope better with unsatisfied dependencies, as requested in bug 328343.