coreutils @9.5 cp cannot copy file on file on PPC Mac OS X 10.4.11, Tiger

[ballapete (Peter "Pete" Dyballa)]

root 368 /\ which cp
/opt/local/libexec/gnubin/cp
root 369 /\ port provides /opt/local/libexec/gnubin/cp
/opt/local/libexec/gnubin/cp is provided by: coreutils
root 370 /\ env LANG=C cp -v Portfiles/Portfile-mupdf-Tess `port file mupdf`
cp: cannot stat '/opt/local/var/macports/sources/nue.de.rsync.macports.org/macports/release/tarballs/ports/graphics/mupdf/Portfile/Portfile-mupdf-Tess': Not a directory
root 371 /\ port installed -v coreutils
The following ports are currently installed:
  coreutils @9.5_0 (active) requested_variants='' platform='darwin 8' archs='ppc' date='2024-04-30T13:37:26+0200'

With former versions of coreutils it worked to copy a locally corrected version of Portfile over the MacPorts' version. Now I have to use /bin/cp…

The documentation writes:

You can either copy one file to another, or copy arbitrarily many files to a destination directory.

[mascguy (Christopher Nielsen)]

Let's test the basics. Can you try the following tests in your home directory, and paste the results?

$ gtouch -v foo
$ gcp -v foo foo2
$ gmkdir -v doo
$ gcp -v foo doo/
$ gcp -v foo doo/foo2

[ballapete (Peter "Pete" Dyballa)]

pete 299 /\ env LANG=C gtouch -v foo
gtouch: invalid option -- 'v'
Try 'gtouch --help' for more information.
Exit 1
pete 300 /\ env LANG=C gtouch foo
pete 301 /\ env LANG=C gcp -v foo foo2
'foo' -> 'foo2'
pete 302 /\ gmkdir -v doo
gmkdir: Verzeichnis 'doo' angelegt
pete 303 /\ env LANG=C gcp -v foo doo/
'foo' -> 'doo/foo'
pete 304 /\ env LANG=C gcp -v foo doo/foo2
'foo' -> 'doo/foo2'

And here is my case, copy onto an existing file:

pete 305 /\ env LANG=C gcp -v foo2 doo/foo2
gcp: cannot stat 'doo/foo2/foo2': Not a directory
Exit 1

[ballapete (Peter "Pete" Dyballa)]

And here is one more variation:

pete 306 /\ env LANG=C gcp -v foo2 doo/foo
gcp: cannot stat 'doo/foo/foo2': Not a directory
Exit 1

[ryandesign (Ryan Carsten Schmidt)]

MacPorts doesn't deliberately introduce bugs for older systems. Therefore this must be an upstream bug and should be ​reported to them.