"We've already been run in this tree;" error world.
On Fri, Nov 25, 2011 at 02:20:59AM -0500, email@example.com wrote
> I just ran a sync and update on my laptop. The builds for...
> ...all came up with the same warning in /var/log/portage/elog
> WARN: prepare
> We've already been run in this tree; you should
> avoid this if possible (perhaps by filing a bug)
Somedays my Google-fu is better than others. Today I ran into the
same error, and managed to find a discussion on the mailing list...
> it seems we have some cases where eclasses/ebuilds interact
> poorly. for example, if an eclass runs eautoreconf or elibtoolize, and
> then the ebuild does some stuff where it ends up running eautoreconf,
> subsequent elibtoolize calls are skipped.
> this means that the work done by the earlier elibtoolize call was all
> for naught, as eautoreconf blows all of its work away be regenerating
> the files elibtoolize patched. and when eautoreconf attempts to run
> elibtoolize itself, we don't get all the fun patches since elibtoolize
> detected it was run already.
> rather than have this continue to silently ignore the issue, i'm
> thinking of making these changes:
> - elibtoolize now has a --force flag
> - eautoreconf always calls elibtoolize with --force
> - if elibtoolize detects a previous run with --force, it warns, but runs
> this way we complain, but at least we continue to work
In a later message in that same thread he says...
> yes, but the current state is that people don't notice and things
> silently break. i'm turning the situation into a QA warning so bug
> reports get filed/fixed, and things continue to work in the mean time.
I appended my info to https://bugs.gentoo.org/show_bug.cgi?id=391749
Walter Dnes <firstname.lastname@example.org>
|All times are GMT. The time now is 12:40 AM.|
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.