Bug 260353 – Request of adding feature to a portage - automatical fall back to older ebuilds of any problem occures

• Status: RESOLVED DUPLICATE of bug 300071
• Product: Gentoo Linux

[Description Jacek Mateusz 'daeron' Ławrynowicz 2009-02-26 09:39:09 UTC]

After messing up with layman I was looking for a feature that'd let portage automatically fall back to older ebuild version if any problem, like missing/masked dependencies, occures.
That feature would have 2 levels
1. It'd use older version if dependencies couldn't be met
2. It'd use older version if emerge fails.

If such thing is already possible without messing with package.mask, I'd be glad if anyone would tell me :)

Reproducible: Always

[Comment 1 Zac Medico 2009-02-26 17:21:07 UTC]

It's not supported yet. We still need to implement backtracking in the dependency resolver.

[Comment 2 Sebastian Luther (few) 2011-09-20 07:47:50 UTC]

I think the current behavior is what people usually want, namely that packages use the highest version of their dependency. In the rare cases you want to diverge from that, p.mask is imo an acceptable solution.

[Comment 3 Zac Medico 2011-09-20 17:35:15 UTC]

(In reply to comment #0)
> After messing up with layman I was looking for a feature that'd let portage
> automatically fall back to older ebuild version if any problem, like
> missing/masked dependencies, occures.
> That feature would have 2 levels
> 1. It'd use older version if dependencies couldn't be met

This is implemented with backtracking since portage-2.1.9.

> 2. It'd use older version if emerge fails.

Use emerge --keep-going, and add failed packages to package.mask as suggested in comment #2.

[Comment 4 Zac Medico 2011-09-20 17:46:11 UTC]

*** This bug has been marked as a duplicate of bug 300071 ***