GNU bug report logs - #10900
[cp] "cp -r a a" gives error message but copies anyway

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 10900 in the body.
You can then email your comments to 10900 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: subratkumar <subratkumar.o <at> globaledgesoft.com>
To: bug-coreutils <at> gnu.org
Subject: Regarding the observed bugs in cp
Date: Mon, 27 Feb 2012 21:57:35 +0530

1. cp -r a a
cp: cannot copy a directory, `a', into itself, `a/a'
as per this the it is not allowable to copy a into a.But its doing
2. cp -s b ../
cp: `../b': can make relative symbolic links only in current directory
its a symbolic link and should not restrict to current directory.
i have checked it in kernel 2.6.21.5 and 3.04 .Please check it and let 
me know if its corrected or not.
Thanks and Regards
Subrat Kumar Ojha

Message #8 received at 10900 <at> debbugs.gnu.org (full text, mbox):

From: era eriksson <era <at> iki.fi>
To: subratkumar.o <at> globaledgesoft.com
Cc: 10900 <at> debbugs.gnu.org
Subject: Clarification re: Regarding the observed bugs in cp
Date: Thu, 30 Aug 2012 11:08:35 +0300

I stumbled across your recent bug report for cp
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10900
and I was wondering if you could follow up with a bit of additional
information.  What did you expect to happen, and what should be fixed in
order for cp to behave like you expect?

Thanks for your bug report!  I am but a mere bystander, but I appreciate
your effort.

/* era */

-- 
If this were a real .signature, it would suck less.  Well, maybe not.

Message #13 received at 10900 <at> debbugs.gnu.org (full text, mbox):

From: era eriksson <era <at> iki.fi>
To: 10900 <at> debbugs.gnu.org
Cc: subratkumar <subratkumar.o <at> globaledgesoft.com>
Subject: Re: Clarification re: Regarding the observed bugs in cp
Date: Fri, 31 Aug 2012 07:39:06 +0300

[Message part 1 (text/plain, inline)]

Forwarding a replyI only received in private.  Please keep the Cc: on
any followups.

From: subratkumar <subratkumar.o <at> globaledgesoft.com>
To: era eriksson <era <at> iki.fi>
Date: Thu, 30 Aug 2012 17:04

On Thursday 30 August 2012 01:38 PM, era eriksson wrote:

I stumbled across your recent bug report for cp
[1]http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10900
and I was wondering if you could follow up with a bit of additional
information.  What did you expect to happen, and what should be fixed in
order for cp to behave like you expect?

Thanks for your bug report!  I am but a mere bystander, but I appreciate
your effort.

/* era */


I expected :
1.cp -r dir1 dir1 (should not copy dir1 inside dir1) ,it was coming with an erro
r message but it was copying inside dir1 ,please check it inside dir1.
2.cp -s file1 ../dir1/ (symlinking out side the current directory should be allo
wed) but it came with error symlink restricted to  current directory.
Please have a look. Let me know about these.

--
------------------------------------------------
Thanks & regards
Subrat Kumar Ojha
PMG, Global Edge Software Ltd.
Mob - +91 - 9620262307

References

1. http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10900

[Message part 2 (text/html, inline)]

[subratkumar_o.vcf (text/x-vcard, attachment)]

Message #22 received at 10900 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: 10900 <at> debbugs.gnu.org
Subject: Re: bug#10900: Clarification re: Regarding the observed bugs in cp
Date: Mon, 15 Oct 2018 10:15:53 -0600

tags 10900 moreinfo
close 10900
stop

(triaging old bugs)


On 30/08/12 10:39 PM, era eriksson wrote:
> 
> From: subratkumar <subratkumar.o <at> globaledgesoft.com>
> To: era eriksson <era <at> iki.fi>
> Date: Thu, 30 Aug 2012 17:04
> 
> On Thursday 30 August 2012 01:38 PM, era eriksson wrote:
> 
> I stumbled across your recent bug report for cp
> [1]http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10900
> and I was wondering if you could follow up with a bit of additional
> information.  What did you expect to happen, and what should be fixed in
> order for cp to behave like you expect?

With no further follow-ups in 6 years, I'm closing this bug.
Discussion can continue by replying to this thread.

regards,
 - assaf

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.