[Hackage] #321: cabal in non-existant directory fails

[Hackage]

#321: cabal in non-existant directory fails
----------------------------+-----------------------------------------------
  Reporter:  larsv          |        Owner:         
      Type:  defect         |       Status:  new    
  Priority:  normal         |    Milestone:         
 Component:  Cabal library  |      Version:  1.4.0.1
  Severity:  normal         |   Resolution:         
  Keywords:                 |   Difficulty:  normal 
Ghcversion:  6.8.3          |     Platform:  Linux  
----------------------------+-----------------------------------------------
Changes (by larsv):

  * ghcversion:  6.8.2 => 6.8.3

Old description:

> To reproduce:
> {{{
> mkdir foo ; cd foo ; rmdir ../foo ; cabal install regex-pcre
> }}}
>
> Result:
> {{{
> shell-init: error retrieving current directory: getcwd: cannot access
> parent directories: No such file or directory
> Resolving dependencies...
> 'regex-base-0.93.1' is cached.
> cabal: Error: some packages failed to install:
> regex-base-0.93.1 failed during the configure step. The exception was:
> getCurrentDirectory: does not exist (No such file or directory)
> regex-pcre-0.94.1 depends on regex-base-0.93.1 which failed to install.
> }}}
>
> The first shell-init error occurs even if no package is chosen or any
> other cabal command is used such as "list" or "upgrade".

New description:

 To reproduce:
 {{{
 mkdir foo ; cd foo ; rmdir ../foo ; cabal install regex-pcre
 }}}

 Result:
 {{{
 shell-init: error retrieving current directory: getcwd: cannot access
 parent directories: No such file or directory
 Resolving dependencies...
 'regex-base-0.93.1' is cached.
 cabal: Error: some packages failed to install:
 regex-base-0.93.1 failed during the configure step. The exception was:
 getCurrentDirectory: does not exist (No such file or directory)
 regex-pcre-0.94.1 depends on regex-base-0.93.1 which failed to install.
 }}}

 The first shell-init error occurs even if no package is chosen or any
 other cabal command is used such as "list" or "upgrade".
 However, that seems to be intrinsic to ghc as it shows when running just
 the ghc binary as well.

-- 
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/321#comment:1>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects