Cezary Sliwa wrote:
>
> On Wed, November 8, 2017 18:14, Joerg Schilling wrote:
> > Cezary Sliwa wrote:
> >
> >> ==
> >>
> >> I get
> >>
> >> a/y: Not linked to a/y
>^^^
>
> >>
> >> which is evidently incorrect.
> >
> > This is correct.
>
> I am not sure whether you mean that
Fixed by commit 1bf590ab [1]. Thank you!
Regards,
Sergey
[1]
http://git.savannah.gnu.org/cgit/tar.git/patch/?id=1bf590ab2da3c40d68d2b4167e494c786ffda6e7
Cezary Sliwa ha escrit:
> I will argue that the message
>
> a/y: Not linked to a/y
>
> is incorrect
Ah, I see the point... Yes, of course, you are right. I'll fix it.
Regards,
Sergey
On Wed, November 8, 2017 18:14, Joerg Schilling wrote:
> Cezary Sliwa wrote:
>
>> ==
>>
>> I get
>>
>> a/y: Not linked to a/y
^^^
>>
>> which is evidently incorrect.
>
> This is correct.
I am not sure whether you mean that the printed message is correct or my
claim that it is
Cezary Sliwa wrote:
> ==
>
> I get
>
> a/y: Not linked to a/y
>
> which is evidently incorrect.
This is correct.
With star -diff -v you get:
star: Blocksize = 16 records.
diffopts=perm,type,nlink,uid,gid,uname,gname,size,data,rdev,hardlink,symlink,sympath,sparse,mtime,ctime,dir
On Wed, November 8, 2017 16:14, Sergey Poznyakoff wrote:
> Hi Cezary,
>
>> To reproduce the bug, enter these shell commands
>
> That's not a bug, but intended behaviour.
>
>> ln a/y a/z
> [...]
>> rm a/z
>> ln -s x a/z
>
> You are replacing a hard link with a symbolic one. These are two
> distinct
Hi Cezary,
> To reproduce the bug, enter these shell commands
That's not a bug, but intended behaviour.
> ln a/y a/z
[...]
> rm a/z
> ln -s x a/z
You are replacing a hard link with a symbolic one. These are two
distinct types of objects, both for filesystem and for the archive.
Regards,
Sergey
