all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>, 27770-done@debbugs.gnu.org
Subject: [bug#27770] [PATCH] gnu: vim: Update to 8.0.0727 [fixes	CVE-2017-11109].
Date: Sat, 29 Jul 2017 16:54:46 +0200	[thread overview]
Message-ID: <87o9s3z421.fsf@fastmail.com> (raw)
In-Reply-To: <20170721192544.GA3708@jasmine.lan>

[-- 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 --]

      parent reply	other threads:[~2017-07-29 14:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20  5:44 [bug#27770] [PATCH] gnu: vim: Update to 8.0.0727 [fixes CVE-2017-11109] Leo Famulari
2017-07-21 19:25 ` bug#27770: " Leo Famulari
2017-07-24 12:45   ` ‘vim-full’ to be removed? Ludovic Courtès
2017-07-29 14:54   ` Marius Bakke [this message]

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=87o9s3z421.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=27770-done@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.