From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.131]) by sourceware.org (Postfix) with ESMTPS id B82EA3858282 for ; Thu, 16 Jun 2022 04:22:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B82EA3858282 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=towo.net Authentication-Results: sourceware.org; spf=none smtp.mailfrom=towo.net Received: from [192.168.178.72] ([91.65.247.133]) by mrelayeu.kundenserver.de (mreue010 [212.227.15.167]) with ESMTPSA (Nemesis) id 1MCKSA-1nsJNH2h6I-009Lnd for ; Thu, 16 Jun 2022 06:22:37 +0200 Message-ID: Date: Thu, 16 Jun 2022 06:22:38 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: unzip failure with files that contain colons To: cygwin@cygwin.com References: <20220615183007.7xchz44wwbx2gnio@lucy.dinwoodie.org> From: Thomas Wolff In-Reply-To: <20220615183007.7xchz44wwbx2gnio@lucy.dinwoodie.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K1:J/DSVpOlShmwMi3uhtNc3t2QJemCH5NEX2olTIGat4HG2V23xtV WUITxZQz3iKaAwWn5jcc2VRFX+Xe8hT2fn/Rqilb3zvtJKtJlKkd3B0Br7orWWdRz34DZ8C pGtYKQ+hfmSJee2r1VP7QTjC9vc6Qgn2ySU/3ElGqp+GXiCy32PcQgGAKkE/9pzD5VXR4oE 2gsuEgvPRf27myGuj6kDg== X-UI-Out-Filterresults: notjunk:1;V03:K0:fY9l4JIh74A=:qoUm0bK83ZIN0/g5GLKB3c 987RpTW3NGS3+wDrymvF9RPQO0m6Q+1Kh1qGDjnHisCcHSHSn4mYdY5IUbSQcESI8HkCy89RJ Q6jkKfoX6TotbHS0mCcEMw2jgH6FdT6ODEjIubR8l9PtvJwWO8JbgbeTZOY8aiuPeboTWoxbO flRb0KKw+Inh6LirDU2jzXCNROMnf1APNxd/whE++Zt9ad7YkzlAGAnS7DyYDRG4Bxdtj9J+i CnWLD2QNiiz4Jw2bQViQUH5tUdETnXLtoGZItGpxRHK/001VznyNnXwX0DII8YKMkjN28Idf1 PWyQ/8Eco/ts8W+V8rNNSXzSNAsOiFsaAH3YkV55iQ8g0Yh0rWB01FvnKqPp0wzaxszByKOTL VnyQbz2kVNvQ5wUsotsOHFuFJbxqXwIWBxX8JMhR3NcugduV23yl7I9CdAPYPelp2I8V9qSIw pty117cZirsZH3kuQRehwJQ08EWsjhoNrO9VdFhvY+jxVPfQ9UuJhFAm05/uNHaIfb9COB9v2 +yhLVpq8LHjngkdULnoFUgJHKF9a5+ryqeg1DfnwmXUWceLCzgZ3pnxrAdfboaW/vxYGadq6k B4pA6b2U2WzA+jqCCNkkRjO5dwtx6eIuVjEU//9xvQgEiPisRIZfSq8V7ABlGHmO4uJa5KVgg lkItLL9bi+jSR4mtiUmTQ1HD8IocJLVb2KgddymgALE/apxkCnL2pqCeERnHXjd+hB/Nf5GK7 Ryno2u9mYMd5IP7KPAjBxgO+O5vwtiBPIQEvyA== X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, 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 04:22:41 -0000 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 Someone should report upstream please. Thomas