From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] change package tarball compression to xz whenever possible
Date: Mon, 9 Sep 2013 09:24:25 +0200 [thread overview]
Message-ID: <20130909092425.6a16e694@skate> (raw)
In-Reply-To: <1378448055-3056-1-git-send-email-jerzy.grzegorek@trzebnica.net>
Peter,
On Fri, 6 Sep 2013 08:14:15 +0200, Jerzy Grzegorek wrote:
> Signed-off-by: Jerzy Grzegorek <jerzy.grzegorek@trzebnica.net>
I've seen you committed this patch, but unfortunately it breaks all
Github downloads. It assumes Github provides a .tar.xz file, but it
doesn't: even if you request a .tar.xz file from Github, it gives you a
gzip compressed file:
$ wget http://github.com/gandro/input-event-daemon/tarball/v0.1.3/input-event-daemon-v0.1.3.tar.xz
[...]
$ file input-event-daemon-v0.1.3.tar.xz
input-event-daemon-v0.1.3.tar.xz: gzip compressed data, from Unix
This is causing a huge number of build failures in the autobuilders.
For example, cpuload:
http://autobuild.buildroot.org/results/bcd/bcdf4bdca4d5f8ffc9c84afcadf1b057fc03e009/build-end.log.
So I believe this patch should be reverted, or at least the parts
affecting Github downloads.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-09 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 6:14 [Buildroot] [PATCH v3 1/1] change package tarball compression to xz whenever possible Jerzy Grzegorek
2013-09-08 20:45 ` Peter Korsgaard
2013-09-09 7:24 ` Thomas Petazzoni [this message]
2013-09-09 9:33 ` Peter Korsgaard
2013-09-09 12:00 ` Jerzy Grzegorek
2013-09-09 14:10 ` Jerzy Grzegorek
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=20130909092425.6a16e694@skate \
--to=thomas.petazzoni@free-electrons.com \
--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