From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] schifra: fix build of examples and add hash
Date: Fri, 31 Oct 2014 12:12:57 +0100 [thread overview]
Message-ID: <20141031121257.540f4ba3@free-electrons.com> (raw)
In-Reply-To: <87egto8pv7.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Fri, 31 Oct 2014 12:01:32 +0100, Peter Korsgaard wrote:
> It seems like it changed AGAIN:
>
> http://autobuild.buildroot.net/results/b62/b624c7f9fd7b431e97599e4b9b5e2a87fcb1a0a9/build-end.log
>
> This is not workable. Nobody will be able to seriously use schifra in a
> project like this, and E.G. 2014.08 and earlier releases are broken.
Are we sure it changed again? Isn't the build error above caused by the
fact that the tarball in the cache was wrong, and now that we've added
the hash, the individual autobuilder instances are progressively
realizing that the tarball they have in their cache is wrong.
> What do we do?
>
> - Get upstream to add a version number to the tarball and bump the
> version whenever it changes
>
> - Put a known good version on sources.buildroot.net and use that
>
> - Drop the package
I personally don't care about schifra. It was added back in August 2012
by Simon Dawson, but unfortunately Simon is no longer contributing to
Buildroot.
Maybe we should first report the issue upstream?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-31 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 10:17 [Buildroot] [PATCH v2] schifra: fix build of examples and add hash Arnout Vandecappelle
2014-10-28 17:55 ` Thomas Petazzoni
2014-10-31 11:01 ` Peter Korsgaard
2014-10-31 11:12 ` Thomas Petazzoni [this message]
2014-10-31 13:36 ` Peter Korsgaard
2014-10-31 14:01 ` Thomas Petazzoni
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=20141031121257.540f4ba3@free-electrons.com \
--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