GNU bug report logs - #32043
[PATCH] gnu: libgit2: Update to 0.26.4 [fixes CVE-2018-11235].

Previous Next

Full log

Message #8 received at 32043 <at> debbugs.gnu.org (full text, mbox):

From: Marius Bakke <mbakke <at> fastmail.com>
To: Leo Famulari <leo <at> famulari.name>, 32043 <at> debbugs.gnu.org
Subject: Re: [bug#32043] [PATCH] gnu: libgit2: Update to 0.26.4 [fixes
 CVE-2018-11235].
Date: Tue, 03 Jul 2018 00:50:37 +0200

[Message part 1 (text/plain, inline)]

Leo Famulari <leo <at> famulari.name> writes:

> * gnu/packages/version-control.scm (libgit2): Update to 0.26.4.
> (source): Adjust patch name.
> * gnu/packages/patches/libgit2-0.25.1-mtime-0.patch: Rename to ...
> * gnu/packages/patches/julia-libgit2-fix.patch: ... this.
> * gnu/local.mk (dist_patch_DATA): Adjust accordingly.
> ---
>  gnu/local.mk                                  |  2 +-
>  gnu/packages/patches/julia-libgit2-fix.patch  | 22 +++++++++++++++++++
>  .../patches/libgit2-0.25.1-mtime-0.patch      | 14 ------------
>  gnu/packages/version-control.scm              |  6 ++---
>  4 files changed, 26 insertions(+), 18 deletions(-)
>  create mode 100644 gnu/packages/patches/julia-libgit2-fix.patch
>  delete mode 100644 gnu/packages/patches/libgit2-0.25.1-mtime-0.patch

'libgit2-mtime-0.patch' seems to have disappeared, yet it's in the
(patches) field of libgit2.  I suppose it got unstaged somehow?

'julia-libgit2-fix.patch' seems unrelated, so the commit message should
probably not say renamed.  And I would guess it should be applied to the
Julia package.  It would be nice with a link to the upstream commit too!

Time for a holiday perhaps? ;-)

LGTM with those adjustments!

[signature.asc (application/pgp-signature, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.