[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#25061: consider adding %COMPAT to default gnutls priority string

From: Kaushal Modi
Subject: bug#25061: consider adding %COMPAT to default gnutls priority string
Date: Thu, 21 Dec 2017 13:20:06 +0000

Thank you all. This fixed the emacs-26 branch. But the master branch is still broken (not broken build but broken https fetches): https://travis-ci.org/kaushalmodi/ox-hugo/jobs/319693934

The emacs-26 branch will be merged into master at some point, but I am just saying.

On Wed, Dec 20, 2017 at 11:14 AM Eli Zaretskii <address@hidden> wrote:
> From: Robert Pluim <address@hidden>
> Date: Wed, 20 Dec 2017 12:41:08 +0100
> Cc: Noam Postavsky <address@hidden>, address@hidden,
>       address@hidden, address@hidden, address@hidden,
>       address@hidden, address@hidden
> > I don't understand why. This function has been available since GnuTLS
> > was created, according to the docs. Do we know what GnuTLS version is used
> > in Travis CI?
> It fails for me here with GnuTLS-3.4.10. According to
> https://lists.gnupg.org/pipermail/gnutls-help/2016-June/004129.html
> that function was added in 3.5.1. Looking through the git repo it was
> previously an internal function.

This means we cannot use this method without some fallback for systems
with older GnuTLS, as 3.5.X is still not old enough to assume it's
available widely enough.  Could we perhaps use a fixed list of
features for older GnuTLS versions?

Ted, could you please fix this ASAP?  It currently prevents the
release branch from building on many systems.

Kaushal Modi

reply via email to

[Prev in Thread] Current Thread [Next in Thread]