From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Fredrik Salomonsson <plattfot@posteo.net>, 48483-done@debbugs.gnu.org
Subject: bug#48483: [PATCH 1/1] gnu: emacs-libyaml: fix broken phase.
Date: Mon, 17 May 2021 20:02:11 +0200 [thread overview]
Message-ID: <e3d31c42dacd8e627a4affba65a3a6a843a9ee91.camel@student.tugraz.at> (raw)
In-Reply-To: <20210517173628.54883-1-plattfot@posteo.net>
Pushed with the adjustments listed below:
Am Montag, den 17.05.2021, 17:36 +0000 schrieb Fredrik Salomonsson:
> * gnu/packages/emacs-xyz.scm (emacs-libyaml): Change
> substitute-libyaml-core-path phase to be added after the unpack
> phase. As the
> add-source-to-load-path phase which it was added to before seems to
> been
> removed, which resulted in the phase not being run.
I've rewritten the header so as to not contain "fix" (there has been
recent discussion to avoid said word unless necessary), and simplified
this line as well.
> ---
> gnu/packages/emacs-xyz.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
> index 7a62b6b7ef..6f67083d01 100644
> --- a/gnu/packages/emacs-xyz.scm
> +++ b/gnu/packages/emacs-xyz.scm
> @@ -22533,7 +22533,7 @@ utilities.")
> (define-public emacs-libyaml
> ;; Upstream made no release so far.
> (let ((version "0")
> - (revision "1")
> + (revision "2")
> (commit "703e0d448c7ee24e25b513a3c65980c80e166805"))
> (package
> (name "emacs-libyaml")
You don't need to change the revision if the source has not changed.
Regards,
Leo
next prev parent reply other threads:[~2021-05-17 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 17:29 [bug#48483] [PATCH 0/1] Fix broken emacs-libyaml Fredrik Salomonsson
2021-05-17 17:36 ` [bug#48483] [PATCH 1/1] gnu: emacs-libyaml: fix broken phase Fredrik Salomonsson
2021-05-17 18:02 ` Leo Prikler [this message]
2021-05-17 18:43 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3d31c42dacd8e627a4affba65a3a6a843a9ee91.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=48483-done@debbugs.gnu.org \
--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 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.