From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: Ryan Prior <rprior@protonmail.com>
Cc: "41010@debbugs.gnu.org" <41010@debbugs.gnu.org>
Subject: [bug#41010] Upgrade Oil to 0.8.pre4
Date: Sat, 16 May 2020 13:20:01 +0200 [thread overview]
Message-ID: <87v9kwnn32.fsf@nckx> (raw)
In-Reply-To: <7j_T0Kf3tHwi7uYPSXZUYLjdVXe_LWrzbgE6XY7mdt-HZsxZQhTuCs8-H4kISkUui_q7IL1BrSnkCIksY62JtGWP-_gXsDC3MBnfusZzcOA=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
Ryan Prior 写道：
> [2. text/x-patch; 0001-gnu-oil-Update-to-0.8.pre4.patch]...
Unfortunately I still can't apply this onto upstream/master:
Applying: gnu: oil: Update to 0.8.pre4
error: sha1 information is lacking or useless
(gnu/packages/shells.scm).
error: could not build fake ancestor
Patch failed at 0001 gnu: oil: Update to 0.8.pre4
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-05-16 11:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 20:01 [bug#41010] Rename & upgrade oil-shell Ryan Prior via Guix-patches via
2020-05-01 21:01 ` [bug#41010] Upgrade Oil to 0.8.pre4 Ryan Prior via Guix-patches via
2020-05-01 23:23 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-01 23:33 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-02 4:02 ` Ryan Prior via Guix-patches via
2020-05-15 17:10 ` Ryan Prior via Guix-patches via
2020-05-15 18:31 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-16 11:20 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2020-05-17 6:14 ` Ryan Prior via Guix-patches via
2020-05-02 19:16 ` Leo Famulari
2020-05-28 23:38 ` [bug#41010] [PATCH 0/1] Updated patch for 0.8.pre5 Ryan Prior via Guix-patches via
2020-05-28 23:38 ` [bug#41010] [PATCH 1/1] gnu: oil: Update to 0.8.pre5 Ryan Prior via Guix-patches via
2020-05-29 4:48 ` bug#41010: [PATCH 0/1] Updated patch for 0.8.pre5 Tobias Geerinckx-Rice via Guix-patches via
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=87v9kwnn32.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=41010@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=rprior@protonmail.com \
/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).