Bug#907559: cgview: Does not start
Control: forwarded -1 https://issues.apache.org/jira/browse/BATIK-1239 On Wed, Aug 29, 2018 at 08:23:38PM +0200, Markus Koschany wrote: > > Wouldn't it help more if I simply try to package batik-constants? > > I thought it would be more likely to get a more precise answer from them > because they certainly know their code best. I am not even sure if > batik-constants is a long term solution or if they want to change that > again in the future. Depending on the cgview code it may have been > possible to patch the sources and make them compatible with Batik 1.10 > without packaging batik-constants. If this all sounds too far-fetched, > then packaging batik-constants is the way to go. Thanks for your insight. I have opened an upstream bug report[1] (no idea how to contact upstream otherwise). Kind regards Andreas. [1] https://issues.apache.org/jira/browse/BATIK-1239 -- http://fam-tille.de
Processed: Re: Bug#907559: cgview: Does not start
Processing control commands: > forwarded -1 https://issues.apache.org/jira/browse/BATIK-1239 Bug #907559 [cgview] cgview: Does not start Set Bug forwarded-to-address to 'https://issues.apache.org/jira/browse/BATIK-1239'. -- 907559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907559 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#907559: cgview: Does not start
Am 29.08.2018 um 19:31 schrieb Andreas Tille: [...] >> Maybe you should raise this issue with upstream (Batik and/or cgview) > > Well cgview is not actively maintained (but has quite a number of users) > and what exactly should I say to Batik upstream if they decided to move > it to a noew project? I admit I have no idea what to say and where to > report. > > Wouldn't it help more if I simply try to package batik-constants? I thought it would be more likely to get a more precise answer from them because they certainly know their code best. I am not even sure if batik-constants is a long term solution or if they want to change that again in the future. Depending on the cgview code it may have been possible to patch the sources and make them compatible with Batik 1.10 without packaging batik-constants. If this all sounds too far-fetched, then packaging batik-constants is the way to go. Regards, Markus signature.asc Description: OpenPGP digital signature
Bug#907559: cgview: Does not start
[Bug #907559 in CC which should collect information about this issue] Hi Markus, On Wed, Aug 29, 2018 at 05:16:38PM +0200, Markus Koschany wrote: > the newer Batik version in testing does not provide the XMLConstant > class anymore. They have split the functionality and moved it into a new > project called Batik Constants. > > https://mvnrepository.com/artifact/org.apache.xmlgraphics/batik-constants > > See also https://issues.apache.org/jira/browse/BATIK-1185 Ahhh, thanks for this helpful information. > Maybe you should raise this issue with upstream (Batik and/or cgview) Well cgview is not actively maintained (but has quite a number of users) and what exactly should I say to Batik upstream if they decided to move it to a noew project? I admit I have no idea what to say and where to report. Wouldn't it help more if I simply try to package batik-constants? Kind regards Andreas. -- http://fam-tille.de
Bug#907559: cgview: Does not start
Package: cgview Severity: grave Justification: renders package unusable Hi, cgview in sid/testing does not start while the same code base in stable works perfectly. It just dies with: $ cgview Error: Unable to initialize main class ca.ualberta.stothard.cgview.CgviewIO Caused by: java.lang.NoClassDefFoundError: org/apache/batik/util/XMLConstants Olivier Sallou suspected that the issue could be caused by the version of Batik which is 1.8 in stable and 1.10 in testing/sid. I've checked both source code and JARs for instance like $ grep -wl XMLConstants /usr/share/java/batik* /usr/share/java/batik-all-1.10.jar /usr/share/java/batik-all.jar /usr/share/java/batik-constants-1.10.jar /usr/share/java/batik-constants.jar /usr/share/java/batik.jar /usr/share/java/batik-libs.jar on a machine (testing) where it fails and where cgview works (stable): $ $ grep -wl XMLConstants /usr/share/java/batik* /usr/share/java/batik-1.8.jar /usr/share/java/batik-all-1.8.jar /usr/share/java/batik-all.jar /usr/share/java/batik.jar /usr/share/java/batik-libs-1.8.jar /usr/share/java/batik-libs.jar /usr/share/java/batik-util-1.8.jar /usr/share/java/batik-util.jar The only interesting difference is that on stable (batik-1.8) the symbol is inside /usr/share/java/batik-util.jar while it is not any more in batik 1.10. The tricky thing is that the string XMLConstants itself is not part of the cgview source code so simply changing util in something else that can be found is not possible and may be the bug is simply in one of the dependencies and not in cgview itself. That's why I take the freedom to add Debian Java list in CC of this bug report. Kind regards Andreas. -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cgview depends on: pn default-jre | java8-runtime pn jarwrapper pn libbatik-java pn libcommons-lang-java pn libjargs-java pn libxerces2-java cgview recommends no packages. cgview suggests no packages.
