From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gustavo Zacarias Date: Tue, 30 Jun 2015 09:28:57 -0300 Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-06-29 In-Reply-To: <20150630142515.636aa6f9@free-electrons.com> References: <20150630063014.44429100A75@stock.ovh.net> <20150630140738.526d72b8@free-electrons.com> <559288ED.3010704@free-electrons.com> <20150630142515.636aa6f9@free-electrons.com> Message-ID: <55928B89.5040802@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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.