On Thu, 26 Jan 2023, Simon Tournier wrote:
Hi,
On Thu, 26 Jan 2023 at 00:12, Jack Hill <[email protected]> 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
