Your message dated Sun, 11 Mar 2007 21:01:41 -0700
with message-id <[EMAIL PROTECTED]>
and subject line jamvm: missing file: /usr/lib/logging.properties
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: jamvm
Version: 1.4.4-1
Severity: grave
Justification: renders package unusable
JamVM fails to start:
$ jamvm -jar /path/to/my/app.jar
Exception occurred while VM initialising.
java/io/FileNotFoundException: No such file or directory:
/usr/lib/logging.properties
furthermore, when creating the missing file a NullPointerException
occurs:
$ sudo touch /usr/lib/logging.properties
$ jamvm -jar /path/to/my/app.jar
Exception occurred while VM initialising.
java/lang/NullPointerException
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages jamvm depends on:
ii classpath 2:0.91-3 clean room standard Java libraries
ii classpath-common 2:0.91-3 architecture independent files
ii java-common 0.25 Base of all Java packages
ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries
ii zlib1g 1:1.2.3-13 compression library - runtime
jamvm recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2:0.92-4
FWIW, Nicolas has given a very good analysis of this bug, but his mail was
only sent to control@, not to the bug itself.
Here is his mail:
> Hello,
> Thanks Michel and Matthew for your answers.
> I'm reassigning this bug to classpath. It is fixed upstream in classpath
> 0.92.
> I could reproduce it with classpath 0.91-3, and confirm it's fixed on
> 0.92-4.
> Please find attached a minimal patch to fix this issue (taken from
> upstream).
> classpath's maintainer, jamvm seems to be unusable in some conditions
> because of this bug. It could be worth sending this patch to t-p-u.
> King Regards,
> --
> Nekral
Since the bug is fixed in 2:0.92-4, I'm marking it as such with this
message. I have also re-attached his patch, so that it's clearly visible in
the bug log.
Maintainers, do you agree that this patch is a correct fix for the problem?
Since the new upstream version of classpath in unstable doesn't look
suitable for a freeze exception, can one of you upload this fix to
testing-proposed-updates, or should I prepare an NMU?
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
diff -rauN ../orig/classpath-0.91/debian/changelog ./classpath-0.91/debian/changelog
--- ../orig/classpath-0.91/debian/changelog 2007-03-11 22:46:44.000000000 +0100
+++ ./classpath-0.91/debian/changelog 2007-03-11 23:00:46.000000000 +0100
@@ -1,3 +1,11 @@
+classpath (2:0.91-3.1) unstable; urgency=low
+
+ * Merge change from upstream
+ java/util/logging/LogManager.java (getLevelProperty): Check whether value
+ is null before passing to Level.parse(). Closes: #413116
+
+ -- Nicolas FRANCOIS (Nekral) <[EMAIL PROTECTED]> Sun, 11 Mar 2007 22:59:22 +0100
+
classpath (2:0.91-3) unstable; urgency=low
* Install header files to /usr/include/classpath.
diff -rauN ../orig/classpath-0.91/java/util/logging/LogManager.java ./classpath-0.91/java/util/logging/LogManager.java
--- ../orig/classpath-0.91/java/util/logging/LogManager.java 2006-04-03 10:59:53.000000000 +0200
+++ ./classpath-0.91/java/util/logging/LogManager.java 2007-03-12 00:39:33.000000000 +0100
@@ -700,7 +700,11 @@
{
try
{
- return Level.parse(getLogManager().getProperty(propertyName));
+ String value = getLogManager().getProperty(propertyName);
+ if (value != null)
+ return Level.parse(getLogManager().getProperty(propertyName));
+ else
+ return defaultValue;
}
catch (Exception ex)
{
--- End Message ---
