All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 8501] gunzip fails to uncompress files
Date: Wed, 02 Dec 2015 23:09:40 +0000	[thread overview]
Message-ID: <bug-8501-163-FLGSH7rMqn@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-8501-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=8501

Peter Korsgaard <jacmet@uclibc.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #3 from Peter Korsgaard <jacmet@uclibc.org> ---
Fixed in git and will be part of 2015.11.1, thanks.

commit 63fdab6b4fcc860abd8dbc8342c7b01643a37e1a
Author: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Date:   Tue Dec 1 21:30:29 2015 +0100

    busybox: add another upstream patch to fix (g)unzip

    0002-unzip.patch was added in 69516e0 to fix a segmentation fault in the
    gunzip applet.  However, it introduced a new issue that made the unzipping
    of some files fail.

    Add an upstream patch that fixes this new issue.

    Fixes #8501.

    Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
    Cc: Jason Rush <rush0033@hotmail.com>
    Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2015-12-02 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 19:32 [Buildroot] [Bug 8501] New: gunzip fails to uncompress files bugzilla at busybox.net
2015-12-01 20:21 ` [Buildroot] [Bug 8501] " bugzilla at busybox.net
2015-12-01 22:16 ` bugzilla at busybox.net
2015-12-02 23:09 ` bugzilla at busybox.net [this message]

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=bug-8501-163-FLGSH7rMqn@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.