497154 – Portage (or sys-libs/glibc ebuild) needs to warn user if FEATURES=fakeroot and glibc has been updated

Bug 497154 - Portage (or sys-libs/glibc ebuild) needs to warn user if FEATURES=fakeroot and glibc has been updated

Summary: Portage (or sys-libs/glibc ebuild) needs to warn user if FEATURES=fakeroot an...

Status:	RESOLVED INVALID

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Sandbox (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Sandbox Maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-01-05 16:56 UTC by Andreas K. Hüttel
Modified:	2014-01-05 18:37 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Andreas K. Hüttel archtester

2014-01-05 16:56:12 UTC

from the fakeroot man page: "Every command executed within fakeroot needs to be linked to the same version of the C library as fakeroot itself."

glibc was recently updated, and I have FEATURES=fakeroot set, which may explain why I am suddenly unable to complete emerge -eav world (random hangs without cpu usage).

testing now with FEATURES=-fakeroot set

(another possible cause for the hangs might be bug 487558)

given the manpage, my suggestion would be that
* either the sys-libs/glibc ebuild outputs a fat warning on update if FEATURES=fakeroot is set
* or that portage detects a glibc update and warns

Comment 1 Andreas K. Hüttel archtester

2014-01-05 18:37:17 UTC

(In reply to Andreas K. Hüttel from comment #0)
>
> glibc was recently updated, and I have FEATURES=fakeroot set, which may
> explain why I am suddenly unable to complete emerge -eav world (random hangs
> without cpu usage).
> 
> testing now with FEATURES=-fakeroot set
> 

actually the hangs seem to be unrelated to fakeroot. :( 

doesn't change the thing about the manpage instructions, but the issue is probably not so serious. 

I'm closing the bug, reopen if you still want to act on it.