On 2016-11-18 Guido Günther wrote:
> On Thu, Nov 17, 2016 at 07:57:05PM +0100, Andreas Metzler wrote:
[...]
> > Would you consider this to be a serious issue for libvirt? i.e. should
> > we block unfixed gnutls from propagating to testing?
> I don't think that would be a good
Hi,
On Thu, Nov 17, 2016 at 07:57:05PM +0100, Andreas Metzler wrote:
> On 2016-11-16 Guido Günther wrote:
> > Package: libgnutls30
> > Version: 3.5.6-4
> > Severity: normal
>
> > Hi,
> > 3.5.6 introduced a behaviour change that breaks libvirt. See
> [...]
>
> Would you
On 2016-11-16 Guido Günther wrote:
> Package: libgnutls30
> Version: 3.5.6-4
> Severity: normal
> Hi,
> 3.5.6 introduced a behaviour change that breaks libvirt. See
[...]
Would you consider this to be a serious issue for libvirt? i.e. should
we block unfixed gnutls from
On Wed, Nov 16, 2016 at 06:54:41PM +0100, Guido Günther wrote:
> Package: libgnutls30
> Version: 3.5.6-4
> Severity: normal
>
> Hi,
> 3.5.6 introuced a behaviour change that breaks libvirt. See
>
> https://lists.gnupg.org/pipermail/gnutls-devel/2016-November/008224.html
>
> and look for
Package: libgnutls30
Version: 3.5.6-4
Severity: normal
Hi,
3.5.6 introuced a behaviour change that breaks libvirt. See
https://lists.gnupg.org/pipermail/gnutls-devel/2016-November/008224.html
and look for "FAIL: virnettlssessiontest".
The upstream discussion is here:
5 matches
Mail list logo