From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Fredrik Salomonsson <plattfot@posteo.net>, 57899@debbugs.gnu.org
Subject: bug#57899: emacs-jsonrpc hash mismatch
Date: Mon, 19 Sep 2022 23:38:08 +0200 [thread overview]
Message-ID: <87r1072gfz.fsf@jpoiret.xyz> (raw)
In-Reply-To: <874jx5wmd5.fsf@posteo.net>
Hi Frederik,
Fredrik Salomonsson <plattfot@posteo.net> writes:
> Not sure what is going on. Or what is the best approach forward.
>
> Any ideas what could be wrong?
I downloaded the derivation and original source from ci using `guix
substitute --substitute` and compared the old and new .tar files using
diffoscope. It seems the new one only has more recent timestamps, thus
leading to a different hash. Maybe ELPA regenerates their archives,
like GitHub tarballs? One more example why we should prefer git-fetch
instead.
Best,
--
Josselin Poiret
next prev parent reply other threads:[~2022-09-19 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 0:35 bug#57899: emacs-jsonrpc hash mismatch Fredrik Salomonsson
2022-09-19 21:38 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2022-09-20 3:13 ` Fredrik Salomonsson
2022-09-20 3:22 ` Fredrik Salomonsson
2022-09-21 2:26 ` Fredrik Salomonsson
2022-09-24 20:03 ` Fredrik Salomonsson
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=87r1072gfz.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=57899@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=plattfot@posteo.net \
/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).