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 types of objects, both for filesystem and for the archive.
I will argue that the message a/y: Not linked to a/y is incorrect, as it says that the file (whatever its type is) is not linked to *itself*, which does not make sense to me. I would rather expect: a/z: Not linked to a/y or vice versa: a/y: Not linked to a/z Much thanks for your reply anyway, C.S. > > Regards, > Sergey > -- Cezary Sliwa Institute of Physics, Polish Academy of Sciences al. Lotnikow 32/46, PL 02-668 Warszawa, POLAND
