From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Perl-www-curl: Fix build failure
Date: Wed, 26 Oct 2016 18:44:46 -0400 [thread overview]
Message-ID: <20161026224446.GA11974@jasmine> (raw)
In-Reply-To: <877f8wfe2d.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Tue, Oct 25, 2016 at 08:01:30PM +0100, Marius Bakke wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > This fixes the build failure of perl-www-curl build on core-updates:
> > https://hydra.gnu.org/build/1553325/nixlog/2
> >
> > The patch is copied from the upstream bug tracker, but the maintainers
> > don't seem to have done anything with the patch yet.
> >
> > What do you think?
> >
> > Leo Famulari (1):
> > gnu: perl-www-curl: Fix build failure.
> >
> > gnu/local.mk | 1 +
> > .../patches/perl-www-curl-remove-symbol.patch | 39 ++++++++++++++++++++++
> > gnu/packages/web.scm | 1 +
> > 3 files changed, 41 insertions(+)
> > create mode 100644 gnu/packages/patches/perl-www-curl-remove-symbol.patch
>
> I dug into the curl history and managed to find the commits[0][1] that
> lead to this. Combined with the bug report[2] linked in the patch, this
> seems sensible.
>
> Last maintainer activity on the upstream tracker was two years ago, so
> we may have to carry this a while.
Okay, I pushed it to core-updates. Thanks for the review!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2016-10-26 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 22:44 [PATCH 0/1] Perl-www-curl: Fix build failure Leo Famulari
2016-10-24 22:44 ` [PATCH 1/1] gnu: perl-www-curl: " Leo Famulari
2016-10-25 19:01 ` [PATCH 0/1] Perl-www-curl: " Marius Bakke
2016-10-26 22:44 ` Leo Famulari [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161026224446.GA11974@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).