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 10511] New: Packages get downloaded uncompressed with wget
Date: Tue, 21 Nov 2017 14:37:30 +0000	[thread overview]
Message-ID: <bug-10511-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 10511
           Summary: Packages get downloaded uncompressed with wget
           Product: buildroot
           Version: 2017.08
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: jean.parpaillon at free.fr
                CC: buildroot at uclibc.org
  Target Milestone: ---

Using buildroot with wget version 1.19.2 on Debian, through nerves toolchain.
(https://github.com/nerves-project/nerves_system_br)

When downloading otp (http://erlang.org/download/otp_src_20.1.tar.gz), wget
(through pkg-download.mk recipes) uncompress the data, resulting with an
gunzipe'd .tar.gz, hence md5 mismatch.

Downloading the package with 'wget --compress=none' fixed the problem, but may
depend on wget versions.

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

             reply	other threads:[~2017-11-21 14:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 14:37 bugzilla at busybox.net [this message]
2017-11-21 20:12 ` [Buildroot] [Bug 10511] Packages get downloaded uncompressed with wget bugzilla at busybox.net
2017-12-18 14:03 ` bugzilla at busybox.net
2018-01-10 20:57 ` bugzilla at busybox.net
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@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.