From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Perl-www-curl: Fix build failure
Date: Tue, 25 Oct 2016 20:01:30 +0100 [thread overview]
Message-ID: <877f8wfe2d.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <cover.1477348992.git.leo@famulari.name>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
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.
0: https://github.com/curl/curl/commit/d6604524ad24daf4581efbe0020da058d2b3af84
1: https://github.com/curl/curl/commit/5fce88aa8c1256486377471186fc353c50d610b1
2: https://rt.cpan.org/Public/Bug/Display.html?id=117793
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]
next prev parent reply other threads:[~2016-10-25 19:01 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 ` Marius Bakke [this message]
2016-10-26 22:44 ` [PATCH 0/1] Perl-www-curl: " 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=877f8wfe2d.fsf@duckhunt.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@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.