From: LRN <lrn1986@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Copying of symbolic links not working as expected
Date: Sun, 21 Apr 2019 12:39:00 -0000 [thread overview]
Message-ID: <c4be4b51-80df-87ad-8995-00ebf7204e2e@gmail.com> (raw)
In-Reply-To: <d2bd014c-9011-907d-157b-baf70d40fdf4@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 810 bytes --]
On 21.04.2019 14:45, Matt D. wrote:
>
> I had the same problem while trying to tar and untar:
>
> tar: aosp/source/system/vold/.git/shallow: Cannot create symlink to
> ‘../../../.repo/projects/system/vold.git/shallow’: No such file or directory
My current workaround for *this* particular problem is to catch the "Cannot
create symlink" message and attempt to re-run tar multiple times until the
message is no longer outputted or the script runs out of attempts. This works
OK, unless the symlink graph is maliciously gnarly.
I doubt that this will be fixed anytime soon, it's a property of the NTFS, and
you should have known what you were signing on for when you enabled
winsymlinks:nativestrict (i'm assuming that you did; otherwise you shouldn't
have been getting these errors).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-04-21 12:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-21 10:07 Matt D.
2019-04-21 11:45 ` Matt D.
2019-04-21 12:20 ` Eliot Moss
2019-04-21 12:39 ` LRN [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c4be4b51-80df-87ad-8995-00ebf7204e2e@gmail.com \
--to=lrn1986@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).