| Summary: | xpak.py fails if $PWD doesnt exist | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | SpanKY <vapier> |
| Component: | Unclassified | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED FIXED | ||
| Severity: | trivial | Keywords: | InVCS |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
portage-2.0.50_pre9 supposed to be fixed in 2.0.50 which is stable now. If this bug is not fixed please reopen. |
here is how to reproduce it: root@vapier 0 root # mkdir blah root@vapier 0 root # cd blah root@vapier 0 blah # rm -rf ../blah root@vapier 0 blah # rm `portageq envvar PKGDIR`/All/coreutils* root@vapier 0 blah # quickpkg coreutils shell-init: could not get current directory: getcwd: cannot access parent directories: No such file or directory * Building package for coreutils-5.0-r3... <tar output> Traceback (most recent call last): File "/usr/bin/xpak", line 11, in ? xpak.xpak(sys.argv[1],sys.argv[2]) File "/usr/lib/python2.2/site-packages/xpak.py", line 57, in xpak origdir=os.getcwd() OSError: [Errno 2] No such file or directory <some more unrelated output> * Packages now in /mnt/space/packages: * coreutils-5.0-r3: not created root@vapier 0 blah #