From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder news
Date: Sun, 11 May 2014 22:37:35 +0200 [thread overview]
Message-ID: <536FDF8F.3040704@mind.be> (raw)
In-Reply-To: <20140511182949.55e5e115@free-electrons.com>
On 11/05/14 18:29, Thomas Petazzoni wrote:
> Dear Arnout Vandecappelle,
>
> On Sat, 10 May 2014 22:28:27 +0200, Arnout Vandecappelle wrote:
>
>> Is it possible that you installed new binaries with the same name but a
>> different ctng configuration? That's a bit annoying because it breaks
>> reproducibility... It's OK to remove the old toolchains, but it would be good if
>> the new ones would have a different name.
>
> No, it is not possible. The new toolchains have a different tarball
> name, and all the tarballs from the previous ctng configurations have
> been kept. So all builds made on the Free Electrons build server should
> be fully reproducible.
>
> Have you found any specific issue?
No, just that when I tried one of the new toolchains it didn't download because
it was already there. But I guess I must have forgotten that I had downloaded it
before, then.
Sorry for the noise.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-05-11 20:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 20:36 [Buildroot] Autobuilder news Thomas Petazzoni
2014-05-04 21:32 ` Luca Ceresoli
2014-05-10 20:28 ` Arnout Vandecappelle
2014-05-11 16:07 ` Thomas Petazzoni
2014-05-11 16:29 ` Thomas Petazzoni
2014-05-11 20:37 ` Arnout Vandecappelle [this message]
2014-05-11 21:14 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2014-08-29 21:26 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=536FDF8F.3040704@mind.be \
--to=arnout@mind.be \
--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