From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin64, 'unzip -d' misbehaviour vs. Cygwin32
Date: Tue, 30 Sep 2014 09:06:00 -0000 [thread overview]
Message-ID: <542A5D5E.50701@gmail.com> (raw)
In-Reply-To: <542A4F29.80204@mwg.dp.ua>
On 30/09/2014 08:35, Wladimir Mutel wrote:
> Dear all,
>
> I have a .zip archive on a different NTFS filesystem than Cygwin64 TMP
> folder (say, .zip on I: and TMP on C:). I create a temporary folder
> by 'mktemp -d' and then try to unpack .zip archive into that folder :
> unzip -d $folder $archive
> I notice that files are unpacked into I:\TMP\ folder instead of
> C:\Cygwin64\tmp\ (unzip recreates temporary subfolder with same name
> inside I:\TMP\, while initial subfolder under c:\cygwin64\tmp\
> remains empty)
> Trying to work around this problem, I do this :
> p=$(pwd)/$archive # archive is relative path under /cygdrive/i/ ,
> # so I construct abs.path
> ( cd $folder
> unzip $p ) # in subshell to keep current pwd unchanged
> Then I get a message like :
> unzip: cannot find either /cygdrive/i/path/archive.zip or
> /cygdrive/i/path/archive.zip.zip.
>
> Even more, unzip -v /cygdrive/i/path/archive.zip invariably fails
> in this way under Cygwin64. What I see is that unzip accepts only
> relative paths for archive files. And that it improperly handles
> specified unpack directory (-d).
>
> No such problems are observable under Cygwin32. unzip works exactly
> as specified with both absolute and relative paths, as well as with
> unpack folder on different filesystem from .zip archive.
>
> Please try to reproduce my findings and fix them on Cygwin64 side
> or tell me how could I fix them myself (if it is my personal problem).
>
> Thanks in advance for your help.
>
works fine for me on any relative or absolute destination
$ unzip software/windows_utilities/usb/usbdeview-x64.zip -d
/cygdrive/c/temp/pippo
Archive: software/windows_utilities/usb/usbdeview-x64.zip
inflating: /cygdrive/c/temp/pippo/USBDeview.exe
inflating: /cygdrive/c/temp/pippo/USBDeview.chm
inflating: /cygdrive/c/temp/pippo/readme.txt
--
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
next prev parent reply other threads:[~2014-09-30 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 7:32 Wladimir Mutel
2014-09-30 9:06 ` Marco Atzeri [this message]
2014-09-30 11:49 ` Wladimir Mutel
[not found] <542A6B85.5030700@mwg.dp.ua>
2014-09-30 11:39 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=542A5D5E.50701@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).