X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Lester Ingber Subject: Re: untarring symlinks with ../ fails randomly Date: Thu, 28 Apr 2011 03:49:16 +0000 (UTC) Lines: 21 Message-ID: References: <20110424121145 DOT GB30696 AT calimero DOT vinschen DOT de> <20110426074325 DOT GP3324 AT calimero DOT vinschen DOT de> <20110426152226 DOT GA22801 AT ednor DOT casa DOT cgf DOT cx> <20110426155346 DOT GA19578 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Dan Grayson math.uiuc.edu> writes: > > Here is a patch to tar that fixes the problem by using mtime instead of ctime. > Yes, it's not a problem with cygwin or tar, but I see no way for users to > figure out, under Windows, which processes are changing the status of their > files. > > diff -ur tar-1.25-copy/src/extract.c tar-1.25/src/extract.c > --- tar-1.25-copy/src/extract.c 2010-11-01 15:34:59.000000000 -0500 > +++ tar-1.25/src/extract.c 2011-04-27 09:12:58.941555800 -0500 ... > I ran your patch on tar-1.26 and it compiled just fine. With the new tar I have no tar/untar problems on two Win7 Ult x64 PCs running up to date Cygwins. Thanks. Lester -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple