Re: Bug in mkdir from fileutils 4.0 on NEXTSTEP 3.3

[Jim Meyering]

Thanks for the report.
Would you please see if that's fixed in the latest test release:

  ftp://alpha.gnu.org/gnu/fetish/fileutils-4.0.38.tar.gz

Thomas C Sobczynski <address@hidden> wrote:
| Hi.  I'd like to report an odd bug I've found in mkdir from fileutils 4.0
| under NEXTSTEP 3.3.  It manifests itself when I use "mkdir -p" with a path
| that starts with "./".  Here's what I mean:
|
| next> mkdir --verbose -p foo/bar
| created directory `foo'mkdir: created directory `foo/bar'
| next> rm -r foo
| next> mkdir --verbose -p ./foo/bar
| mkdir: `.' exists but is not a directory
| next> mkdir --version
| mkdir (GNU fileutils) 4.0
| next> rm -r foo
| rm: foo nonexistent
| next> mkdir foo
| next> rmdir foo
| next> mkdir ./foo
| next> mkdir ./foo/bar
| next> rm -r foo
| next> mkdir -p ./foo/bar
| mkdir: `.' exists but is not a directory
| next>