From: Nicolas Graves via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 55618@debbugs.gnu.org
Subject: bug#55618: Allow patching from mummi issues
Date: Wed, 25 May 2022 00:14:00 +0200 [thread overview]
Message-ID: <874k1ek1ue.fsf@ngraves.fr> (raw)
Hi !
I was tring to fix a local build using an online patch on mummi, this
way :
(define-public my-emacs-list-utils
(package
(inherit emacs-list-utils)
(name "my-emacs-list-utils")
(version "0.4.6")
(source
(origin
(method git-fetch)
(uri (git-reference
(url "https://github.com/rolandwalker/list-utils")
(commit (string-append "v" version))))
(file-name (git-file-name name version))
(sha256
(base32 "07hbz2md52ccy95gv4d5n6szrfmpfqf3w4kwqdg2cf54c7kgf7hw"))
(patches
(list
(origin
(method url-fetch)
(uri "https://issues.guix.gnu.org/issue/55498/attachment/0")
(sha256
(base32
"1ysjb23g21m0jhkn63hq56snjd6skd9pl58c365g519q03hq5s87")))))))))
As it is a quick and convenient way to apply someone's work while the
patch is not upstream, I expected it to work, but it failed with the
following error during download:
Starting download of /gnu/store/v91i1m61skr42136vnxhzm4gzyidp11y-0
From https://issues.guix.gnu.org/issue/55498/attachment/0...
Bad media-type header component: text
I don't now if the fix should come from mummi's or guix's side, but I
found it a relevant way to quickly test an existing patch for one's
needs.
Thanks if you can enable this type of patches, or get alternatives if
there are. Also thanks for all the work on guix, it's amazing.
Nicolas Graves
next reply other threads:[~2022-05-24 22:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 22:14 Nicolas Graves via Bug reports for GNU Guix [this message]
2022-05-25 11:06 ` bug#55618: Allow patching from mummi issues Maxime Devos
2022-05-25 12:06 ` Daniel Meißner via Bug reports for GNU Guix
2022-05-25 12:16 ` Liliana Marie Prikler
2022-05-25 14:21 ` Maxime Devos
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=874k1ek1ue.fsf@ngraves.fr \
--to=bug-guix@gnu.org \
--cc=55618@debbugs.gnu.org \
--cc=ngraves@ngraves.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).