Bug#863337: visualvm: Typos in launcher script - does not start anymore

2017-07-05 Thread Emmanuel Bourg
Le 5/07/2017 à 13:07, Erich Schubert a écrit : > To me, these appear to be obvious typos; independent of whether you can > reproduce them, or not... This was changed by upstream in the latest version: https://github.com/visualvm/visualvm/commit/d6026fc5 These options are passed to nbexec,

Bug#863337: visualvm: Typos in launcher script - does not start anymore

2017-07-05 Thread Erich Schubert
Hi, I will try to double-check this, but I'm constantly short on time these days. I didn't modify visualvm.conf But by any means, by looking at the source don't you think it should be -J rather than -L? Even if e.g. the bug only appears because Java 9 fails to start with -L, whereas maybe java 8

Bug#863337: visualvm: Typos in launcher script - does not start anymore

2017-05-29 Thread tony mancill
On Thu, May 25, 2017 at 04:50:56PM +0200, Erich Schubert wrote: > Package: visualvm > Version: 1.3.9-1 > Severity: grave > Justification: renders package unusable > > visualvm does not start anymore with the error: > Unknown option -L-XX:PermSize=32m > Versions of packages visualvm depends

Bug#863337: visualvm: Typos in launcher script - does not start anymore

2017-05-28 Thread Chris Lamb
Hey Erich, > visualvm: Typos in launcher script - does not start anymore I can't seem to reproduce this on a fresh stretch or sid chroot. Can you paste your /etc/visualvm/visualvm.conf? Is this an upgrade? My chroots seem to be using OpenJDK if that helps. Regards, -- ,''`. : :'

Bug#863337: visualvm: Typos in launcher script - does not start anymore

2017-05-25 Thread Erich Schubert
Package: visualvm Version: 1.3.9-1 Severity: grave Justification: renders package unusable visualvm does not start anymore with the error: Unknown option -L-XX:PermSize=32m This is caused by a trivial typo in the start script, which supposedly should use -J (like "Java options") instead of -L