Summary: | "sudo repoman manifest" results in traceback | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Raffaello D. Di Napoli <rafdev> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077, 288499 | ||
Attachments: | patch for repoman |
Description
Raffaello D. Di Napoli
2009-08-31 04:09:30 UTC
Created attachment 202767 [details, diff]
patch for repoman
It appears that this is caused by having an empty or unset PWD environment variable. This patch fixes that issue, by allowing repoman to ignore an empty or unset PWD.
(In reply to comment #1) > Created an attachment (id=202767) [edit] > patch for repoman Thanks, that's in svn r14174. Sorry for the delay, I now found a few minutes to try the suggested patch. $ sudo repoman manifest [CRITICAL] Repoman is unable to determine PORTDIR or PORTDIR_OVERLAY from the current working directory $ sudo bash # repoman manifest [CRITICAL] Repoman is unable to determine PORTDIR or PORTDIR_OVERLAY from the current working directory # exit exit $ So now it’s just not working, no matter if I’m root or not. I also don’t understand the PWD issue. If I run `echo $PWD` I do get the right working directory, so I guess we’re not talking about the same PWD. Ah, except sudo clears the environment, right. Okay, got it now. This is fixed in 2.2_rc41. This is fixed in 2.1.7. |