X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org A91A63850205
Authentication-Results:	sourceware.org;
	dmarc=fail (p=none dis=none) header.from=nifty.ne.jp
Authentication-Results:	sourceware.org; spf=fail smtp.mailfrom=nifty.ne.jp
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-04.nifty.com 25GGieqT017311
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp;
	s=dec2015msa; t=1655397880;
	bh=p2LkqUDTE0ZQP7mp+q+fqy3GNyOttzjFT5KMI+PhvyM=;
	h=Date:From:To:Subject:In-Reply-To:References:From;
	b=xMGTdmiKT21cC9Qvdc0nbIC9q9Za6EnnFXqvP3ZTR5eGLRTrpIeQDzEiLD2Tcop6Q
	hBW0SEDpdiQ1+qyqT3r6v8ZzkMZtMogSrTtcGeeeO0Mt0AdmlvRQSJYjnWpKidLiBn
	Q9wBbU+5Kiod85zMG0PQ10JYOpwTKcTtC+PiC0aTHQoAnidKq4FTdNzt8lGsBhGpAO
	jFwbskrqI9YycabQEp39QybNG8tGN5n/8Fyp3vs0pcAEbSGmGDI2GuH47XquH7xwH5
	Fbkg96xujCsyqOpO5ArBawmJPhDQ4j8Hg3D2rCSZDkSLTcNpk74fJpiwPfiYF3/Kff
	R75sR+P6G6/kQ==
X-Nifty-SrcIP:	[119.150.44.95]
Date:	Fri, 17 Jun 2022 01:44:40 +0900
From:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
To:	cygwin AT cygwin DOT com
Subject:	Re: unzip failure with files that contain colons
Message-Id:	<20220617014440.695b55eaae270bb3b19f87c7@nifty.ne.jp>
In-Reply-To:	<9093a683-0215-3835-42f5-a8f82975c29f@cs.umass.edu>
References:	<20220615183007 DOT 7xchz44wwbx2gnio AT lucy DOT dinwoodie DOT org>
	<ba73b31b-be25-fe58-98de-11d8cad679cd AT towo DOT net>
	<20220617002939 DOT 65c772fc3504f992b6fcf4d9 AT nifty DOT ne DOT jp>
	<9093a683-0215-3835-42f5-a8f82975c29f AT cs DOT umass DOT edu>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-5.9 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
	SPF_HELO_NONE, SPF_PASS, TXREP,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>
X-MIME-Autoconverted:	from base64 to 8bit by delorie.com id 25GGjPch005153

On Thu, 16 Jun 2022 11:50:23 -0400
Eliot Moss wrote:
> On 6/16/2022 11:29 AM, Takashi Yano wrote:
> > On Thu, 16 Jun 2022 06:22:38 +0200
> > Thomas Wolff wrote:
> >> Am 15.06.2022 um 20:30 schrieb Adam Dinwoodie:
> >>> Cygwin generally handles filenames with colons just fine, by mapping the
> >>> character to some higher Unicode character and remapping on the fly.
> >>> However Cygwin's `unzip` appears to have a bug: when unzipping an
> >>> archive that contains a filename with a colon, it replaces the colon
> >>> with an underscore.
> >>>
> >>> cygcheck.out and simple test script attached; expected behaviour from
> >>> running `bash unzip-bug.sh` is that you get an empty file called `a:b`,
> >>> but on Cygwin you instead get an empty file called `a_b`.
> >> It's an explicit #ifdef __CYGWIN__ in upstream unzip, file unix/unix.c,
> >> which transforms a bunch of characters.
> >> If I uncomment most of them (except \), all unpack fine:
> >> x0:z  x1<z  x2>z  x3|z  x4"z  x5?z  x6*z
> > 
> > I have taken over the maintenance of unzip package, and
> > fix the problem in the updated unzip-6.0-18.
> > https://cygwin.com/pipermail/cygwin/2022-June/251653.html
> 
> Is colon used for ADS under Windows?  Could that be why one should
> be careful with it?

Cygwin replaces ':' (0x3A) in file name with U+F03A when creating
the file. See winsup/cygwin/path.cc and winsup/cygwin/strfuncs.cc.
Therefore, ':' can be safely used in file name without conflict.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

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

- Raw text -