[bug#27770] [PATCH] gnu: vim: Update to 8.0.0727 [fixes CVE-2017-11109].

[bug#27770] [PATCH] gnu: vim: Update to 8.0.0727 [fixes CVE-2017-11109].

[Leo Famulari]

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

bug#27770: [PATCH] gnu: vim: Update to 8.0.0727 [fixes CVE-2017-11109].

[Leo Famulari]

On Thu, Jul 20, 2017 at 01:44:36AM -0400, Leo Famulari wrote:
> 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?

In 3c14378381fc1f187a07b2f958eeed1958f02672, I updated vim and kept
vim-full at 8.0.0600.

This means that vim-full is still vulnerable to CVE-2017-11109.

I'll remove the vim-full package in 1 week (July 28) unless we have a
fix for this bug.

‘vim-full’ to be removed?

[Ludovic Courtès]

Dear Vim users,

This is an excerpt from <https://bugs.gnu.org/27770>:

Leo Famulari <leo@famulari.name> skribis:

> On Thu, Jul 20, 2017 at 01:44:36AM -0400, Leo Famulari wrote:
>> 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?
>
> In 3c14378381fc1f187a07b2f958eeed1958f02672, I updated vim and kept
> vim-full at 8.0.0600.
>
> This means that vim-full is still vulnerable to CVE-2017-11109.
>
> I'll remove the vim-full package in 1 week (July 28) unless we have a
> fix for this bug.

I’m sure removing this package would annoy quite a bunch of people, so
please do take a look and give a hand to Leo!

Ludo’.

[bug#27770] [PATCH] gnu: vim: Update to 8.0.0727 [fixes CVE-2017-11109].

[Marius Bakke]

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

Leo Famulari <leo@famulari.name> writes:

> On Thu, Jul 20, 2017 at 01:44:36AM -0400, Leo Famulari wrote:
>> 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?
>
> In 3c14378381fc1f187a07b2f958eeed1958f02672, I updated vim and kept
> vim-full at 8.0.0600.
>
> This means that vim-full is still vulnerable to CVE-2017-11109.
>
> I'll remove the vim-full package in 1 week (July 28) unless we have a
> fix for this bug.

FWIW I believe the root cause of at least some of the failing GUI tests
have been found:

https://groups.google.com/forum/#!msg/vim_dev/_a9DYXDuZ1I/Mb2c3lUbBgAJ

I don't have strong objections against removing this package, but we
could also just disable tests until it's working again.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]