From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29457@debbugs.gnu.org, "Clément Lassieur" <clement@lassieur.org>
Subject: [bug#29457] [PATCH] gnu: emacs-org-contrib: Fix sha256 checksum due to emacs-org update.
Date: Sun, 26 Nov 2017 17:35:21 -0500 [thread overview]
Message-ID: <20171126223521.GA17517@jasmine.lan> (raw)
In-Reply-To: <87wp2cu1o2.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Sun, Nov 26, 2017 at 11:15:41PM +0100, Ludovic Courtès wrote:
> Clément Lassieur <clement@lassieur.org> skribis:
>
> > * gnu/packages/emacs.scm (emacs-org-contrib)[source]: Fix sha256 checksum.
> > ---
> > gnu/packages/emacs.scm | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/gnu/packages/emacs.scm b/gnu/packages/emacs.scm
> > index acd6ec30a..7e16c8b4b 100644
> > --- a/gnu/packages/emacs.scm
> > +++ b/gnu/packages/emacs.scm
> > @@ -4230,7 +4230,7 @@ reproducible research.")
> > (package-version emacs-org) ".tar"))
> > (sha256
> > (base32
> > - "0xy2xrndlhs4kyvh6mmv24dnh3fn5p63d2gaimnrypf1p8znwzh4"))))
> > + "071vqv6hdyjp85ap39930782ks07ypjzch81r8kax3ybwfrf0chx"))))
>
> Was the SHA256 simply erroneous, or was the file modified in-place
> upstream?
>
> It’s a good idea to investigate a bit in such cases IMO.
I assumed this was a case where a package FOO inherits another package
BAR's version, and BAR was updated, leaving FOO with a broken source.
Otherwise, yes, all hash mismatches should be investigated and reported
upstream.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-26 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 17:07 [bug#29457] [PATCH] gnu: emacs-org-contrib: Fix sha256 checksum due to emacs-org update Clément Lassieur
2017-11-26 20:51 ` Leo Famulari
2017-11-26 22:15 ` Ludovic Courtès
2017-11-26 22:35 ` Leo Famulari [this message]
2017-11-28 2:43 ` Clément Lassieur
2017-11-28 17:00 ` Nicolas Goaziou
2017-12-10 14:33 ` Clément Lassieur
2017-12-19 16:36 ` Leo Famulari
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171126223521.GA17517@jasmine.lan \
--to=leo@famulari.name \
--cc=29457@debbugs.gnu.org \
--cc=clement@lassieur.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.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).