From: Steven Rostedt <rostedt@goodmis.org>
To: "Dominic Sacré" <dominic.sacre@gmx.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users@vger.kernel.org
Subject: Re: Changing checksums of RT patches
Date: Tue, 14 Feb 2017 13:57:38 -0500 [thread overview]
Message-ID: <20170214135738.366f21e5@gandalf.local.home> (raw)
In-Reply-To: <ea5ff7b5-77d2-754d-b7c2-6c9f9c3d7b90@gmx.de>
On Tue, 14 Feb 2017 19:42:35 +0100
Dominic Sacré <dominic.sacre@gmx.de> wrote:
> Could this be the cause of your issue?
>
> I think so. Looking at the current contents of rt/4.1, I see that
> patch-4.1.38-rt45.patch.gz and older/patch-4.1.38-rt45.patch.gz have
> different sha256 hashes. I would have expected them to be copies of the
> exact same file, so I guess the question is why they're different in the
> first place.
It's the way kernel.org does the updates. I upload a .xz file and a
signed gpg file of the uncompressed image. kernel.org creates the gz
file from the uncompressed version. As I upload it twice, kernel.org
does two gzips of the uncompressed file. I'm guessing that there's a
timestamp that gets used as well, making both gzipped files different,
even though what they contain are the same.
I may need to change my workflow to simply delete the file in the
current directory than to move it. Although, I had better make sure
that there's a copy in the older directory first. Maybe I'll change my
tool to download the older and current versions, uncompress them, make
sure they are the same, and if they are, remove the current version,
else, move the current version on the older one.
-- Steve
next prev parent reply other threads:[~2017-02-14 18:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 9:09 Changing checksums of RT patches Dominic Sacré
2017-02-10 18:54 ` Sebastian Andrzej Siewior
2017-02-13 22:56 ` Dominic Sacré
2017-02-13 23:15 ` Dominic Sacré
2017-02-14 14:18 ` Steven Rostedt
2017-02-14 18:42 ` Dominic Sacré
2017-02-14 18:57 ` Steven Rostedt [this message]
2017-02-15 13:38 ` Dominic Sacré
2017-02-15 13:52 ` Sebastian Andrzej Siewior
2017-02-15 14:50 ` Dominic Sacré
2017-02-15 17:15 ` Sebastian Andrzej Siewior
2017-02-28 18:03 ` Thomas Gleixner
2017-02-28 18:30 ` Steven Rostedt
2017-03-10 23:13 ` Dominic Sacré
2017-03-10 23:19 ` Steven Rostedt
2017-03-11 2:27 ` Julia Cartwright
2017-03-11 3:21 ` Steven Rostedt
2017-03-11 11:14 ` Dominic Sacré
2017-03-11 13:42 ` Steven Rostedt
2017-03-11 9:45 ` Thomas Gleixner
2017-03-11 13:43 ` Steven Rostedt
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=20170214135738.366f21e5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=dominic.sacre@gmx.de \
--cc=linux-rt-users@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).