Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10511] Packages get downloaded uncompressed with wget
Date: Wed, 10 Jan 2018 20:57:28 +0000	[thread overview]
Message-ID: <bug-10511-163-piIXKey0iL@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10511-163@https.bugs.busybox.net/>

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

--- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---
Thanks for the investigation. This problem has been fixed/worked-around
upstream by commit
http://git.savannah.gnu.org/cgit/wget.git/commit/?id=047746eb765d212cbf05afac16f4bd73257d8186
which ensures that .gz and .tgz files don't get uncompressed.

However wget 1.19.2 remains affected.

Options:

 - Ignore the problem, and leave users of 1.19.2 affected by the problem.

 - Bail out if wget 1.19.2 is used, and leave it to the user to use a suitable
wget version

 - Detect if wget >= 1.19.2, and pass --compression=none

Thoughts?

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

  parent reply	other threads:[~2018-01-10 20:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 14:37 [Buildroot] [Bug 10511] New: Packages get downloaded uncompressed with wget bugzilla at busybox.net
2017-11-21 20:12 ` [Buildroot] [Bug 10511] " bugzilla at busybox.net
2017-12-18 14:03 ` bugzilla at busybox.net
2018-01-10 20:57 ` bugzilla at busybox.net [this message]
2018-01-10 21:17 ` bugzilla at busybox.net
2018-04-02 15:39 ` bugzilla at busybox.net
2018-04-02 16:17 ` bugzilla at busybox.net

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-10511-163-piIXKey0iL@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox