From: Leo Famulari <leo@famulari.name>
To: 27770@debbugs.gnu.org
Subject: [bug#27770] [PATCH] gnu: vim: Update to 8.0.0727 [fixes CVE-2017-11109].
Date: Thu, 20 Jul 2017 01:44:36 -0400 [thread overview]
Message-ID: <13567bf3a5179aafe1491aff8e2fa62e9c543ea2.1500529284.git.leo@famulari.name> (raw)
vim-full fails its tests with this update. I've noticed from previous
discussion that the test suite is flaky with vim-full. What do you
suggest?
------
Test results:
From test_alot.vim:
Found errors in Test_input_in_timer():
function RunTheTest[24]..Test_input_in_timer line 4: Expected 'hello' but got ''
Found errors in Test_map_ctrl_c_insert():
function RunTheTest[24]..Test_map_ctrl_c_insert line 7: Expected 'TEST2: CTRL-C |<ctrl-c>A|' but got 'GoTEST2: CTRL-C |<ctrl-c>A|'
TEST FAILURE
------
* gnu/packages/vim.scm (vim, vim-full): Update to 8.0.0727.
---
gnu/packages/vim.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/vim.scm b/gnu/packages/vim.scm
index 27c0b0da9..39894f39c 100644
--- a/gnu/packages/vim.scm
+++ b/gnu/packages/vim.scm
@@ -60,7 +60,7 @@
(define-public vim
(package
(name "vim")
- (version "8.0.0600")
+ (version "8.0.0727")
(source (origin
(method url-fetch)
(uri (string-append "https://github.com/vim/vim/archive/v"
@@ -68,7 +68,7 @@
(file-name (string-append name "-" version ".tar.gz"))
(sha256
(base32
- "1ifaj0lfzqn06snkcd83l58m9r6lg7lk3wspx71k5ycvypyfi67s"))))
+ "0hwqglpsk8qlp2rn6q9p35fxk88xixljk1yv42m3j01g3bgqg0gx"))))
(build-system gnu-build-system)
(arguments
`(#:test-target "test"
--
2.13.3
next reply other threads:[~2017-07-20 5:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 5:44 Leo Famulari [this message]
2017-07-21 19:25 ` bug#27770: [PATCH] gnu: vim: Update to 8.0.0727 [fixes CVE-2017-11109] Leo Famulari
2017-07-24 12:45 ` ‘vim-full’ to be removed? Ludovic Courtès
2017-07-29 14:54 ` [bug#27770] [PATCH] gnu: vim: Update to 8.0.0727 [fixes CVE-2017-11109] Marius Bakke
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=13567bf3a5179aafe1491aff8e2fa62e9c543ea2.1500529284.git.leo@famulari.name \
--to=leo@famulari.name \
--cc=27770@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 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.