Re: Tomcat 8 transition complete

2016-12-09 Thread Emmanuel Bourg
Le 9/12/2016 à 09:43, Timo Aaltonen a écrit : > a test-rebuild of reverse build-depends before the migration would've > been nice to catch these well in advance ;) You are right, sorry, I didn't realize dogtag and tomcatjss were so tightly coupled with Tomcat internals. > getting rid of ServerS

Re: Tomcat 8 transition complete

2016-12-09 Thread Timo Aaltonen
On 09.12.2016 10:11, Emmanuel Bourg wrote: > Hi Timo, > > Le 9/12/2016 à 08:56, Timo Aaltonen a écrit : > >> 8.5 broke tomcatjss and dogtag, and it doesn't look like upstream will >> be able to fix them in about two weeks which is when uploads should >> happen in time for stretch.. > > What issu

Re: Tomcat 8 transition complete

2016-12-09 Thread Timo Aaltonen
On 06.11.2016 00:46, Emmanuel Bourg wrote: > Hi all, > > I'm pleased to announce that the transition to Tomcat 8 is now complete. > The tomcat7 source package still exists but builds only the Servlet API > 3.0. This version of the Servlet API is no longer used in sid, but I > think it's a good ide

Re: Tomcat 8 transition complete

2016-12-09 Thread Emmanuel Bourg
Hi Timo, Le 9/12/2016 à 08:56, Timo Aaltonen a écrit : > 8.5 broke tomcatjss and dogtag, and it doesn't look like upstream will > be able to fix them in about two weeks which is when uploads should > happen in time for stretch.. What issues did you get? > Any chance of tomcat8.0? The move to

Re: Tomcat 8 transition complete

2016-11-08 Thread Thorsten Glaser
On Mon, 7 Nov 2016, Emmanuel Bourg wrote: > Ok I think I get it. There are actually 4 websocket implementations: […] > you can simply ignore the Jetty 8/9 and Tomcat 7 specific code. You can > safely patch guacamole/pom.xml and modify the configuration of the > maven-compiler-plugin to ignore the

Re: Tomcat 8 transition complete

2016-11-06 Thread Emmanuel Bourg
Le 7/11/2016 à 07:47, Thorsten Glaser a écrit : > AIUI we want to dump it into a Tomcat and be done with it, > so that means Tomcat 8. Upstream said that it would work > in Tomcat 8 after building it against Tomcat 7 when the > Fedora packager complained about similar issues (I already > fixed an

Re: Tomcat 8 transition complete

2016-11-06 Thread Thorsten Glaser
On Mon, 7 Nov 2016, Emmanuel Bourg wrote: > I see that there are 3 websocket implementations, for Jetty 8, Jetty 9 Yes, that was confusing. > and Tomcat 7. Are the three absolutely needed? Is supporting only Jetty > 9 a viable alternative? AIUI we want to dump it into a Tomcat and be done with

Re: Tomcat 8 transition complete

2016-11-06 Thread Emmanuel Bourg
Le 6/11/2016 à 23:35, Thorsten Glaser a écrit : > Unfortunately, the new version of guacamole I’ve been working > with Natureshadow on (with my Teckids hat worn) requires the > websocket API from libtomcat7-java. > > I don’t know enough to comment on this (I just barely made the > package compile

Re: Tomcat 8 transition complete

2016-11-06 Thread Thorsten Glaser
On Sat, 5 Nov 2016, Emmanuel Bourg wrote: > I'm pleased to announce that the transition to Tomcat 8 is now complete. > The tomcat7 source package still exists but builds only the Servlet API > 3.0. This version of the Servlet API is no longer used in sid, but I Unfortunately, the new version of g