X-Spam-Check-By: sourceware.org
Message-ID: <469F9964.28152CFB@dessent.net>
Date: Thu, 19 Jul 2007 10:03:32 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Unix tar file with colons in archived file names
References: <11692093 DOT post AT talk DOT nabble DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

gmoney3138 wrote:

> When the cygwin tar recognizes this, due to Windows restrictions, the output
> file is not properly extracted.  I Googled around and found options for

Use a managed mount or "--transform s,:,_,g".

I'm not sure what this --force-file you mention is but it's not a valid
tar option.  --force-local might have been what you were looking for,
however the purpose of that is for overriding the meaning of colon when
specifying the name of the input file to read, not for dealing with
filenames inside a tarball that contain a colon, so it's irrelevant to
this case.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/