all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Vasile Dumitrascu <va511e@yahoo.com>
Cc: 26746@debbugs.gnu.org
Subject: bug#26746: [PATCH] gnu: bind: Update to 9.11.1.
Date: Tue, 2 May 2017 13:32:34 -0400	[thread overview]
Message-ID: <20170502173234.GB15523@jasmine> (raw)
In-Reply-To: <20170502123428.17304-1-va511e@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 864 bytes --]

On Tue, May 02, 2017 at 02:34:28PM +0200, Vasile Dumitrascu wrote:
> * gnu/packages/dns.scm (bind): Update to 9.11.1.
> * gnu/packages/dns.scm (bind)[license]: Change isc to mpl2.0.

Thanks! I see that ISC recommends this release for production use,
although it is labeled "Early Deployment" instead of "Current-Stable".

You can see this production "endorsement" if you hover your mouse over
the "Early Deployment" text in the BIND tab:

https://www.isc.org/downloads/

Does anyone see a reason to stick to the 9.10 release series for now?
And, should we stick the 9.9 release series for isc-dhcp's bundled BIND
replacement?

> -    (license (list license:isc))))
> +    (license (list license:mpl2.0))))

In case anyone is wondering, ISC relicensed BIND to the MPL2.0 in BIND
9.11.0:

https://www.isc.org/blogs/bind9-adopts-the-mpl-2-0-license-with-bind-9-11-0/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-05-02 17:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02 12:34 bug#26746: [PATCH] gnu: bind: Update to 9.11.1 Vasile Dumitrascu
2017-05-02 17:32 ` Leo Famulari [this message]
2017-05-02 21:34   ` Ludovic Courtès
2017-05-03 22:52 ` Leo Famulari
2017-05-05 13:38   ` Vasile Dumitrascu
2017-05-05 14:38     ` tumashu
2017-05-05 19:32       ` 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=20170502173234.GB15523@jasmine \
    --to=leo@famulari.name \
    --cc=26746@debbugs.gnu.org \
    --cc=va511e@yahoo.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 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.