delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2019/04/21/08:39:35

X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:subject:to:references:from:message-id:date
:mime-version:in-reply-to:content-type; q=dns; s=default; b=ai09
QnnbKWOmO3RaquRMgkQ0w13QHO+9StNcS5O3QkSGLTiK/gO6Tpo9JGX8yQ9/nI+q
9E5mp68tZmR2o1oVPYSZvvab8hD4ALwJrJze0H+IrzX8pDUSBXIHnemUN9dxk9wW
B8S/QvT7+10JrnAdcAPI0v0MCxD2COwjVh1loB0=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:subject:to:references:from:message-id:date
:mime-version:in-reply-to:content-type; s=default; bh=j9hrEVl80a
rI4SeVrXoJ5r5j2Ao=; b=IB2z1Jsklg1NGzbXi5oTdNXfmL+Lt2+Q9IXhnq2XIz
A+uMlE0nWwfc7w/Frl4jCpFsGuaH/4T9hl2ozDlFwo1bitM04NOo3yquwG8Y4l1v
G+LDyZFXKmIKnG/LpucOT2qeYDuID5aPoY7rpy/xtC9B+1efwSbsO0S5q5nU+6NH
U=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_50,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=H*RU:sk:broadba, HX-Spam-Relays-External:sk:broadba, H*UA:x64, H*UA:Win64
X-HELO: mail-lj1-f175.google.com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:autocrypt:message-id:date:user-agent :mime-version:in-reply-to; bh=1/Z9YhV1aSJNBkSchWcdVquAbiY6UrWcp+xo8aHDhlI=; b=vCzlhAw2XQuJEkZMcOvkd6WKkPgT8TjeBM1f2+roW6svHpTTByMbvn8+DUjdA1KIOj cIQnGPmG8yO0g4EoHbUe0eFOVCdpCHit0W5RExo8dJTT06qio79OZ9dNI1cyYaVWVPp1 kRvncKB1PbRIkd/gyQwR+/2eWwRNKSl2vimL3eX/4w5oabVz0J91M/kr5fJIL4ZER9DF JgxQpbuG2lpspVhvaxr62vW0UTpyZz6OX55V7ZJYqDj6+OobvvdT0NfGGJidGlfbT2yB bZ+JTJe4+cC5gpdyKWorC5deivpdrLTJ7kWFHvw/rHs6Atia0E5IEN4N2HYf1W+IwaiU yQyQ==
Subject: Re: Copying of symbolic links not working as expected
To: cygwin AT cygwin DOT com
References: <a79d955d-6324-4b87-9973-665967aba511 AT gmail DOT com> <d2bd014c-9011-907d-157b-baf70d40fdf4 AT gmail DOT com>
From: LRN <lrn1986 AT gmail DOT com>
Message-ID: <c4be4b51-80df-87ad-8995-00ebf7204e2e@gmail.com>
Date: Sun, 21 Apr 2019 15:39:13 +0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <d2bd014c-9011-907d-157b-baf70d40fdf4@gmail.com>
X-IsSubscribed: yes

--Kc4Mq0TylaEF4CMdXssDEiRzN6CbciXD6
Content-Type: multipart/mixed; boundary="6EWirSEEwuppqkLZUIwDVBLpAbe7uxDtd";
 protected-headers="v1"
From: LRN <lrn1986 AT gmail DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <c4be4b51-80df-87ad-8995-00ebf7204e2e AT gmail DOT com>
Subject: Re: Copying of symbolic links not working as expected


--6EWirSEEwuppqkLZUIwDVBLpAbe7uxDtd
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 21.04.2019 14:45, Matt D. wrote:
>=20
> I had the same problem while trying to tar and untar:
>=20
> tar: aosp/source/system/vold/.git/shallow: Cannot create symlink to=20
> =E2=80=98../../../.repo/projects/system/vold.git/shallow=E2=80=99: No suc=
h 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 wor=
ks
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).


--6EWirSEEwuppqkLZUIwDVBLpAbe7uxDtd--

--Kc4Mq0TylaEF4CMdXssDEiRzN6CbciXD6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE4MWzR43wYaAzEA49ja3pJ2dZunQFAly8ZHEACgkQja3pJ2dZ
unSYKQ/+P865k0YFlDrLqusvoOXrF2JJQssYd4P+3dGgwN38BYj0ZdXxKE7JsC8D
FY2QlQ6B0Gj8wKksMONpdp98mCtbf9Fa+T50FLey2Vcbc1+UA8Blgrd1W9cx0ce+
4y1Wt2vZkATwx+2ZPFHr8Vz5myvX8vihmStmVydKPV72eKjCBxivLlI86QWnffpA
DSEGOD3GPs+v8M8+Q0ZqcjiVIpErylYrYi3ELZoD3zVuRoi7xtZ0IzbohqfrgnGb
wY/ojnNz7KMt7df42MH+4yMqvc+0yi7EaMXEbX0/f/5Nwd8y+LsM0Fb90wfZRS/o
tHwLHA5XTFu7FpsR7RsAhGyPmlaM6ELV2KqX6T3cdorqlY27xVy1DdFLBXzoccSO
hv/s43NdyH0S2xaWxWsamvlq6Ndub7hdJB7NVD9WebsW1VmwNRYri0cj8Q3/iRtW
WLuO1XKyDPGwGQ3DFqTGLHTrHmupMGFG0RQSYarJ8oVVNLZ5XJrBAj0jgThY0lIM
HAUWf6OvGbNZZMJ5mQIWh+4XLkfu2HDTSBbUQ3Y+hqYpJGKP45efsrWq8+tI7wC9
sG+GOFtX5MbkUQJwn7J2wxnyceIA5Gs6/EvFCwyQxlnXsxF5zgWbRd2x0zrOpQFE
efEipi+BFqyYzGSJlb16qapXsiH+LD51rha2SgvkfKGp5OhcqdM=
=dUgY
-----END PGP SIGNATURE-----

--Kc4Mq0TylaEF4CMdXssDEiRzN6CbciXD6--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019