From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mailsrv.cs.umass.edu (mailsrv.cs.umass.edu [128.119.240.136]) by sourceware.org (Postfix) with ESMTPS id 949CA385AE5A for ; Thu, 16 Jun 2022 15:50:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 949CA385AE5A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=cs.umass.edu Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=cs.umass.edu Received: from [192.168.50.148] (c-24-62-201-179.hsd1.ma.comcast.net [24.62.201.179]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id 595ED4029625; Thu, 16 Jun 2022 11:50:23 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: unzip failure with files that contain colons To: Takashi Yano , cygwin@cygwin.com References: <20220615183007.7xchz44wwbx2gnio@lucy.dinwoodie.org> <20220617002939.65c772fc3504f992b6fcf4d9@nifty.ne.jp> From: Eliot Moss Message-ID: <9093a683-0215-3835-42f5-a8f82975c29f@cs.umass.edu> Date: Thu, 16 Jun 2022 11:50:23 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: <20220617002939.65c772fc3504f992b6fcf4d9@nifty.ne.jp> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, NICE_REPLY_A, 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2022 15:50:28 -0000 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  x1z  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? Regards - Eliot