From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mhw@netris.org, Nicolas Petton <nicolas@petton.fr>, emacs-devel@gnu.org
Subject: Re: emacs-24.5-rc3.tar.xz modified in place
Date: Fri, 10 Apr 2015 11:50:45 +0200 [thread overview]
Message-ID: <87r3rsgvm2.fsf@igel.home> (raw)
In-Reply-To: <83h9sov30b.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Apr 2015 10:47:16 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Nicolas Petton <nicolas@petton.fr>
>> Date: Fri, 10 Apr 2015 00:36:19 +0200
>> Cc: emacs-devel@gnu.org
>>
>> > I've downloaded emacs-24.5-rc3.tar.xz and the corresponding .sig from
>> > alpha.gnu.org twice, and they are different. Both are signed by Nicolas
>> > Petton's public key (7C207910). See below for the differences.
>> >
>> > It's bad practice to modify tarball releases without changing the
>> > version number. Please don't do it. Among other things, it breaks
>> > distributions such as GNU Guix that include cryptographic hashes of all
>> > source tarballs.
>>
>> I'm sorry, that's my fault.
>
> No, it isn't. There's no fault to begin with.
Yes, there is. If a tarball needs to be replaced for whatever reason,
it *must* get a new file name.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2015-04-10 9:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 21:27 emacs-24.5-rc3.tar.xz modified in place Mark H Weaver
2015-04-09 22:36 ` Nicolas Petton
2015-04-10 7:47 ` Eli Zaretskii
2015-04-10 9:50 ` Andreas Schwab [this message]
2015-04-10 7:42 ` Eli Zaretskii
2015-04-10 9:21 ` Ulrich Mueller
2015-04-10 10:22 ` Eli Zaretskii
2015-04-10 11:19 ` Ulrich Mueller
2015-04-10 12:00 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3rsgvm2.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mhw@netris.org \
--cc=nicolas@petton.fr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).