From: "Clément Lassieur" <clement@lassieur.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 29457@debbugs.gnu.org
Subject: [bug#29457] [PATCH] gnu: emacs-org-contrib: Fix sha256 checksum due to emacs-org update.
Date: Sun, 10 Dec 2017 15:33:08 +0100 [thread overview]
Message-ID: <87wp1utzyz.fsf@lassieur.org> (raw)
In-Reply-To: <87induqqwq.fsf@nicolasgoaziou.fr>
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Clément Lassieur <clement@lassieur.org> writes:
>
>> Leo Famulari <leo@famulari.name> writes:
>>> On Sun, Nov 26, 2017 at 11:15:41PM +0100, Ludovic Courtès wrote:
>>>>
>>>> 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.
>>
>> Exactly. I'll put a comment, as suggested by Leo, so that we don't
>> forget to update it anymore.
>
> But wouldn't it make more sense, in this case, to merge both packages
> and let "contrib" be an output for emacs-org?
Indeed, to me it makes sense, but Leo knows much more than me about
packages, so I cc'ed him.
next prev parent reply other threads:[~2017-12-10 14:34 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
2017-11-28 2:43 ` Clément Lassieur
2017-11-28 17:00 ` Nicolas Goaziou
2017-12-10 14:33 ` Clément Lassieur [this message]
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=87wp1utzyz.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=29457@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.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/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).