From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Missing patch on savannah means coreutils can't build
Date: Sun, 21 Feb 2016 16:29:01 -0500 [thread overview]
Message-ID: <20160221212901.GA20728@jasmine> (raw)
In-Reply-To: <87povqsvd4.fsf@netris.org>
On Sat, Feb 20, 2016 at 08:30:31PM -0500, Mark H Weaver wrote:
> Mark H Weaver <mhw@netris.org> writes:
>
> > Christopher Allan Webber <cwebber@dustycloud.org> writes:
> >
> >> Efraim Flashner writes:
> >>
> >>> On Sat, 20 Feb 2016 10:19:51 -0800
> >>> Christopher Allan Webber <cwebber@dustycloud.org> wrote:
> >>>
> >>>> Earlier today I tried doing a build without substitutes. I was
> >>>> surprised to see this error:
> >>>>
> >>>> Starting download of /gnu/store/hg3692jqq4jmhg4qx8d7y67fspimy898-?id=3ba68f9e64fa2eb8af22d510437a0c6441feb5e0
> >>>> From http://git.savannah.gnu.org/cgit/coreutils.git/patch/?id=3ba68f9e64fa2eb8af22d510437a0c6441feb5e0...
> >>>> patch 1.2MiB/s 00:00 | 1KiB transferred
> >>>> output path `/gnu/store/hg3692jqq4jmhg4qx8d7y67fspimy898-?id=3ba68f9e64fa2eb8af22d510437a0c6441feb5e0' should have sha256 hash `1dnlszhc8lihhg801i9sz896mlrgfsjfcz62636prb27k5hmixqz', instead has `0zygncr1z1nswmny2vl1havfqswm40vzj0vjvhf5yndavhzr267j'
> >>>>
> >>>> From the coreutils definition:
> >>>> (patches
> >>>> (list (origin
> >>>> (method url-fetch)
> >>>> (uri "http://git.savannah.gnu.org/cgit/coreutils.git/\
> >>>> patch/?id=3ba68f9e64fa2eb8af22d510437a0c6441feb5e0")
> >>>> (sha256
> >>>> (base32
> >>>> "1dnlszhc8lihhg801i9sz896mlrgfsjfcz62636prb27k5hmixqz"))
> >>>> (file-name "coreutils-tail-inotify-race.patch"))))))
> >>>>
> >>>> But indeed, it's not surprising that there's a hash mismatch... there's
> >>>> nothing here!
> >>>>
> >>>> http://git.savannah.gnu.org/cgit/coreutils.git/patch/?id=3ba68f9e64fa2eb8af22d510437a0c6441feb5e0
> >>>>
> >>>
> >>> I updated coreutils on core-updates which included removing the patch from
> >>> the package definition.
> >>
> >> Thanks! In case it's useful, here's a patch which includes the patch
> >> itself rather than pulling it down via http.
> >
> > I fixed this differently, in commit 1a51cbc825, by simply removing the
> > "/" before the "?" in the URL.
>
> I had to revert this, because it caused a full rebuild.
> To be continued...
This seems like a strange result, given that the patch had the same hash
and was stored with the same name. Does anyone have any insight on this
issue?
>
> Mark
>
next prev parent reply other threads:[~2016-02-21 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 18:19 Missing patch on savannah means coreutils can't build Christopher Allan Webber
2016-02-20 20:50 ` Efraim Flashner
2016-02-20 23:19 ` Christopher Allan Webber
2016-02-20 23:51 ` Mark H Weaver
2016-02-21 1:30 ` Mark H Weaver
2016-02-21 21:29 ` Leo Famulari [this message]
2016-02-23 19:27 ` Mark H Weaver
2016-02-28 14:34 ` Ludovic Courtès
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=20160221212901.GA20728@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).