From: Eric Wong <e@80x24.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jeff King" <peff@peff.net>, "René Scharfe" <l.s.r@web.de>,
git@vger.kernel.org,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH] test-lib: stricter unzip(1) check
Date: Mon, 18 Jul 2016 21:19:51 +0000 [thread overview]
Message-ID: <20160718211951.GA62657@plume> (raw)
In-Reply-To: <xmqqk2giitrn.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> wrote:
> Eric Wong <e@80x24.org> writes:
> > Junio C Hamano <gitster@pobox.com> wrote:
> >> +test_lazy_prereq UNZIP_AUTOTEXT '
> >> + (
> >> + mkdir unzip-autotext &&
> >> + cd unzip-autotext
> >> + "$GIT_UNZIP" -a "$TEST_DIRECTORY"/t5003/infozip-text.zip &&
> >> + test -f text
> >> + )
> >
> > /usr/bin/unzip actually takes -a on FreeBSD, just not in the
> > same way the Info-ZIP version does, so I suspect "test -f"
> > here is not enough.
>
> Hmph. So it only and always does "CRLF -> LF", while Info-ZIP
> version does something like autocrlf?
No, it does CRLF -> LF based on the absence of non-ASCII
characters and ignoring metadata set in the zipfile.
The unzip manpage states:
Normally, the -a option should only affect files which are
marked as text files in the zipfile's central directory. Since
the archive(3) library reads zipfiles sequentially, and does
not use the central directory, that information is not available
to the unzip utility. Instead, the unzip utility will assume
that a file is a text file if no non-ASCII characters are
present within the first block of data decompressed for that
file. If non-ASCII characters appear in subsequent blocks of
data, a warning will be issued.
https://www.freebsd.org/cgi/man.cgi?query=unzip&sektion=1&manpath=FreeBSD+10.3-RELEASE
> Heh. It was created like so:
>
> $ printf 'text\r\n' >text && zip -ll infozip-text.zip text
> $ zipinfo infozip-text.zip text
> -rw-r----- 3.0 unx 5 tx stor 16-Jul-18 13:12 text
>
Thanks, but I think the test file is too small. I tried
setting up a test to store the text file as binary in the
zip to check for inadvertant CRLF conversions:
printf 'text\r\n' >binary && zip -B infozip-binary.zip binary
But zip -B/--binary only works on VM/CMS and MVS...
So I'm inclined to go with Dscho's patch.
(apologies for messing up René's name in my previous email;
on my new FreeBSD setup: mutt displays it fine, as does vim when
taking it from .mailmap, but something gets lost when mutt
populates the file for vim. Perhaps some Debian patch didn't
make it upstream...)
next prev parent reply other threads:[~2016-07-18 21:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 6:44 [PATCH] test-lib: stricter unzip(1) check Eric Wong
2016-07-18 13:04 ` Jeff King
2016-07-18 13:52 ` Johannes Schindelin
2016-07-18 18:20 ` Junio C Hamano
2016-07-18 18:56 ` Jeff King
2016-07-18 19:17 ` Junio C Hamano
2016-07-19 11:27 ` Johannes Schindelin
2016-07-19 17:26 ` Junio C Hamano
2016-07-18 19:43 ` Junio C Hamano
2016-07-18 20:03 ` Eric Wong
2016-07-18 20:19 ` Junio C Hamano
2016-07-18 21:19 ` Eric Wong [this message]
2016-07-18 21:27 ` Junio C Hamano
2016-07-18 23:41 ` Jeff King
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=20160718211951.GA62657@plume \
--to=e@80x24.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=l.s.r@web.de \
--cc=peff@peff.net \
/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 NNTP newsgroup(s).