Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 252973 - emerge: Random wrong characters in environment files
Summary: emerge: Random wrong characters in environment files
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Portage team
Depends on:
Reported: 2008-12-29 10:43 UTC by Magnus Johansson
Modified: 2008-12-30 18:37 UTC (History)
0 users

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

emerge error, space has become NULL. (,38.95 KB, application/octet-stream)
2008-12-29 10:47 UTC, Magnus Johansson
Portage error where space has become NULL (,61.05 KB, application/octet-stream)
2008-12-29 10:48 UTC, Magnus Johansson
emerge error where e has become E (,51.21 KB, application/octet-stream)
2008-12-29 10:49 UTC, Magnus Johansson

Note You need to log in before you can comment on or make changes to this bug.
Description Magnus Johansson 2008-12-29 10:43:44 UTC
If I emerge a lot of files like 'emerge -e system' all packages might be re-emerged but mostly it ends with an error in an environment file in any random package. Looking at the environment file a space might have become a NULL and I also have an example where an e has become E alas 0x20 has been subtracted from the character.

Reproducible: Sometimes

I have gotten some help via the forum to resolv this; It can be found at <>
Comment 1 Magnus Johansson 2008-12-29 10:47:59 UTC
Created attachment 176726 [details]
emerge error, space has become NULL.
Comment 2 Magnus Johansson 2008-12-29 10:48:59 UTC
Created attachment 176727 [details]
Portage error where space has become NULL
Comment 3 Magnus Johansson 2008-12-29 10:49:46 UTC
Created attachment 176728 [details]
emerge error where e has become E
Comment 4 Zac Medico gentoo-dev 2008-12-30 08:36:07 UTC
I've never seen anything like it. It seems like bash or the python script that filters the environment is misbehaving, either due to some hardware or software corruption.

Rebuild bash and python to see if that helps. If that doesn't help, extract a stage3 somewhere and chroot into it, as if you're doing a fresh install. Run emerge -e system in there to see if you experience the same problem in the chroot. If you can reproduce the problem inside the chroot then it has to be related to your hardware or your kernel.
Comment 5 Magnus Johansson 2008-12-30 10:42:13 UTC
(In reply to comment #4)

Unfortunate for me I still get the error inside the chroot, so I guess I have to go out and get some new hardware.