Bug#874276: ca-certificates-java: fails to install on armhf: Error: missing `server' JVM at `/usr/lib/jvm/java-8-openjdk-armhf/jre/lib/arm/server/libjvm.so'

2017-09-26 Thread Sebastiaan Couwenberg
Is anyone working on this issue? It's preventing the build of many packages on armhf and by extension their transitions. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 __ This is the maintainer address of Debian's Java

Bug#853134: CVE-2017-5617: svgSalamander

2017-02-03 Thread Sebastiaan Couwenberg
On 02/02/2017 07:09 PM, Sebastiaan Couwenberg wrote: > On 02/02/2017 07:44 AM, Sebastiaan Couwenberg wrote: >> On 02/01/2017 10:08 AM, Bas Couwenberg wrote: >>> On 2017-02-01 09:35, Bas Couwenberg wrote: >>>> Including the JOSM developers (josm-...@openstreetmap.org)

Bug#853134: CVE-2017-5617: svgSalamander

2017-02-02 Thread Sebastiaan Couwenberg
On 02/02/2017 07:44 AM, Sebastiaan Couwenberg wrote: > Control: tags -1 pending > > On 02/01/2017 10:08 AM, Bas Couwenberg wrote: >> On 2017-02-01 09:35, Bas Couwenberg wrote: >>> Including the JOSM developers (josm-...@openstreetmap.org) is also a >>> good

Bug#853134: CVE-2017-5617: svgSalamander

2017-02-01 Thread Sebastiaan Couwenberg
Control: tags -1 pending On 02/01/2017 10:08 AM, Bas Couwenberg wrote: > On 2017-02-01 09:35, Bas Couwenberg wrote: >> Including the JOSM developers (josm-...@openstreetmap.org) is also a >> good idea, they (and Vincent Privat in particular) have contributed >> patches to svgSalamander recently. >

Bug#835430: libphonenumber: FTBFS in unstable (org.easymock:easymockclassextension:jar:debian artifact not available)

2016-08-25 Thread Sebastiaan Couwenberg
On 08/25/16 20:02, Markus Koschany wrote: I think the issue is not unrelated to protobuf 3.0.0. Yesterday I filed https://bugs.debian.org/835358 because protobuf used a wrong pom.xml file which provides important information like groupids or artifactids. So this bug got resolved today but now I

Bug#801475: freeplane: Fails to build with JMapViewer 1.11

2015-10-18 Thread Sebastiaan Couwenberg
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 18-10-15 17:00, tony mancill wrote: > On 10/18/2015 04:58 AM, Sebastiaan Couwenberg wrote: >> On Fri, 16 Oct 2015 20:49:12 +0200 Felix Natter wrote: >>> I added a patch for JMapViewer-1.11 compatibility: >>> http://

Bug#801475: freeplane: Fails to build with JMapViewer 1.11

2015-10-18 Thread Sebastiaan Couwenberg
Hi Felix, I missed this update to the bugreport. On Fri, 16 Oct 2015 20:49:12 +0200 Felix Natter wrote: > I added a patch for JMapViewer-1.11 compatibility: > http://anonscm.debian.org/cgit/pkg-java/freeplane.git > > I've set the distribution to experimental since it should probably be > uploa

Bug#801475: freeplane: Fails to build with JMapViewer 1.11

2015-10-18 Thread Sebastiaan Couwenberg
Control: severity -1 serious With the upload of jmapviewer (1.11+dfsg-1) to unstable today freeplane now FTBFS. Please update the openmaps plugin to support JMapViewer 1.11 or consider adding skip_openmaps=true to debian/ant.properties. Kind Regards, Bas __ This is the maintainer address of De

Bug#780179: libmetadata-extractor-java: Please package latest upstream release

2015-05-30 Thread Sebastiaan Couwenberg
On 05/30/2015 10:31 AM, Emmanuel Bourg wrote: > Tika uses metadata-extractor 2.6 up to the version 1.7, and the latest > version 1.8 switched to metadata-extractor 2.8. Do you know if JOSM is > compatible with this version? Not explicitly, but looking at the release notes for 2.8 I don't see any A

Bug#780179: libmetadata-extractor-java: Please package latest upstream release

2015-05-16 Thread Sebastiaan Couwenberg
Control: reopen -1 Hi Emmanuel, On 05/05/2015 06:35 PM, Sebastiaan Couwenberg wrote: > On 03/10/2015 06:14 PM, Emmanuel Bourg wrote: >> Le 10/03/2015 17:50, Sebastiaan Couwenberg a écrit : >> >>> I can take care of gpsprune and josm. >> >> Thank you, I'

Bug#779256: jaffl: unit tests during build time are failing

2015-05-13 Thread Sebastiaan Couwenberg
On Wed, 25 Feb 2015 20:26:11 -0300 Miguel Landaeta wrote: > Package: src:jaffl > Version: 0.5.9-5 > Severity: normal > > This package looks unmaintained and kinda abandoned by upstream. It looks like upstream renamed the project, it lives on GitHub: https://github.com/jnr/jnr-ffi The 0.5 branch

Bug#780179: libmetadata-extractor-java: Please package latest upstream release

2015-05-05 Thread Sebastiaan Couwenberg
On 03/10/2015 06:14 PM, Emmanuel Bourg wrote: > Le 10/03/2015 17:50, Sebastiaan Couwenberg a écrit : > >> I can take care of gpsprune and josm. > > Thank you, I'll look into Tika. > > >> The next version to be released next month will be compatible, its v

Bug#780179: libmetadata-extractor-java: Please package latest upstream release

2015-04-01 Thread Sebastiaan Couwenberg
On 03/10/2015 06:14 PM, Emmanuel Bourg wrote: > Le 10/03/2015 17:50, Sebastiaan Couwenberg a écrit : >> The next version to be released next month will be compatible, its version >> is not yet known, as it's based on the SVN revision. >> >> The current version and

Bug#780179: libmetadata-extractor-java: Please package latest upstream release

2015-03-11 Thread Sebastiaan Couwenberg
On 03/10/2015 06:14 PM, Emmanuel Bourg wrote: > Le 10/03/2015 17:50, Sebastiaan Couwenberg a écrit : > >> I can take care of gpsprune and josm. > > Thank you, I'll look into Tika. I've patched gpsprune to build with metadata-extractor 2.7.2, and uploaded gpsprune

Bug#780179: libmetadata-extractor-java: Please package latest upstream release

2015-03-10 Thread Sebastiaan Couwenberg
> I'm going to upload the version 2.7.2 to experimental. It breaks > libtika-java and gpsprune, some coordination will be required to > transition smoothly. Thanks for the quick response. I can take care of gpsprune and josm. > What is the first version of josm compatible with this version so I

Bug#770608: maven: FTBFS: maven-install-plugin or one of its dependencies could not be resolved

2014-11-30 Thread Sebastiaan Couwenberg
Control: tags -1 patch Hi Daniel, This RC bug is threatening the removal of quite a number of Java packages that depend on maven. I've reproduced the issue you reported in an up-to-date sid chroot. During the maven-compile phase the build attempts to download maven-install-plugin-2.3.pom which