From: ng0 <ng0@libertad.pw>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] version bump libgcrypt -> 1.7
Date: Mon, 18 Apr 2016 00:02:33 +0200 [thread overview]
Message-ID: <87y48bki6e.fsf@libertad.pw> (raw)
In-Reply-To: <20160417202150.GA25383@jasmine> (Leo Famulari's message of "Sun, 17 Apr 2016 16:21:50 -0400")
Leo Famulari <leo@famulari.name> writes:
> On Sat, Apr 16, 2016 at 11:15:25PM +0200, ng0 wrote:
>> Subject: [PATCH] gnu: libgcrypt: Update to 1.7.0.
>
> Here are what I think are the salient parts of the release announcement
> [0].
>
> 1.7.0 is a new stable version of libgcrypt.
>
> 1.7.0 is API and ABI compatible with 1.6. There are no changed or
> deleted interfaces. All the interface changes are from the addition of
> new interfaces.
>
> The 1.6 series will "enter end-of-life state on 2017-06-30.
>
> Regardless of whether we replace 1.6 or create a new package, any
> changes to libgcrypt should go to core-updates:
>
> $ guix refresh -l libgcrypt
> Building the following 706 packages would ensure 1999 dependent packages are rebuilt [...]
> $ guix refresh -l libgcrypt@1.5
> Building the following 363 packages would ensure 875 dependent packages are rebuilt [...]
>
> [0]
> https://lists.gnupg.org/pipermail/gnupg-announce/2016q2/000386.html
Hi, thanks for your additional input.
I already reconsidered this and updated it.
It seems like I need to change the subject if I update patches:
http://lists.gnu.org/archive/html/guix-devel/2016-04/msg00681.html
thanks,
--
ng0
prev parent reply other threads:[~2016-04-17 22:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 21:15 [PATCH] version bump libgcrypt -> 1.7 ng0
2016-04-17 7:53 ` Alex Kost
2016-04-17 9:36 ` ng0
2016-04-17 9:53 ` ng0
2016-04-18 20:32 ` Leo Famulari
2016-04-19 8:27 ` Alex Kost
2016-04-19 9:27 ` ng0
2016-04-20 17:03 ` Ludovic Courtès
2016-04-21 16:32 ` Leo Famulari
2016-04-24 14:23 ` Ludovic Courtès
2016-05-11 12:50 ` ng0
2016-05-14 23:54 ` ng0
2016-05-15 17:49 ` Leo Famulari
2016-04-17 20:21 ` Leo Famulari
2016-04-17 22:02 ` ng0 [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=87y48bki6e.fsf@libertad.pw \
--to=ng0@libertad.pw \
--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 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).