Bug#828451: Upstream are aware but stuck

[Sebastian Andrzej Siewior]

On 2017-12-16 12:55:35 [+], deb...@fau.xxx wrote:
> Upstream are aware of this issue, but quite stuck on it, by the look of
> it:
> 
>  * https://github.com/netty/netty-tcnative/issues/263
>  * https://github.com/netty/netty/issues/6320
> 
> This is going to be a problem, as netty-tcnative can't be removed from
> testing, as it chains to fop, which half the world build-deps on for docs.

My understanding is that the only open issue is the renegotiation that is no
longer supported/ possible. If that is that the case then I suggest to drop
that and be done with it. Renegotiation initiated by the client is something
one does not want (since it may cause high load on the server). Also I don't
know anything *good* it will bring.

Sebastian

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#828451: Upstream are aware but stuck

[debian]

Upstream are aware of this issue, but quite stuck on it, by the look of
it:

 * https://github.com/netty/netty-tcnative/issues/263
 * https://github.com/netty/netty/issues/6320

This is going to be a problem, as netty-tcnative can't be removed from
testing, as it chains to fop, which half the world build-deps on for docs.

 * netty-tcnative
 * netty
 * jython
 * batik
 * fop
 * half the world

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.