Summary: | emerge and env-update bug | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kamil Neczaj <kneczaj> |
Component: | [OLD] GCC Porting | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | 1.4 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 136244 |
Description
Kamil Neczaj
2006-09-05 09:17:58 UTC
*** Bug 146413 has been marked as a duplicate of this bug. *** It seems that portage is getting an IOError when it tries to read one of the files in /etc/env.d/. See if you get any interesting output from the following command: for x in /etc/env.d/*; do [ -f "${x}" ] && cat "${x}" >/dev/null; done This was fixed to raise the IOError in svn r4052 (about a month ago) and has been released prior to 2.1.1_rc*. I just have fixed this bug by myself. In /etc/env.d/ was symbolic link, called 20sun-jdk-1.4.2.10, to /etc/env.d/java/20sun-jdk-1.4.2.10, which doesn't exist. Before this bug started showing I had installed sun-jdk-1.4.2.10. Next I installed sun-jdk-1.4.2.12 and unmerged sun-jdk-1.4.2.10, but the symbolic link wasn't deleted. I delated this link and made new correct link. I think this action should be exectute automaticaly by portage. (In reply to comment #4) > Before this bug started showing I had installed sun-jdk-1.4.2.10. Next I > installed sun-jdk-1.4.2.12 and unmerged sun-jdk-1.4.2.10, but the symbolic link > wasn't deleted. Portage doesn't (and shouldn't) manage the files in /etc/env.d/ any differently from any other files that are installed by packages or tools (such as java-config). Portage should handle broken symlinks better though... In svn r4416, broken symlinks cause a message to be printed to stderr. This has been released in 2.1.1_rc1-r6. |