public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-apps@cygwin.com
Subject: [ITA] unzip-6.0-18
Date: Thu, 16 Jun 2022 18:00:36 +0900	[thread overview]
Message-ID: <20220616180036.6c02350fd35bcfbf11c2f4c9@nifty.ne.jp> (raw)

Hi,

I would like to take over the maintenance of unzip package, which is
currently orphaned. I have already prepared an updated unzip package
as follows.

What's new:
------------------------------------------------------------------
* Apply several security patches. (imported from fedora)
* Add -O and -I options which specifies charset of archive file.
  (imported from fedora)
* Allow '"', '*', ':', '?', '|' '<' and '>' chars in file name,
  which are curretly replaced with '_' when extracting.


Package Files:
------------------------------------------------------------------
D=https://tyan0.yr32.net/cygwin
${D}/x86_64/release/unzip/unzip-6.0-18-src.tar.xz
${D}/x86_64/release/unzip/unzip-6.0-18-src.hint
${D}/x86_64/release/unzip/unzip-6.0-18.tar.xz
${D}/x86_64/release/unzip/unzip-6.0-18.hint
${D}/x86_64/release/unzip/unzip-debuginfo/unzip-debuginfo-6.0-18.hint
${D}/x86_64/release/unzip/unzip-debuginfo/unzip-debuginfo-6.0-18.tar.xz
${D}/x86/release/unzip/unzip-6.0-18-src.tar.xz
${D}/x86/release/unzip/unzip-6.0-18-src.hint
${D}/x86/release/unzip/unzip-6.0-18.tar.xz
${D}/x86/release/unzip/unzip-6.0-18.hint
${D}/x86/release/unzip/unzip-debuginfo/unzip-debuginfo-6.0-18.hint
${D}/x86/release/unzip/unzip-debuginfo/unzip-debuginfo-6.0-18.tar.xz

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

             reply	other threads:[~2022-06-16  9:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16  9:00 Takashi Yano [this message]
2022-06-16 13:43 ` Ken Brown

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=20220616180036.6c02350fd35bcfbf11c2f4c9@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin-apps@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).