Gentoo Archives: gentoo-user

From: Walter Dnes <waltdnes@××××××××.org>
To: Gentoo Users List <gentoo-user@l.g.o>
Subject: [gentoo-user] "We've already been run in this tree;" error world.
Date: Fri, 09 Dec 2011 09:29:22
Message-Id: 20111209092732.GA24071@waltdnes.org
In Reply to: [gentoo-user] Error message for several ebuilds when updating world. by waltdnes@waltdnes.org
1 On Fri, Nov 25, 2011 at 02:20:59AM -0500, waltdnes@××××××××.org wrote
2 > I just ran a sync and update on my laptop. The builds for...
3 >
4 > gnome-extra/libgsf-1.14.21
5 > x11-libs/gdk-pixbuf-2.24.0-r1
6 > gnome-base/librsvg-2.34.1-r1
7 > www-client/firefox-7.0.1-r1
8 > app-text/ghostscript-gpl-9.04-r4
9 > app-office/abiword-2.8.6-r1
10 >
11 > ...all came up with the same warning in /var/log/portage/elog
12 >
13 > WARN: prepare
14 > We've already been run in this tree; you should
15 > avoid this if possible (perhaps by filing a bug)
16
17 Somedays my Google-fu is better than others. Today I ran into the
18 same error, and managed to find a discussion on the mailing list...
19 http://www.gossamer-threads.com/lists/gentoo/dev/242435?do=post_view_flat#
20
21 vapier says...
22
23 > it seems we have some cases where eclasses/ebuilds interact
24 > poorly. for example, if an eclass runs eautoreconf or elibtoolize, and
25 > then the ebuild does some stuff where it ends up running eautoreconf,
26 > subsequent elibtoolize calls are skipped.
27 >
28 > this means that the work done by the earlier elibtoolize call was all
29 > for naught, as eautoreconf blows all of its work away be regenerating
30 > the files elibtoolize patched. and when eautoreconf attempts to run
31 > elibtoolize itself, we don't get all the fun patches since elibtoolize
32 > detected it was run already.
33 >
34 > rather than have this continue to silently ignore the issue, i'm
35 > thinking of making these changes:
36 > - elibtoolize now has a --force flag
37 > - eautoreconf always calls elibtoolize with --force
38 > - if elibtoolize detects a previous run with --force, it warns, but runs
39 > this way we complain, but at least we continue to work
40
41 In a later message in that same thread he says...
42 > yes, but the current state is that people don't notice and things
43 > silently break. i'm turning the situation into a QA warning so bug
44 > reports get filed/fixed, and things continue to work in the mean time.
45
46 I appended my info to https://bugs.gentoo.org/show_bug.cgi?id=391749
47
48 --
49 Walter Dnes <waltdnes@××××××××.org>