Re: libfontconfig1 missing in openjdk-8-jre-headless

2015-07-29 Thread Joel Chen
Hi Tony, Thank you for your prompt reply. I had filed a bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793210) last week, but there are no updates of anyone looking into it, whether it will be addressed, and when it will be. Warmest Regards, Joel > On 30 Jul 2015, at 4:03 am, t

Re: libfontconfig1 missing in openjdk-8-jre-headless

2015-07-29 Thread tony
On Thu, Jul 30, 2015 at 03:22:58AM +0800, Joel Chen wrote: > When openjdk-8-jre-headless is used under openjdk-8-jre Docker container, > using Font in Java application triggers NullPointerException. > > This was discussed in https://github.com/docker-library/java/issues/46 issue. > Please includ

libfontconfig1 missing in openjdk-8-jre-headless

2015-07-29 Thread Joel Chen
When openjdk-8-jre-headless is used under openjdk-8-jre Docker container, using Font in Java application triggers NullPointerException. This was discussed in https://github.com/docker-library/java/issues/46 issue. Please include libfontconfig1 into openjdk-8-jre-headless as openjdk-7-jre-headle

Re: OpenJDK 8 transition

2015-07-29 Thread Emmanuel Bourg
Le 29/07/2015 16:36, tmanc...@debian.org a écrit : > Any concerns with an upload of java-commons to experimental sooner than > September? Yes good idea. -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.or

Re: OpenJDK 8 transition

2015-07-29 Thread tmancill
On Tue, Jul 28, 2015 at 09:23:22PM -0700, tony mancill wrote: > On 07/28/2015 12:49 AM, Emmanuel Bourg wrote: > > Hi all, > > > > We are reaching the end of the OpenJDK 8 transition, we are down to one > > package failing to build with the new version, and not the least since > > it's Eclipse. The

Re: OpenJDK 8 transition

2015-07-29 Thread Miguel Landaeta
On Tue, Jul 28, 2015 at 09:49:39AM +0200, Emmanuel Bourg wrote: > Hi all, > > I suggest that we do the switch the first week of September. OpenJDK 7 > will remain available, but ultimately we aim for its removal in Stretch > to lower the maintenance burden. > > What do you think? +1 Wonderful n