Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-06-29
Date: Tue, 30 Jun 2015 09:28:57 -0300	[thread overview]
Message-ID: <55928B89.5040802@free-electrons.com> (raw)
In-Reply-To: <20150630142515.636aa6f9@free-electrons.com>



On 30/06/15 09:25, Thomas Petazzoni wrote:

>> I should have emailed about this earlier, i didn't miss the hash, in
>> fact it's perfectly fine, look at
>> http://download.pureftpd.org/pub/pure-ftpd/releases/distinfo
>> The md5 hash stated there matches my previous tarball and my previous
>> tarabll sha256, and the file timestamp predates the tarball... so
>> upstream pulled a switcharoo.
>> I'm ok with the revised hash since it matches the signature, but it
>> wasn't my fault :)
>
> Yes, I also suspected that upstream changed the tarball. I didn't meant
> to be offensive in any way about your work here, really just wanted to
> fix the problem, nothing more. I definitely trust you that the hash was
> correct at the time you sent the patch, and that upstream did crap.

No offense taken, don't worry, i just went with the forensics for my 
conclusion, it might help somebody else in the future.
Regards.

  reply	other threads:[~2015-06-30 12:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-06-29 Thomas Petazzoni
2015-06-30 12:07 ` Thomas Petazzoni
2015-06-30 12:12   ` Bartosz Golaszewski
2015-06-30 12:17   ` Gustavo Zacarias
2015-06-30 12:25     ` Thomas Petazzoni
2015-06-30 12:28       ` Gustavo Zacarias [this message]
2015-06-30 13:39   ` Romain Naour
2015-06-30 17:33     ` Alexey Brodkin
2015-07-01  8:48       ` Romain Naour
2015-06-30 17:45   ` Bernd Kuhls
2015-07-01  9:45   ` Alexey Brodkin
2015-07-06 13:56   ` Gustavo Zacarias
2015-07-06 19:33   ` Gustavo Zacarias
2015-07-07  7:11     ` 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=55928B89.5040802@free-electrons.com \
    --to=gustavo.zacarias@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