From: Jack Hill <jackhill@jackhill.us>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: purpose of GnuTLS versions
Date: Mon, 30 Jan 2023 15:25:29 -0500 (EST) [thread overview]
Message-ID: <420a4ffb-83f7-efc4-dab0-ee6d05a8c4b2@jackhill.us> (raw)
In-Reply-To: <865yctsdrr.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Thu, 26 Jan 2023, Simon Tournier wrote:
> Hi,
>
> On Thu, 26 Jan 2023 at 00:12, Jack Hill <jackhill@jackhill.us> wrote:
>
>> It seems to me that the `gnutls` variable should refer to the latest
>> "stable" release, and the `gnutls-latest` variable to latest "next"
>> release. Does that make sense? What am I missing?
>
> This means a core-updates change – so next core-updates merge cycle? :-)
Agreed, a change to the gnutls variable will need to go through
core-updates. However, while the current situation does seem odd to me,
I'm still not sure what the best resolution will be. "Downgrading" gnutls
was only one option. Another option that I can think of is moving to only
having one GnuTLS version, probably 3.7.x, and fixing problems via grafts
in the master branch. In the meantime, we may want to move individual
packages from gnutls to gnutls-latest or patch the known bugs in gnutls
with grafts.
To help us decide, I've asked [0] the GnuTLS developers for their
thoughts.
> If I read correctly, core-updates already uses 3.7.7 for the variable
> ’gnutls’ and note that the variable ’gnutls-latest’ also uses 3.7.7. :-)
:)
[0] https://lists.gnutls.org/pipermail/gnutls-help/2023-January/004813.html
Best,
Jack
next prev parent reply other threads:[~2023-01-30 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 5:12 purpose of GnuTLS versions Jack Hill
2023-01-26 12:04 ` Simon Tournier
2023-01-30 20:25 ` Jack Hill [this message]
2023-01-30 21:19 ` Jack Hill
2023-01-31 16:59 ` Ludovic Courtès
2023-01-31 17:14 ` Jack Hill
2023-02-08 8:50 ` Ludovic Courtès
2023-01-30 21:51 ` Ludovic Courtès
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=420a4ffb-83f7-efc4-dab0-ee6d05a8c4b2@jackhill.us \
--to=jackhill@jackhill.us \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.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.