Bug#894860: pdftk: New "upstream" (java-only) version available

2018-04-04 Thread Rogério Brito
Package: pdftk Version: 2.02-4+b2 Severity: wishlist Hi. There is a new, java-only version/conversion of pdftk at https://gitlab.com/marcvinyals/pdftk This would deal with a lot of problems and FTBFS bugs regarding the removal of gcj... Please, package this new version as it would be very hard

Re: OpenJFX 9 integration

2018-04-04 Thread Markus Koschany
Am 04.04.2018 um 10:24 schrieb Emmanuel Bourg: > Le 04/04/2018 à 09:48, Matthias Klose a écrit : > >> I wouldn't spend any time on that. We are moving towards 11, and openjfx is >> split out there. So yes, maybe packages have to drop openjfx support for >> some time. > > +1, Oracle has announced

Re: OpenJFX 9 integration

2018-04-04 Thread tony mancill
On Wed, Apr 04, 2018 at 11:15:59AM +0200, Bas Couwenberg wrote: > On 2018-04-04 10:24, Emmanuel Bourg wrote: > > Le 04/04/2018 à 09:48, Matthias Klose a écrit : > > > > > I wouldn't spend any time on that. We are moving towards 11, and > > > openjfx is > > > split out there. So yes, maybe packages

Re: OpenJFX 9 integration

2018-04-04 Thread Bas Couwenberg
On 2018-04-04 10:24, Emmanuel Bourg wrote: Le 04/04/2018 à 09:48, Matthias Klose a écrit : I wouldn't spend any time on that. We are moving towards 11, and openjfx is split out there. So yes, maybe packages have to drop openjfx support for some time. +1, Oracle has announced last month [1] t

Re: OpenJFX 9 integration

2018-04-04 Thread Emmanuel Bourg
Le 04/04/2018 à 09:48, Matthias Klose a écrit : > I wouldn't spend any time on that. We are moving towards 11, and openjfx is > split out there. So yes, maybe packages have to drop openjfx support for some > time. +1, Oracle has announced last month [1] that JavaFX would be decoupled from Java 1

Re: OpenJFX 9 integration

2018-04-04 Thread Matthias Klose
On 04.04.2018 07:10, Sebastiaan Couwenberg wrote: > On 10/23/2017 01:00 AM, Emmanuel Bourg wrote: >> Le 22/10/2017 à 12:57, Matthias Klose a écrit : >>> (C) looks like the best workaround for now. Looking at at least four >>> security >>> releases per year, and maybe the double amount of package