Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 27052 - portage-2.0.49_pre18 and getcwd errors
Summary: portage-2.0.49_pre18 and getcwd errors
Status: RESOLVED WONTFIX
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-21 07:20 UTC by Markus Nigbur (RETIRED)
Modified: 2011-10-30 22:18 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Nigbur (RETIRED) gentoo-dev 2003-08-21 07:20:21 UTC
I'm pretty sure I haven't seen such errors before upgrading to _pre18.

# etc-update
shell-init: could not get current directory: getcwd: cannot access parent
directories: No such file or directory
Scanning Configuration files...
shell-init: could not get current directory: getcwd: cannot access parent
directories: No such file or directory
shell-init: could not get current directory: getcwd: cannot access parent
directories: No such file or directory
shell-init: could not get current directory: getcwd: cannot access parent
directories: No such file or directory
The following is the list of files which need updating, each
configuration file is followed by a list of possible replacement files.
1) /etc/mplayer.conf
/etc/._cfg0000_mplayer.conf
Please select a file to edit by entering the corresponding number.
              (-1 to exit) (-3 to auto merge all remaining files)
                           (-5 to auto-merge AND not use 'mv -i'):

# qpkg -f /usr/sbin/etc-update
shell-init: could not get current directory: getcwd: cannot access parent
directories: No such file or directory
sys-apps/portage *
Comment 1 SpanKY gentoo-dev 2003-08-21 07:51:42 UTC
cd / 
etc-update 
 
it's cause you removed your working dir ... i do it all the time :) 
afaik, theres no way to fix those warnings when using bash scripts ... ive tried ... 
Comment 2 Markus Nigbur (RETIRED) gentoo-dev 2003-08-21 08:46:08 UTC
interesting. ;)
i'm pretty sure this message can be surpressed, but even if, it should not be necassary.
thanks for the thought-provoking impulse.