kryo-serializers is marked for autoremoval from testing

kryo-serializers 0.22-3 is marked for autoremoval from testing on 2017-02-22 It is affected by these RC bugs: 852253: kryo-serializers: FTBFS (Cannot access central (https://repo.maven.apache.org/maven2) in offline mode) __ This is the maintainer address of Debian's Java team

Bug#855262: Set System Encoding as UTF-8

On Thu, Feb 16, 2017 at 03:28:20PM +0800, 殷啟聰 wrote: > Package: gradle-debian-helper > Version: 1.5.1 > Severity: wishlist > > On Debian Buildd the default encoding on Java is usually not UTF-8, > which results in compilation failure on source files containing CJK > symbols or even a "©". > >

tomcat8_8.0.14-1+deb8u7_amd64.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 13 Feb 2017 10:34:43 +0100 Source: tomcat8 Binary: tomcat8-common tomcat8 tomcat8-user libtomcat8-java libservlet3.1-java libservlet3.1-java-doc tomcat8-admin tomcat8-examples tomcat8-docs Architecture: source

Bug#855324: pdfsam fails to start

On Sat, 18 Feb 2017 18:25:32 -0800, tony mancill wrote: > Change the value in the element ~/.pdfsam/config.xml to '1': > > ... > > > 1 >^ >| > ... After this change, pdfsam starts for me and shows me an empty white window (or grey-ish) with nothing in

Bug#851304: marked as done (tomcat8 use 100% cpu time)

Your message dated Sat, 18 Feb 2017 23:32:21 + with message-id and subject line Bug#851304: fixed in tomcat8 8.0.14-1+deb8u7 has caused the Debian Bug report #851304, regarding tomcat8 use 100% cpu time to be marked as done. This means that you claim that

Bug#854551: marked as done (tomcat7: Remote https GET requests to Tomcat7 with default config cause server cpu to jump 100% forever)

Your message dated Sat, 18 Feb 2017 23:32:20 + with message-id and subject line Bug#854551: fixed in tomcat7 7.0.56-3+deb8u8 has caused the Debian Bug report #854551, regarding tomcat7: Remote https GET requests to Tomcat7 with default config cause server

Bug#855324: pdfsam fails to start

On Fri, Feb 17, 2017 at 12:30:47PM +0100, Philip Rinn wrote: > If you could point me to some document or tell me how to debug further, I'm > willing to so but I need some guidance... Hi Philip, As a work-around, would you mind trying to following to see if it resolves the problem for you?

Bug#851304: tomcat8 use 100% cpu time

Hi Markus, On Fri, Feb 17, 2017 at 10:19:18PM +0100, Markus Koschany wrote: > On 17.02.2017 22:09, Salvatore Bonaccorso wrote: > > Hi Markus, hi Emmanuel, > > > > On Mon, Feb 13, 2017 at 10:48:20AM +0100, Markus Koschany wrote: > >> On 13.02.2017 08:34, Moritz Mühlenhoff wrote: > >>> On Sun, Feb

tomcat7_7.0.56-3+deb8u8_amd64.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 13 Feb 2017 10:16:57 +0100 Source: tomcat7 Binary: tomcat7-common tomcat7 tomcat7-user libtomcat7-java libservlet3.0-java libservlet3.0-java-doc tomcat7-admin tomcat7-examples tomcat7-docs Architecture: source

Bug#854551: Bug#851304: tomcat8 use 100% cpu time

On 18.02.2017 13:21, Salvatore Bonaccorso wrote: [...] > No problem. Thanks for noticing, can you let us know as usual when you > have a debdiff ready for the regression update? > > I tend to see this as regression update for the previous DSA, so no > need for a new CVE id. But let me know if

Bug#855324: pdfsam fails to start

On Fri, Feb 17, 2017 at 12:30:47PM +0100, Philip Rinn wrote: > Hi, > > I tired to locate the error - but I'm no Java expert so I might be totally > off... > > Reading the log, I think it throws an error here: > >