Summary: | app-admin/eselect - 'eselect profile' - /bin/sed: can't read //profiles/profiles.desc: No such file or directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pavel Volkov <ao> |
Component: | [OLD] Unspecified | Assignee: | Gentoo eselect Team <eselect> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jwbraun, lamusic.gentoo, orionbelt2 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pavel Volkov
2008-11-05 22:13:26 UTC
Which version of app-admin/eselect is installed on your system? It's eselect 1.0.11-r1 It sounds like somehow PORTDIR got unset on your system... what is your output for "portageq portdir" ? Sorry, I just remembered to check your --info output for PORTDIR, and it looks fine. It is puzzling then that on your system the module /usr/share/eselect/modules/profile.eselect thinks ${portdir} is empty ... I get the correct value of ${portdir}=/usr/portage using the same version of eselect?? (In reply to comment #4) > Sorry, I just remembered to check your --info output for PORTDIR, and it looks > fine. It is puzzling then that on your system the module > /usr/share/eselect/modules/profile.eselect thinks ${portdir} is empty ... I get > the correct value of ${portdir}=/usr/portage using the same version of > eselect?? It's puzzling unless perhaps PORTDIR was set to / in the shell that eselect was run in, while it wasn't set in the environment when `emerge --info' was run... I get the same output with bash as login shell and with setting PORTDIR manually: $ PORTDIR="/usr/portage" eselect profile list /bin/sed: can't read //profiles/profiles.desc: No such file or directory !!! Error: Failed to get a list of valid profiles zsh: killed PORTDIR="/usr/portage" eselect profile list *** Bug 247627 has been marked as a duplicate of this bug. *** I no longer have this error message. Don't know the reason, though. (In reply to comment #8) > I no longer have this error message. Don't know the reason, though. > I had the same issue but found that re-emerging eselect resolved this issue. Re-emerging eselect also fixed this problem for me. Re-emerging eselect did not fix this problem for me. What fixed it was un-defining the ROOT environment variable, which i was defining in my .cshrc because of some script that needs it. Alas, portage also uses ROOT (when defined) to specify the target root filesystem (e.g., read "man emerge" under "ENVIRONMENT OPTIONS") ! If running "printenv ROOT" does not return empty (or with a result that makes sense), then simply "unsetenv ROOT" (and stop defining it in your environment), and the problem should go away. Note that this affects all portage-related commands, not just eselect. For example, equery could not find packages that were actually installed. |