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
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