Add a presubj fragment for reportbug.
authorgregor herrmann <gregoa@debian.org>
Tue, 1 Dec 2009 17:26:38 +0000 (17:26 -0000)
committergregor herrmann <gregoa@debian.org>
Tue, 1 Dec 2009 17:26:38 +0000 (17:26 -0000)
debian/changelog
debian/jabref.install
debian/presubj [new file with mode: 0644]

index 2291972..487661b 100644 (file)
@@ -10,6 +10,7 @@ jabref (2.6~beta2-1) UNRELEASED; urgency=low
   * Refresh patch 01_free_javac.patch.
   * Adjust debian/jabref.links and debian/jabref.install to new jar file.
   * Simplify debian/jabref.dirs.
   * Refresh patch 01_free_javac.patch.
   * Adjust debian/jabref.links and debian/jabref.install to new jar file.
   * Simplify debian/jabref.dirs.
+  * Add a presubj fragment for reportbug.
 
  -- gregor herrmann <gregoa@debian.org>  Tue, 01 Dec 2009 17:46:36 +0100
 
 
  -- gregor herrmann <gregoa@debian.org>  Tue, 01 Dec 2009 17:46:36 +0100
 
index a501ad0..c928a87 100644 (file)
@@ -1,3 +1,4 @@
 build/lib/JabRef-2.6b2.jar usr/share/java
 build/*.xpm usr/share/pixmaps
 debian/jabref.desktop usr/share/applications
 build/lib/JabRef-2.6b2.jar usr/share/java
 build/*.xpm usr/share/pixmaps
 debian/jabref.desktop usr/share/applications
+debian/presubj usr/share/bug/jabref
diff --git a/debian/presubj b/debian/presubj
new file mode 100644 (file)
index 0000000..05462b8
--- /dev/null
@@ -0,0 +1,13 @@
+Quite some bugs reported against JabRef are actually problems with the used
+Java Virtual machine.
+
+Before filing a bug against JabRef please make sure to test with all
+installed JVMs, and provide the output of the jabref wrapper called with the
+debug paramter in the bug report, e.g.:
+
+$ DEBUG_WRAPPER=1 JAVA_HOME=/usr/lib/jvm/java-6-openjdk/ jabref
+$ DEBUG_WRAPPER=1 JAVA_HOME=/usr/lib/jvm/java-6-sun jabref
+
+Please also go through the bug reports against the JVM you're using at
+http://bugs.debian.org/ and check if similar problems are already reported
+there.