all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: [PATCH 0/2] Fix URLS for fuse and sshfs-fuse and update fuse
Date: Sat, 26 Dec 2015 01:44:30 -0500	[thread overview]
Message-ID: <cover.1451111675.git.leo@famulari.name> (raw)

The libfuse project has moved their home to Github and so fuse and
sshfs-fuse have new source URLs.

There is a new version of fuse. The new source URLs are a mess. All the
old bootstrapped versions are under a directory named for the current
release. There are non-bootstrapped auto-generated Github tarballs
available under saner URLs.

For now, I think we should use the "messy" URL to fix the packaging and
upgrade to the current release (2.9.4). When 2.9.5 or 3.0.0 comes out, I
expect the situation will improve.

CVE-2015-3202 is fixed in 2.9.4:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3202

Leo Famulari (2):
  gnu: fuse: Update to 2.9.4.
  gnu: sshfs-fuse: Update source URL.

 gnu-system.am                                 |  1 -
 gnu/packages/linux.scm                        | 20 ++++++---
 gnu/packages/patches/fuse-CVE-2015-3202.patch | 65 ---------------------------
 3 files changed, 13 insertions(+), 73 deletions(-)
 delete mode 100644 gnu/packages/patches/fuse-CVE-2015-3202.patch

-- 
2.6.2

             reply	other threads:[~2015-12-26  6:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-26  6:44 Leo Famulari [this message]
2015-12-26  6:44 ` [PATCH 1/2] gnu: fuse: Update to 2.9.4 Leo Famulari
2015-12-29 15:07   ` Ludovic Courtès
2015-12-29 19:21     ` Leo Famulari
2015-12-30  2:02   ` Mark H Weaver
2015-12-30  3:34     ` Mark H Weaver
2015-12-30  6:54       ` Leo Famulari
2015-12-26  6:44 ` [PATCH 2/2] gnu: sshfs-fuse: Update source URL Leo Famulari
2015-12-29 15:08   ` Ludovic Courtès
2015-12-29 19:22     ` Leo Famulari

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=cover.1451111675.git.leo@famulari.name \
    --to=leo@famulari.name \
    --cc=guix-devel@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.