Bug#852253: marked as done (kryo-serializers: FTBFS (Cannot access central (https://repo.maven.apache.org/maven2) in offline mode))

2017-02-20 Thread Debian Bug Tracking System
Your message dated Tue, 21 Feb 2017 06:14:59 +0100 with message-id <0f6453df-0542-9c03-60df-4476da961...@debian.org> and subject line Re: kryo-serializers: no longer FTBFS in stretch has caused the Debian Bug report #852253, regarding kryo-serializers: FTBFS (Cannot access central

Bug#855324: pdfsam fails to start

2017-02-20 Thread Markus Koschany
FYI, I had a look at the latest version and worked on a new debian package which can be found at https://anonscm.debian.org/cgit/pkg-java/pdfsam.git (might take a few minutes until it is accessible) pdfsam is now a JavaFX application and requires at least https://github.com/torakiki/sejda

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

2017-02-20 Thread Markus Koschany
On 20.02.2017 17:45, Salvatore Bonaccorso wrote: [...] > Sorry for the delay (due to various circumstances). The fix looks sane > to me. Assuming the fix could have been tested as well, please do > upload to security-master. > Hi, no problem. I have just uploaded both packages to

Bug#855324: pdfsam fails to start

2017-02-20 Thread Philip Rinn
On 20.02.2017 at 18:25, gregor herrmann wrote: > On Mon, 20 Feb 2017 09:20:17 -0800, tony mancill wrote: > >>> With "0" I still get an empty greyish window and nothing more. >> Ugh! I'm just guessing, but I suspect you are now seeing a *different* >> issue related to one of the AWT race

Bug#855324: pdfsam fails to start

2017-02-20 Thread Philip Rinn
On 20.02.2017 at 18:20, tony mancill wrote: > On Sun, Feb 19, 2017 at 11:36:05PM +0100, gregor herrmann wrote: >> On Sun, 19 Feb 2017 18:09:22 +0100, Philip Rinn wrote: >> >>> On 19.02.2017 at 04:56, gregor herrmann wrote: After this change, pdfsam starts for me and shows me an empty white

Bug#855324: pdfsam fails to start

2017-02-20 Thread gregor herrmann
On Mon, 20 Feb 2017 09:20:17 -0800, tony mancill wrote: > > With "0" I still get an empty greyish window and nothing more. > Ugh! I'm just guessing, but I suspect you are now seeing a *different* > issue related to one of the AWT race conditions we seem to encounter > from time to time. Quite

Bug#855324: pdfsam fails to start

2017-02-20 Thread tony mancill
On Sun, Feb 19, 2017 at 11:36:05PM +0100, gregor herrmann wrote: > On Sun, 19 Feb 2017 18:09:22 +0100, Philip Rinn wrote: > > > On 19.02.2017 at 04:56, gregor herrmann wrote: > > > After this change, pdfsam starts for me and shows me an empty white > > > window (or grey-ish) with nothing in it. >

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

2017-02-20 Thread Salvatore Bonaccorso
Hi Markus, On Sat, Feb 18, 2017 at 07:53:33PM +0100, Markus Koschany wrote: > 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

Bug#854551: 400 errors caused by 7.0.28-4+deb7u10

2017-02-20 Thread Markus Koschany
On 20.02.2017 17:20, Samuel Wolf wrote: > A fixed version for Jessie will released as deb8u9 with the next point > release? The security team will release a regression update soon. Regards, Markus signature.asc Description: OpenPGP digital signature __ This is the maintainer address of

Bug#854551: 400 errors caused by 7.0.28-4+deb7u10

2017-02-20 Thread Samuel Wolf
A fixed version for Jessie will released as deb8u9 with the next point release? __ This is the maintainer address of Debian's Java team . Please use debian-j...@lists.debian.org for discussions and questions.

Bug#855262: Set System Encoding as UTF-8

2017-02-20 Thread Emmanuel Bourg
Le 16/02/2017 à 08:28, 殷啟聰 a écrit : > 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 "©". > > Currently we need to add `-Dfile.encoding=UTF-8` to > `override_dh_auto_build`. Why not