all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon South <simon@simonsouth.net>
To: 44596@debbugs.gnu.org
Cc: Simon South <simon@simonsouth.net>
Subject: [bug#44596] [PATCH v2 0/2] gnu: knot-resolver: Update to 5.2.0; add "doc" output
Date: Tue,  1 Dec 2020 09:45:18 -0500	[thread overview]
Message-ID: <cover.1606831469.git.simon@simonsouth.net> (raw)
In-Reply-To: <cover.1605198478.git.simon@simonsouth.net>

I've been waiting to see whether the Knot Resolver team would issue a point
release with their fix[0] for the bug discovered in version 5.2.0, but as that
doesn't seem to be happening here is an updated patchset that applies the fix
directly.

The only changes from the initial set are

- The addition of a patch with the upstream commit that fixes an issue with
  the internal map() function on 32-bit platforms, and

- Some gentle editing of the commit messages.

For convenience, here's my original cover letter:

These patches

- Update Knot Resolver, a resolving DNS server, to 5.2.0. Two inputs are
  added to support new functionality in this release:

  - Texinfo, to enable generating the manual in Info format; and

  - libnghttp2, to enable a new implementation in C of DNS-over-HTTPS. From
    the Knot Resolver manual:

      Knot Resolver currently offers two DoH implementations. It is
      recommended to use this new implementation, which is more reliable,
      scalable and has fewer dependencies. Make sure to use doh2 kind in
      net.listen() to select this implementation.[1]

- Move the Knot Resolver manual to a separate "doc" output, allowing it to be
  installed on its own by a user responsible for configuring the
  service. (This also helps align this package with the one for Knot, its
  sibling authoritative name server.)

[0] https://gitlab.nic.cz/knot/knot-resolver/-/merge_requests/1093
[1] https://knot-resolver.readthedocs.io/en/v5.2.0/daemon-bindings-net_tlssrv.html#dns-over-https-doh

--
Simon South
simon@simonsouth.net


Simon South (2):
  gnu: knot-resolver: Update to 5.2.0.
  gnu: knot-resolver: Move manual, examples to separate "doc" output

 gnu/local.mk                                  |   1 +
 gnu/packages/dns.scm                          |  27 +++-
 ...t-resolver-fix-map-command-on-32-bit.patch | 146 ++++++++++++++++++
 3 files changed, 170 insertions(+), 4 deletions(-)
 create mode 100644 gnu/packages/patches/knot-resolver-fix-map-command-on-32-bit.patch

-- 
2.29.2





  parent reply	other threads:[~2020-12-01 14:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 16:46 [bug#44596] [PATCH 0/2] gnu: knot-resolver: Update to 5.2.0; add "doc" output Simon South
2020-11-12 16:48 ` [bug#44596] [PATCH 1/2] gnu: knot-resolver: Update to 5.2.0 Simon South
2020-11-12 16:48 ` [bug#44596] [PATCH 2/2] gnu: knot-resolver: Move manual, examples to separate "doc" output Simon South
2020-11-13 16:00 ` [bug#44596] [PATCH 0/2] gnu: knot-resolver: Update to 5.2.0; add " Simon South
2020-12-01 14:45 ` Simon South [this message]
2020-12-01 14:45   ` [bug#44596] [PATCH v2 1/2] gnu: knot-resolver: Update to 5.2.0 Simon South
2020-12-01 14:45   ` [bug#44596] [PATCH v2 2/2] gnu: knot-resolver: Move manual, examples to separate "doc" output Simon South
2020-12-06 10:41   ` bug#44596: [PATCH v2 0/2] gnu: knot-resolver: Update to 5.2.0; add " 宋文武

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.1606831469.git.simon@simonsouth.net \
    --to=simon@simonsouth.net \
    --cc=44596@debbugs.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.