* Re: Cygwin64, 'unzip -d' misbehaviour vs. Cygwin32
[not found] <542A6B85.5030700@mwg.dp.ua>
@ 2014-09-30 11:39 ` Marco Atzeri
0 siblings, 0 replies; 4+ messages in thread
From: Marco Atzeri @ 2014-09-30 11:39 UTC (permalink / raw)
To: cygwin
On 30/09/2014 10:36, Wladimir Mutel wrote:
> Dear Marco,
>
Bottom post only and stay on the mailing list, please.
> 1. please try to unpack .zip archive with full absolute path specified
> (i.e. starting from /cygdrive/N)
as mentioned, it makes no differences
$ unzip
/cygdrive/e/downloads/software/windows_utilities/usb/usbdeview-x64.zip
-d /cygdrive/c/temp/pippo
Archive:
/cygdrive/e/downloads/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
> 2. please try to unpack it into temporary directory generated by 'mktemp
> -d'
> their path start from /tmp and so require resolution through mount table.
$ mktemp -d
/tmp/tmp.vtQwN9a232
$ unzip
/cygdrive/e/downloads/software/windows_utilities/usb/usbdeview-x64.zip
-d /tmp/tmp.vtQwN9a232
Archive:
/cygdrive/e/downloads/software/windows_utilities/usb/usbdeview-x64.zip
inflating: /tmp/tmp.vtQwN9a232/USBDeview.exe
inflating: /tmp/tmp.vtQwN9a232/USBDeview.chm
inflating: /tmp/tmp.vtQwN9a232/readme.txt
> 3. it is not very clear from your example that your archive
> usbdeview-x64.zip is stored outside of /cygdrive/c/
both origin and destination are outside on cygwin tree.
>
>> works fine for me on any relative or absolute destination
Regards
Marco
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Cygwin64, 'unzip -d' misbehaviour vs. Cygwin32
2014-09-30 7:32 Wladimir Mutel
2014-09-30 9:06 ` Marco Atzeri
@ 2014-09-30 11:49 ` Wladimir Mutel
1 sibling, 0 replies; 4+ messages in thread
From: Wladimir Mutel @ 2014-09-30 11:49 UTC (permalink / raw)
To: cygwin
Dear all, please disregard this thread.
It was a false alarm because I did not have unzip installed under Cygwin64
and its shell found some stray unzip from Dell utilities in Windows path.
Sorry for disturbing you without grounds.
On Tue, Sep 30, 2014 at 09:35:21AM +0300, Wladimir Mutel wrote:
> Dear all,
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Cygwin64, 'unzip -d' misbehaviour vs. Cygwin32
2014-09-30 7:32 Wladimir Mutel
@ 2014-09-30 9:06 ` Marco Atzeri
2014-09-30 11:49 ` Wladimir Mutel
1 sibling, 0 replies; 4+ messages in thread
From: Marco Atzeri @ 2014-09-30 9:06 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Cygwin64, 'unzip -d' misbehaviour vs. Cygwin32
@ 2014-09-30 7:32 Wladimir Mutel
2014-09-30 9:06 ` Marco Atzeri
2014-09-30 11:49 ` Wladimir Mutel
0 siblings, 2 replies; 4+ messages in thread
From: Wladimir Mutel @ 2014-09-30 7:32 UTC (permalink / raw)
To: cygwin
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.
--
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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-09-30 11:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <542A6B85.5030700@mwg.dp.ua>
2014-09-30 11:39 ` Cygwin64, 'unzip -d' misbehaviour vs. Cygwin32 Marco Atzeri
2014-09-30 7:32 Wladimir Mutel
2014-09-30 9:06 ` Marco Atzeri
2014-09-30 11:49 ` Wladimir Mutel
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).