From: HiPhish <hiphish@posteo.de>
To: 35218@debbugs.gnu.org
Subject: [bug#35218] [PATCH] Fix Lua dependencies of Neovim
Date: Wed, 10 Apr 2019 13:49:35 +0200 [thread overview]
Message-ID: <3027356.Ros9scuHIA@aleksandar-ixtreme-m5740> (raw)
[-- Attachment #1: Type: text/plain, Size: 131 bytes --]
Lua minor version releases are not backwards-compatible and Neovim requires
Lua 5.1, not the previously specified Lua 5.2 version.
[-- Attachment #2: 0001-2019-04-10-HiPhish-hiphish-posteo.de.patch --]
[-- Type: text/x-patch, Size: 1473 bytes --]
From c878cc9d30a265bc97836e799b85ad41bc8a5e29 Mon Sep 17 00:00:00 2001
From: HiPhish <hiphish@posteo.de>
Date: Wed, 10 Apr 2019 13:21:26 +0200
Subject: [PATCH] 2019-04-10 HiPhish <hiphish@posteo.de>
* gnu/packages/vim.scm (neovim): Use correct Lua version as dependencies
---
gnu/packages/vim.scm | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/gnu/packages/vim.scm b/gnu/packages/vim.scm
index 56deb12c3d..dadffa3ab1 100644
--- a/gnu/packages/vim.scm
+++ b/gnu/packages/vim.scm
@@ -756,7 +756,7 @@ are detected, the user is notified.")))
#t))
(add-after 'unpack 'set-lua-paths
(lambda* (#:key inputs #:allow-other-keys)
- (let* ((lua-version "5.2")
+ (let* ((lua-version "5.1")
(lua-cpath-spec
(lambda (prefix)
(let ((path (string-append prefix "/lib/lua/" lua-version)))
@@ -783,10 +783,10 @@ are detected, the user is notified.")))
("unibilium" ,unibilium)
("jemalloc" ,jemalloc)
("libiconv" ,libiconv)
- ("lua" ,lua-5.2)
- ("lua-lpeg" ,lua5.2-lpeg)
- ("lua-bitop" ,lua5.2-bitop)
- ("lua-libmpack" ,lua5.2-libmpack)))
+ ("lua" ,lua-5.1)
+ ("lua-lpeg" ,lua5.1-lpeg)
+ ("lua-bitop" ,lua5.1-bitop)
+ ("lua-libmpack" ,lua5.1-libmpack)))
(native-inputs
`(("pkg-config" ,pkg-config)
("gettext" ,gettext-minimal)
--
2.19.1
next reply other threads:[~2019-04-10 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 11:49 HiPhish [this message]
2019-04-11 11:34 ` bug#35218: [PATCH] Fix Lua dependencies of Neovim 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=3027356.Ros9scuHIA@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=35218@debbugs.gnu.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).