Bug 67435

Summary:	Portage: Suggestion for the worst case (rebuilding a broken system)
Product:	[OLD] Docs-developer	Reporter:	Martin Scherer <martin_konrad_scherer>
Component:	Portage Documentation	Assignee:	Portage team <dev-portage>
Status:	RESOLVED CANTFIX
Severity:	critical
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Martin Scherer 2004-10-13 11:30:30 UTC

Scenario: A crash produced broken files on the root partition
in this case an emerge empty world will fail, because some packages may be broken but are depended by other ebuilds!
In design of empty this should not be a problem, but a there exist several ebuilds which doesnt contain a consistent $DEPEND or even worther $RDEPEND.
Also if $RDEPEND is set correctly but the depencies are broken due the crash configure or make will fail!

The solution for this problem seems simple:
If emerge would check the consisty of $DEPEND $REPEND _before_ trying to merge the actually ebuild, a big source of errors will be eliminated!

I hope somebody would care about this even if this scenario does not occour daily ;-)


Reproducible: Always
Steps to Reproduce:
1. Crash your root fs (DO NOT DO THIS!)
2. try to emerge empty world 
3. see emerge failing on ebuilds, which have broken depencies and or broken files

Comment 1 SpanKY gentoo-dev

2004-10-13 16:06:17 UTC

there really is no way to verify the consistency of installed packages the way you want