From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: unzip, find broken by auto handling of .exe file extension
Date: Fri, 02 Sep 2016 18:40:00 -0000 [thread overview]
Message-ID: <9c8c94a1-2df6-354e-12ed-55d9d19670ca@gmail.com> (raw)
In-Reply-To: <FDF650EB6B144CDE9983FC655ABFF5FA@skywavemobile.com>
On 9/1/2016 12:00 PM, Stephen Anderson wrote:
> I am in the process of importing zip archive contents into an SVN repo
> and have encountered problems when unzip-6.00 expands an archive
> containing an executable file in a directory that contains a
> subdirectory with the same base name as the executable. If the
> executable happens to occur after the subdirectory, unzip works, however
> if the executable is first, unzip fails with the error:
>
> checkdir error: testAutoExeExpansion/test exists but is not directory
> unable to process testAutoExeExpansion/test/.
>
How can a directory and a file of the same name exist? It can't and
because Cygwin stats the foo.exe to be foo then that is the filename
comparison.
> Luckily I am able to use 7z extract, which does not exhibit the unzip
> problem and even allows me to exclude the culprit subdirectory (which
> luckily contains nothing I am interested in).
>
Unzip has the -x option to exclude archive items.
> In the process of trying to solve this problem, I used find-4.6.0 to try
> and delete the subdirectory after extracting with 7z to no avail.
> Even preceding the path match with a type directory spec find gets
> confused (so did the svn commit BTW).
>
Did you trail the name with / for the delete? The rmdir command should
work. You would use the -exec option with find to execute rmdir rather
than the delete function of find.
> The enclosed ruby unit test reproduces the minimal circumstances of the
> issue for both unzip and find.
> It is likely that this is a common problem somewhere in the bowels of
> file 'globbing' in cygwin only.
>
Yes and one that allows the stat of foo.exe by foo only so that it can
launch the application. It has existed since the beginning of Cygwin
and I doubt it will ever be resolved without requiring the full file
name for executables.
--
cyg Simple
--
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:[~2016-09-02 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 16:00 Stephen Anderson
2016-09-02 18:40 ` cyg Simple [this message]
2016-09-02 20:20 ` Stephen Anderson
2016-09-09 13:18 ` Stephen Anderson
2016-09-09 13:59 ` Nellis, Kenneth
2016-09-12 20:37 ` Stephen Anderson
2016-09-12 23:30 ` Marco Atzeri
2016-09-12 23:41 ` Stephen Anderson
2016-09-13 1:35 ` Andy Hall
2016-09-13 8:00 ` 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=9c8c94a1-2df6-354e-12ed-55d9d19670ca@gmail.com \
--to=cygsimple@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).