cp ignore default ACLs

[Jakub Turski]

Binary package hint: coreutils

Hi,

Given:

yacoob:~/stuff/music/_in[261]> getfacl .
# file: .
# owner: yacoob
# group: yacoob
user::rwx
group::r-x
other::r-x
default:user::rwx
default:group::r-x
default:other::r-x

I get following bad behaviour:

yacoob:~/stuff/music/_in[264]> ls -l /tmp/bam
-r--r--r-- 1 yacoob yacoob 0 2007-09-22 15:27 /tmp/bam
yacoob:~/stuff/music/_in[265]> cp --no-preserve=all /tmp/bam .
yacoob:~/stuff/music/_in[266]> ls -l bam
-r--r--r-- 1 yacoob yacoob 0 2007-09-22 15:27 bam

I do believe cp should get the access rights from the default ACL of the directory we're copying files to, with --no-preserve in effect.
This is similar to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=402332

Best regards,

KT.

[Aaron Toponce (atoponce-deactivatedaccount)]

The man page is also wrong. It describes 'cp -p' is the same as 'cp --preserve=mode,ownership,timestamps'. This is correct. However, it also describes 'cp -a', the same as 'cp -dpR'. This is incorrect. It should actually be 'cp -dpPR' which should be 'cp -dPR --preserve=mode,ownership,timestamps,context,links', which is obviously incorrect with the initial -p.

[xteejx (xteejx-deactivatedaccount)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release?

Aaron Toponce: This needs to be reported as a separate bug if it is still an issue.

Thank you.

[C de-Avillez (hggdh2)]

Additionally, coreutils 7.3 (currently available on karmic) has had many changes on cp. Up to Jaunty, at least since Intrepid, we were using coreutils 6.10.

[xteejx (xteejx-deactivatedaccount)]

Agreed hggdh, therefore if at all possible, it may be beneficial to upgrade to Karmic when it is released, as this is quite a jump in versions in coreutils, I would assume that this is probably fixed - needs verifying.

[xteejx (xteejx-deactivatedaccount)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!