* [gentoo-user] "We've already been run in this tree;" error world.
@ 2011-12-09 9:27 99% ` Walter Dnes
0 siblings, 0 replies; 1+ results
From: Walter Dnes @ 2011-12-09 9:27 UTC (permalink / raw
To: Gentoo Users List
On Fri, Nov 25, 2011 at 02:20:59AM -0500, waltdnes@waltdnes.org wrote
> I just ran a sync and update on my laptop. The builds for...
>
> gnome-extra/libgsf-1.14.21
> x11-libs/gdk-pixbuf-2.24.0-r1
> gnome-base/librsvg-2.34.1-r1
> www-client/firefox-7.0.1-r1
> app-text/ghostscript-gpl-9.04-r4
> app-office/abiword-2.8.6-r1
>
> ...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...
http://www.gossamer-threads.com/lists/gentoo/dev/242435?do=post_view_flat#
vapier says...
> 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 <waltdnes@waltdnes.org>
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2011-11-25 7:20 [gentoo-user] Error message for several ebuilds when updating world waltdnes
2011-12-09 9:27 99% ` [gentoo-user] "We've already been run in this tree;" error world Walter Dnes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox