From: Ben Myers <bpm@sgi.com>
To: xfs@oss.sgi.com
Cc: Rich Johnston <rjohnston@sgi.com>, David Kaylor <dpkaylor@gmail.com>
Subject: Re: [ANNOUNCE] xfsdump v3.1.3
Date: Wed, 15 May 2013 16:51:37 -0500 [thread overview]
Message-ID: <20130515215137.GV29359@sgi.com> (raw)
In-Reply-To: <518AA3CE.9000702@sgi.com>
Hey,
On Wed, May 08, 2013 at 02:13:18PM -0500, Rich Johnston wrote:
> Version 3.1.3 of xfsdump has been released.
>
> The source code can be accessed via git using this URL:
>
> git://oss.sgi.com/xfs/cmds/xfsdump.git
>
> A gzipped-tar archive of the source code is available here:
>
> ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsdump-3.1.3.tar.gz
David Kaylor pointed out that the posted signature for this tarball
fails verification. I tracked this down to the fact that I ran 'make
deb' after running the release script but before posting the tarball.
'make deb' regenerated the tar.gz and gzip put an updated timestamp in
the header so the tarball no longer matched the signature. However the
contents of the tarballs are otherwise identical, so I've moved the old
.sig out of the way, signed the tarball that was posted, and uploaded
the new .sig.
It might be nice for 'make dist' to create an identical .tar.gz for
identical inputs. gzip can be told not to update it's timestamp with
the -n option, but our current method of generating the tarball relies
upon .gitcensus being created on each run and this is currently
$(_FORCE) and required for the 'make deb' target. I don't have a
solution at this time, so for the time being 'make dist' is creating
non-identical tarballs for identical inputs at each invocation.
Suggestions are welcome.
Thanks to David for his attention to detail.
Regards,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-05-15 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 19:13 [ANNOUNCE] xfsdump v3.1.3 Rich Johnston
2013-05-15 21:51 ` Ben Myers [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=20130515215137.GV29359@sgi.com \
--to=bpm@sgi.com \
--cc=dpkaylor@gmail.com \
--cc=rjohnston@sgi.com \
--cc=xfs@oss.sgi.com \
/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