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/1] w3m: Change source and update
Date: Mon,  4 Jan 2016 14:26:54 -0500	[thread overview]
Message-ID: <cover.1451935587.git.leo@famulari.name> (raw)

This patch fixes bug#16791. There is some background in the bug's thread
[0].

Basically, our current source for w3m seems to be abandoned [1].

There is an active development fork at Debian [2] that fixes bug#16791.
They have also fixed several other SSL/TLS issues, as well as both of
the patches / substitutions currently applied to our package. They are
also addressing bugs and integrating patches from other distros (at
least, I saw work from Ubuntu and Gentoo).

I think the Debian repo is our best source for w3m.

I have emailed the person doing most of the work in the Debian repo for
advice about packaging, such as which branch and tags are most suitable.

Until they reply, here is my best effort patch, based on the latest
non-Debian release tag on the master branch.

[0]
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16791

[1]
http://sourceforge.net/p/w3m/

[2]
http://anonscm.debian.org/cgit/collab-maint/w3m.git

Leo Famulari (1):
  gnu: w3m: Update to 0.5.3+git20151119.

 gnu-system.am                              |  1 -
 gnu/packages/patches/w3m-fix-compile.patch | 15 ---------------
 gnu/packages/w3m.scm                       | 24 +++++++++---------------
 3 files changed, 9 insertions(+), 31 deletions(-)
 delete mode 100644 gnu/packages/patches/w3m-fix-compile.patch

-- 
2.6.4

             reply	other threads:[~2016-01-04 19:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 19:26 Leo Famulari [this message]
2016-01-04 19:26 ` [PATCH 1/1] gnu: w3m: Update to 0.5.3+git20151119 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.1451935587.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.