Description of problem: mc man page says: Preserve attributes ... If this option is not set, the current value of the umask will be respected. However, when I uncheck that checkbox in the copy dialog, target file is always created with mode 600 - my biggest concern is that it's not readable for anyone but me. My umask is 0022. Version-Release number of selected component (if applicable): mc-4.6.1a-13.FC5 How reproducible: Always Steps to Reproduce: 1. launch mc 2. go to a file with unusual permissions (the bug will then reveal better) 3. F5, uncheck Preserve attributes, OK Actual results: target file has mode 600 Expected results: target file mode respects umask Additional info: Life would be really cool without this bug. One could then e.g. copy files from CDs of FAT partitions, where the files have undesired permissions, into destination directories without having to chmod them to something usable - currently, neither Preserve Attributes nor this option disabled create copies that are appropriate for further sharing.
Created attachment 141092 [details] fix
What mc with the patch above does is it preserves attributes of the source file when Preserve Attributes is unchecked. So now it basically doesn't matter if it's checked or not...
it works for me. if the destination file already exists and Preserver Attributes is unchecked, the destination file keeps its former attributes. maybe this is your case..? i've copied this behaviour from cp, so i hope it's correct. please let me know, if there's some other issue.
Just tried in Fedora 8 - I'm seeing the behavior I described in comment 2. Looks like the patch made it into mc. But that's wrong, as I said, mc with this patch simply ignores the Preserve Attributes checkbox - the destination file gets permissions identical to the permissions of the original file REGARDLESS OF the checkbox value (checked or not). I'm talking about a situation where the destination file doesn't exist before copying. Changing bug summary accordingly.
It's now fixed in F8 cvs. Will be really fixed as the next mc update for F8 will show up. Thanks for reporting!
mc-4.6.1a-50.20070604cvs.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update mc'
With the version now in updates-testing, mc is back where it was when this bug was reported. (see comment 0.) So the problem with ignoring Preserve Attributes is fixed, but not in the way I expected :)
mc-4.6.1a-50.20070604cvs.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
It does! As written in comment 7.
This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
Sorry for not responding back earlier. It's still around.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.