Summary: | Inheriting completely broken in portage 2.0.33 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Maurizio Disimino <kevin> |
Component: | Unclassified | Assignee: | Daniel Robbins (RETIRED) <drobbins> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | gkajmowi, kurt.hindenburg, magus |
Priority: | Lowest | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Maurizio Disimino
2002-08-31 02:20:28 UTC
Confirmed. Portage .33 breaks _all_ eclass-using apps; the inheriting simply doesn't happen. This is due to the new code that makes inherit() conditional on $PORTAGE_RESTORE_ENV != 1. This doesn't work for some reason or other. I've disabled this code and made a portage-2.0.33_p1 to make things work for now (I haven't changed the internal portage version number because I wasn't sure how it'd react to a _p1 version). BTW the change to inherit() that broke it wasn't even in the porage changelog. Please tell whoever committed it (don't remember who it was, I think it wasn't you?) to be more careful... BTW there's lots of cvs-conflict and patch-reject files in the portage tarballs. You should prune them, it would make the tarballs smaller :-) *** Bug 7302 has been marked as a duplicate of this bug. *** *** Bug 7304 has been marked as a duplicate of this bug. *** *** Bug 7308 has been marked as a duplicate of this bug. *** fixed in 2.0.34; thanks. |