Bug 431638 – sys-apps/sandbox-2.6 sometimes sends QA warnings to tty

• Product: Portage Development
• Status: RESOLVED FIXED

[Description Michael Weiser 2012-08-16 16:16:06 UTC]

sandbox recently prints messages such as:

>>> Emerging (91 of 208) sys-apps/lm_sensors-3.3.1
>>> Jobs: 85 of 208 complete, 2 running             Load avg: 2.41, 2.50, 2.56 (null)*(null) Unable to trace static ELF: /sbin/ldconfig: /sbin/ldconfig -p
>>> Jobs: 85 of 208 complete, 2 running             Load avg: 2.61, 2.55, 2.57 (null)*(null) Unable to trace static ELF: /sbin/ldconfig: /sbin/ldconfig -p
>>> Jobs: 85 of 208 complete, 2 running             Load avg: 2.63, 2.57, 2.58 (null)*(null) Unable to trace static ELF: /sbin/ldconfig: /sbin/ldconfig -p
>>> Jobs: 85 of 208 complete, 2 running             Load avg: 2.60, 2.57, 2.58 (null)*(null) Unable to trace static ELF: ./conftest: ./conftest
>>> Installing (91 of 208) sys-apps/lm_sensors-3.3.1

This seems to have been introduced in sandbox-2.6.

Might this be related to https://bugs.gentoo.org/show_bug.cgi?id=364877#c4?

[Comment 1 SpanKY 2012-08-16 17:51:17 UTC]

sandbox has always complained about tracing static binaries.  it just might not have bubbled up to the level where you noticed.

[Comment 2 Michael Weiser 2012-08-16 19:44:12 UTC]

Shame on me. But since I do notice now, I'd like to get rid of it. Is there a way?

[Comment 3 SpanKY 2013-02-25 04:25:15 UTC]

should be fixed by:
http://git.overlays.gentoo.org/gitweb/?p=proj/sandbox.git;a=commitdiff;h=e12fee192ac8b0343a468e5a8f7811a7b029ff9a

[Comment 4 SpanKY 2013-04-18 15:59:33 UTC]

*** Bug 466314 has been marked as a duplicate of this bug. ***

[Comment 5 aditsu 2014-02-28 09:32:35 UTC]

I'm still seeing "Unable to trace static ELF" messages.
sandbox-2.6-r1, wine-1.6.1

[Comment 6 SpanKY 2015-05-26 00:04:27 UTC]

*** Bug 503532 has been marked as a duplicate of this bug. ***

[Comment 7 Pastafarianist 2015-09-28 19:47:32 UTC]

Please reopen this issue, since it is not actually resolved.

[Comment 8 SpanKY 2015-09-28 20:31:34 UTC]

(In reply to Pastafarianist from comment #7)

you need to provide real details as to how it's not resolved.  simply saying "it's still broken" is not useful.

make sure you've actually upgraded your sandbox to the latest version (2.9) first.

[Comment 9 Pastafarianist 2015-09-28 20:38:34 UTC]

(In reply to SpanKY from comment #8)
> (In reply to Pastafarianist from comment #7)
> 
> you need to provide real details as to how it's not resolved.  simply saying
> "it's still broken" is not useful.
> 
> make sure you've actually upgraded your sandbox to the latest version (2.9)
> first.

2.9 is not even in the tree yet. I am on 2.6-r1, which is the latest stable, and https://bugs.gentoo.org/show_bug.cgi?id=466314 is still present in it.

[Comment 10 SpanKY 2015-09-28 21:04:57 UTC]

(In reply to Pastafarianist from comment #9)

yes, it is.  your tree is probably out of date in which case you need to sync.

the bug is marked fixed because it's in git/release.  i don't track stable bugs because eventually all versions go stable, and these aren't critical enough to do straight-to-stable backports.

[Comment 11 Pastafarianist 2015-09-28 21:10:33 UTC]

(In reply to SpanKY from comment #10)
> (In reply to Pastafarianist from comment #9)
> 
> yes, it is.  your tree is probably out of date in which case you need to
> sync.
> 

You're right — for some reason, I thought that I had eix-sync in crontab. A friend has also told me that 2.9 doesn't have this bug. Sorry for the inconvenience.

[Comment 12 SpanKY 2015-09-28 21:19:21 UTC]

(In reply to Pastafarianist from comment #11)

np.  glad it seems to be working for someone else ;).