[debbugs-tracker] bug#24251: closed (Potential cp bug: directories created with --parents and --no-preserve=mode retain original mode bits don't match ~umask)

[GNU bug Tracking System]

Your message dated Thu, 18 Aug 2016 13:57:48 +0100
with message-id <address@hidden>
and subject line Re: bug#24251: Potential cp bug: directories created with 
--parents and --no-preserve=mode retain original mode bits don't match ~umask
has caused the debbugs.gnu.org bug report #24251,
regarding Potential cp bug: directories created with --parents and 
--no-preserve=mode retain original mode bits don't match ~umask
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
24251: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24251
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: Potential cp bug: directories created with --parents and --no-preserve=mode retain original mode bits don't match ~umask Date: Wed, 17 Aug 2016 11:42:40 +0000

Hi,

I'm writing to report a potential bug with cp.  I don't think the mode bits always get properly set on directories created when using the --parents option combined with --no-preserve=mode option.  I'm not sure what the expected behaviour is supposed to be, but my assumption is that the created directories would match process's ~umask (like mkdir -p).

I've attached a simple script and its output to demonstrate the behaviour.  I've tested this on the most recent master branch of the coreutils git repository (output of git describe is 'v8.25-55-gff2178b').

Thanks for your efforts on these utilities, it is much appreciated :-).

-Mark

test-output.txt
Description: Text document

test-cp-parents-umask.sh
Description: Bourne shell script

--- End Message ---

--- Begin Message --- Subject: Re: bug#24251: Potential cp bug: directories created with --parents and --no-preserve=mode retain original mode bits don't match ~umask Date: Thu, 18 Aug 2016 13:57:48 +0100 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

On 17/08/16 12:42, Mark Mitchell wrote:
> Hi,
> 
> I'm writing to report a potential bug with cp.  I don't think the mode bits
> always get properly set on directories created when using the --parents
> option combined with --no-preserve=mode option.  I'm not sure what the
> expected behaviour is supposed to be, but my assumption is that the created
> directories would match process's ~umask (like mkdir -p).
> 
> I've attached a simple script and its output to demonstrate the behaviour.
> I've tested this on the most recent master branch of the coreutils git
> repository (output of git describe is 'v8.25-55-gff2178b').
> 
> Thanks for your efforts on these utilities, it is much appreciated :-).

I agree that's unexpected, especially since cp -r --no-preserve=mode
does not copy the permissions for created dirs.

I think this may have changed with:
http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=v5.92-435-gfdffb6b

I've adjusted things back in the attached.

thanks,
Pádraig.

cp-parents-no-preserve-mode.patch
Description: Text Data

--- End Message ---