From: Paul Barker <pbarker@toganlabs.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: netdev@vger.kernel.org
Subject: Re: ethtool-4.8.tar.gz checksum change
Date: Mon, 10 Apr 2017 10:13:21 +0100 [thread overview]
Message-ID: <20170410101321.12a1b087@host0.betafive.co.uk> (raw)
In-Reply-To: <20170405140003.GB18361@tuxdriver.com>
On Wed, 5 Apr 2017 10:00:04 -0400
"John W. Linville" <linville@tuxdriver.com> wrote:
> On Mon, Apr 03, 2017 at 11:25:54AM +0100, Paul Barker wrote:
> > Hi,
> >
> > It looks like the checksum of the following file has changed recently:
> > https://www.kernel.org/pub/software/network/ethtool/ethtool-4.8.tar.gz
> >
> > Original checksum from around 23/10/2016:
> > md5sum = 28c4a4d85c33f573c49ff6d81ec094fd
> > sha256sum = 1bd82ebe3d41de1b7b0d8f4fb18a8e8466fba934c952bc5c5002836ffa8bb606
> >
> > Current checksum:
> > md5sum = 992eab97607c64b7848edfd37f23da22
> > sha256sum = c8ea20b8d85898377ec130066008f9241ebcdd95ac85dbcc2d50b32fe2e2f934
> >
> > Is this change intentional?
> >
> > I've spotted this when doing an OpenEmbedded build, it's rejecting the
> > ethtool-4.8.tar.gz file as corrupted since the checksums do not match those
> > originally recorded.
> >
> > Thanks,
> > Paul Barker
>
> Yes, the .tar.gz file got regenerated locally as I was tinkering with
> the release scripts that I inherited from the former ethtool maintainer,
> and the regenerated .tar.gz file got uploaded. The newly updated one
> is properly signed and the signature is there to verify. (Note that
> the signature is against the .tar file and not the .tar.gz file.)
>
> I downloaded the file from the website and verified against the
> matching version of the git tree locally as well. If you have any idea
> as to who is in charge of the OpenEmbedded build and can correct/remove
> this complaint, then please let me know and/or have them contact me.
> (Ditto for Yocto builds...)
>
> Thanks,
>
> John
We've updated things in OpenEmbedded now. Thanks for the confirmation.
Cheers,
Paul
prev parent reply other threads:[~2017-04-10 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 10:25 ethtool-4.8.tar.gz checksum change Paul Barker
2017-04-05 14:00 ` John W. Linville
2017-04-10 9:13 ` Paul Barker [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=20170410101321.12a1b087@host0.betafive.co.uk \
--to=pbarker@toganlabs.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).