[PATCH 2/2] gnu: neovim: upgrade to 0.7.0

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • Ryan Sundberg
Owner
unassigned
Submitted by
Ryan Sundberg
Severity
normal
Merged with
R
R
Ryan Sundberg wrote on 2 May 2022 21:13
(address . guix-patches@gnu.org)(name . Ryan Sundberg)(address . ryan@arctype.co)
20220502191338.5032-2-ryan@arctype.co
* gnu/packages/vim.scm (neovim): Upgrade to 0.7.0
---
gnu/packages/vim.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Toggle diff (24 lines)
diff --git a/gnu/packages/vim.scm b/gnu/packages/vim.scm
index 7279798fe6..d04ee49775 100644
--- a/gnu/packages/vim.scm
+++ b/gnu/packages/vim.scm
@@ -668,7 +668,7 @@ (define-public neovim-syntastic
(define-public neovim
(package
(name "neovim")
- (version "0.6.1")
+ (version "0.7.0")
(source
(origin
(method git-fetch)
@@ -677,7 +677,7 @@ (define-public neovim
(commit (string-append "v" version))))
(file-name (git-file-name name version))
(sha256
- (base32 "10p6lg5yv9n6wcwdprwvvi56dfcm4wsj54nm0invyx3mhf7374lx"))))
+ (base32 "1m7xmry66pn27gvk7qj9di83xa1h7zjp4c6ygnf218pqhr08x06g"))))
(build-system cmake-build-system)
(arguments
`(#:modules ((srfi srfi-26)
--
2.34.0
L
L
Ludovic Courtès wrote on 20 May 2022 20:17
control message for bug #55228
(address . control@debbugs.gnu.org)
874k1kxe4t.fsf@gnu.org
merge 55228 55229
quit
L
L
Ludovic Courtès wrote on 20 May 2022 20:18
Re: bug#55228: [PATCH 2/2] gnu: neovim: upgrade to 0.7.0
(name . Ryan Sundberg)(address . ryan@arctype.co)(address . 55228-done@debbugs.gnu.org)
87zgjcvziz.fsf_-_@gnu.org
Hi,

Ryan Sundberg <ryan@arctype.co> skribis:

Toggle quote (2 lines)
> * gnu/packages/vim.scm (neovim): Upgrade to 0.7.0

This was done independently and pushed a few days ago as commit
e49a2d03bbfcc0cc6b69f2299ba661f2e581301e.

Closing, thanks!

Ludo’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 55228@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 55228
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch