cp preserves mode with --no-preserve=mode

Thank you for opening this bug and helping make Ubuntu better. Can you please state your Ubuntu and coreutils versions?

Also, can you please show an example?

Hi there, it's now a vfat fs plugged into a 9.10 system:
ii coreutils 7.4-2ubuntu1 The GNU core utilities

$ ls -l /media/USB/
-rwxr-xr-x 1 test.txt1
-rwxr-xr-x 1 test.txt2

$ cp /media/USB/test.txt1 .
$ ls -l
-rwxr-xr-x 1 test.txt1

$ cp --no-preserve=mode /media/USB/test.file2 .
$ ls -l
-rwxr-xr-x 1 test.txt1
-rwxr-xr-x 1 test.txt2

With --no-preserve I'd expect the new file to have the same permissions as a newly created file (umask dependent) but this is not the case.

Thank you. Now, the only thing missing is your umask ;-)

I do not have, right now, a vfat I can mount & test -- will find where I stowed one, I *know* I should have it. I tested under an etx4, and it works as expected.

yeah, right a umask setting the exec bit ;-)

Regarding comments in debbugs #488024

cp --no-preserve=mode ... should be different to cp ...! This is really a bug, because the option does not create the new copy with standard new file permission (not preserving the mode of the original file).

This --no-preserve=mode is a standard use case, for example, when copying files from an iso CD (all "executable") to a filesystem with more attributes.

Attatched the patch from Jim Meyering

This appears to be fixed in 8.20, now on its way into raring. From the NEWS file:

  cp --no-preserve=mode now no longer preserves the original file's
  permissions but correctly sets mode specified by 0666 & ~umask