all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 46456-done@debbugs.gnu.org, dannym@scratchpost.org,
	Leo Famulari <leo@famulari.name>
Subject: bug#46456: [core-updates] d3.v5.js source checksum changed
Date: Wed, 13 Jul 2022 01:19:52 -0400	[thread overview]
Message-ID: <87fsj537yf.fsf@gmail.com> (raw)
In-Reply-To: <87pn15owzl.fsf@elephly.net> (Ricardo Wurmus's message of "Fri, 12 Feb 2021 21:24:30 +0100")

Hi,

Ricardo Wurmus <rekado@elephly.net> writes:

> Leo Famulari <leo@famulari.name> writes:
>
>> On Fri, Feb 12, 2021 at 04:53:15AM +0100, Danny Milosavljevic wrote:
>>> Starting download of /gnu/store/bf496ni94ik19gdxkgp0vddkfxbid2vf-d3.v5.js
>>> From https://d3js.org/d3.v5.js...
>>> downloading from https://d3js.org/d3.v5.js ...
>>>  d3.v5.js                                                                                                                  2.22GiB/s 00:00 | 504KiB transferred
>>> sha256 hash mismatch for /gnu/store/bf496ni94ik19gdxkgp0vddkfxbid2vf-d3.v5.js:
>>>   expected hash: 0kxvx5pfagxn6nhavdwsdnzyd26g0z5dsfi1pi5dvcmb0c8ipcdn
>>
>> Attached.
>
> I guess we can’t use this URL then.  This is just for the latest minor
> version for major version 5.  We use similar d3 URLs for the other major
> versions.

Updated hashes for all mismatching cases in commit 5017cca351.

Closing.

Thanks for the report!

Maxim




  reply	other threads:[~2022-07-13  5:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12  3:53 bug#46456: [core-updates] d3.v5.js source checksum changed Danny Milosavljevic
2021-02-12 18:14 ` Leo Famulari
2021-02-12 20:24   ` Ricardo Wurmus
2022-07-13  5:19     ` Maxim Cournoyer [this message]
2021-02-13  3:15 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fsj537yf.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=46456-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=leo@famulari.name \
    --cc=rekado@elephly.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.