From: ng0 <ng0@libertad.pw>
To: guix-devel@gnu.org
Subject: Re: gnurl: update and various changes to package definition
Date: Thu, 22 Dec 2016 16:32:45 +0000 [thread overview]
Message-ID: <87r34zorf6.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161221172718.28612-1-ng0@libertad.pw>
ng0 <ng0@libertad.pw> writes:
> [PATCH 1/3] gnu: gnurl: Update to 7.52.0 [fixes CVE.....
>
> I'm aware of the warning the cURL maintainers posted and will make the gnurl release as soon as they release the version of cURL fixing whatever unknown security issue they have.
In my opinion, we can wait until I have released the version
which fixes whatever is so insecure in cURL at the moment. I will
rebase this patchset and send again then, skipping the version
released on 2016-12-21.
What do you think?
> [PATCH 2/3] gnu: gnurl: Make tests more verbose.
>
> Compare to curl.scm
>
> [PATCH 3/3] gnu: gnurl: Split man pages to doc output.
>
> Man pages are 1.5 MB big. Split it.
>
>
--
♥Ⓐ ng0 | PGP keys and more: https://n0is.noblogs.org/
| http://ng0.chaosnet.org
next prev parent reply other threads:[~2016-12-22 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 17:27 gnurl: update and various changes to package definition ng0
2016-12-21 17:27 ` [PATCH 1/3] gnu: gnurl: Update to 7.52.0 [fixes CVE-2016-{9586, 9952, 9953}] ng0
2016-12-21 17:27 ` [PATCH 2/3] gnu: gnurl: Make tests more verbose ng0
2016-12-21 17:27 ` [PATCH 3/3] gnu: gnurl: Split man pages to doc output ng0
2016-12-22 16:32 ` ng0 [this message]
2016-12-23 11:29 ` gnurl, update to 7.52.1 (and: more verbose tests + split man pages to "doc") ng0
2016-12-23 11:29 ` [PATCH 1/3] gnu: gnurl: Update to 7.52.1 [fixes CVE-2016-{9586, 9952, 9953, 9594}] ng0
2016-12-23 11:29 ` [PATCH 2/3] gnu: gnurl: Make tests more verbose ng0
2016-12-23 11:29 ` [PATCH 3/3] gnu: gnurl: Split man pages to doc output ng0
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=87r34zorf6.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@libertad.pw \
--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.