From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] support/download/wrapper expects file output in temp directory but support/wrapper/git produces output.gz
Date: Wed, 6 Aug 2014 18:55:17 +0200 [thread overview]
Message-ID: <CAAXf6LU+mrkLV=mm2ifd+i0Oxn8EQjEhbmg_nirLygGJhRrMjA@mail.gmail.com> (raw)
In-Reply-To: <20140806162934.GB3891@free.fr>
On Wed, Aug 6, 2014 at 6:29 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> Graham, All,
>
> On 2014-08-06 16:29 +0100, Graham Newton spake thusly:
>> Running support/download/wrapper git fails because the final instruction of
>> support/download/git gzips the output file creating output.gz which wrapper
>> isn't expecting.
>
> Doh... I wonder how I could let this slip through... :-(
I also should have caught this in my testing. I now understand why
this happened: sources.buildroot.net also contains the tar file of the
package I tried in my testing, and I did not actually verify the build
output. Since the package was downloaded and the contents looked ok, I
assumed the git download wrapper was fine.
Very bad testing on my part, my apologies!
Best regards,
Thomas
prev parent reply other threads:[~2014-08-06 16:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 22:19 [Buildroot] [git commit] arch: pass cpu option instead of tune option on ARM Thomas Petazzoni
2014-01-23 15:31 ` Jonas Jensen
2014-01-23 18:15 ` Yann E. MORIN
2014-08-04 14:45 ` Thomas De Schampheleire
2014-08-06 15:29 ` [Buildroot] support/download/wrapper expects file output in temp directory but support/wrapper/git produces output.gz Graham Newton
2014-08-06 16:29 ` Yann E. MORIN
2014-08-06 16:55 ` Thomas De Schampheleire [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='CAAXf6LU+mrkLV=mm2ifd+i0Oxn8EQjEhbmg_nirLygGJhRrMjA@mail.gmail.com' \
--to=patrickdepinguin@gmail.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 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.