-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi
I am preparing an upload of japitools that I would like to enter
Squeeze; I have attached the changes from the -2 to the -3 upload and I
have also uploaded the package to mentors.d.n[1].
I have pasted the latest changelog entry for quick reference.
japitools (0.9.5+cvs20060115-3) unstable; urgency=low
* Team upload.
* Added patch from James Page to minimize Ubuntu diff.
- Replaced Depends on default-jdk with headless JREs
- Bumped Standards-Versions to 3.9.1 - no changes required.
(Closes: #590910)
* Added Homepage and Vcs-* fields.
* Removed unused simple-patch system.
* Fixed some hyphens that should have been minus signs in the
manpages.
* Converted source format to 3.0 (quilt).
-- Niels Thykier <niels@thykier.net> Thu, 02 Sep 2010 09:50:53 +0200
Thanks for your time,
~Niels
NB: Please CC me in replies as I am not subscribed.
[1]
http://mentors.debian.net/debian/pool/main/j/japitools/japitools_0.9.5+cvs20060115-3.dsc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEAREIAAYFAkx/W2EACgkQVCqoiq1Ylqzi1QCdEkJL5V++ckaIb7L2+WLg/5IR
XpMAn02ghZB3v/65FtZCEriwhjxCD0+L
=UmIB
-----END PGP SIGNATURE-----
Index: debian/control
===================================================================
--- debian/control (revision 12846)
+++ debian/control (revision 12953)
@@ -4,11 +4,15 @@
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Uploaders: Michael Koch <konqueror@gmx.de>
Build-Depends: debhelper (>= 7), cdbs, ant, default-jdk
-Standards-Version: 3.8.3
+Standards-Version: 3.9.1
+Vcs-Svn: svn://svn.debian.org/svn/pkg-java/trunk/japitools
+Vcs-Browser: http://svn.debian.org/wsvn/pkg-java/trunk/japitools
+Homepage: http://savannah.nongnu.org/projects/japitools/
+
Package: japitools
Architecture: all
-Depends: default-jdk, ${misc:Depends}, ${perl:Depends}
+Depends: default-jre-headless | java2-runtime-headless , ${misc:Depends}, ${perl:Depends}
Description: Java API compatibility testing tools
It consists of two simple tools designed to test for compatibility between
Java APIs. They were originally designed for testing free implementations
Index: debian/japize.1
===================================================================
--- debian/japize.1 (revision 12846)
+++ debian/japize.1 (revision 12953)
@@ -60,7 +60,7 @@
.TP
\fB+\fP|\fB-\fR<pkgpath\fR>\fP
-To specify which classes are included, use +pkgpath to add pkgpaths to be scanned and -pkgpath to exclude sub-pkgpaths of these. You MUST specify at least one +pkgpath option to specify which pkgpath to include, otherwise Japize could happily scan through all the zipfiles and directories but not actually process any of the classes. Since that would be a useless thing to do, japize gives an error instead.
+To specify which classes are included, use +pkgpath to add pkgpaths to be scanned and \-pkgpath to exclude sub-pkgpaths of these. You MUST specify at least one +pkgpath option to specify which pkgpath to include, otherwise Japize could happily scan through all the zipfiles and directories but not actually process any of the classes. Since that would be a useless thing to do, japize gives an error instead.
A "pkgpath" refers to either a package (which includes, by implication, all sub-packages of it) or a single class. A pkgpath for a package looks like "com.foo.pkg.sub," and a pkgpath for a class looks like "com.foo.pkg,Cls". The existence and placement of the comma indicates unambiguously which type of path is intended.
@@ -70,15 +70,15 @@
Sun's JDK 1.1 includes classes in java.awt.peer and in java.text.resources that are not part of the public API, even though they are public classes; however, every other class in the java.* package hierarchy is part of the public API. The syntax to construct a useful jdk11.japi.gz would therefore be:
-$ japize as jdk11 apis classes.zip +java -java.awt.peer -java.text.resources
+$ japize as jdk11 apis classes.zip +java \-java.awt.peer \-java.text.resources
Note that since all pkgpath arguments here are packages, you could save a small amount of processing by doing this instead:
-$ japize as jdk11 packages classes.zip +java -java.awt.peer -java.text.resources
+$ japize as jdk11 packages classes.zip +java \-java.awt.peer \-java.text.resources
or even this:
-$ japize as jdk11 explicitly classes.zip +java, -java.awt.peer, -java.text.resources,
+$ japize as jdk11 explicitly classes.zip +java, \-java.awt.peer, \-java.text.resources,
.SH SEE ALSO
.BR japicompat (1)
Index: debian/japicompat.1
===================================================================
--- debian/japicompat.1 (revision 12846)
+++ debian/japicompat.1 (revision 12953)
@@ -42,7 +42,7 @@
.TP
\fB\-j\fP
-generates output in raw machine readable form. The format produced is called "japio" format, and by convention should be saved with a ".japio" file extension. The standalone japiotext and japiohtml utilities can be used to convert this format into html or text (actually, japicompat calls japiotext or japiohtml internally if the -h or -t flags are used). Japio files can also be used with the -i flag to support ignoring errors caused by incompatibilities between JDK versions.
+generates output in raw machine readable form. The format produced is called "japio" format, and by convention should be saved with a ".japio" file extension. The standalone japiotext and japiohtml utilities can be used to convert this format into html or text (actually, japicompat calls japiotext or japiohtml internally if the \-h or \-t flags are used). Japio files can also be used with the \-i flag to support ignoring errors caused by incompatibilities between JDK versions.
.TP
\fB\-w\fP
@@ -54,7 +54,7 @@
.TP
\fB\-o\fR <outfile\fR>\fP
-Send the output to <outfile> instead of stdout. The format of this file depends on the -h, -t and -j flags.
+Send the output to <outfile> instead of stdout. The format of this file depends on the \-h, \-t and \-j flags.
.TP
\fB\-i\fR <ignorefiles\fR>\fP
@@ -62,15 +62,15 @@
Unfortunately Sun has not followed their own binary compatibility rules between JDK releases, let alone the expanded rules that japicompat tests for. So when you run a comparison between JDK 1.1 and your implementation, you will get spurious error reports when you're compatible with 1.4 but not 1.1.
-Obviously what you really want is to ignore errors like this, and japicompat provides a way to do so. First, run a comparison between 1.1 and 1.4 using the -j switch. Then run the comparison between 1.1 and your implementation, passing the "-i" option with the output of the previous run. For example:
+Obviously what you really want is to ignore errors like this, and japicompat provides a way to do so. First, run a comparison between 1.1 and 1.4 using the \-j switch. Then run the comparison between 1.1 and your implementation, passing the "\-i" option with the output of the previous run. For example:
-$ japicompat -jo ignore-11-14.japio jdk11.japi.gz jdk14.japi.gz
+$ japicompat \-jo ignore-11-14.japio jdk11.japi.gz jdk14.japi.gz
.br
-$ japicompat -ho jdk11-myimpl.html -i ignore-11-14.japio jdk11.japi.gz myimpl.japi.gz
+$ japicompat \-ho jdk11-myimpl.html \-i ignore-11-14.japio jdk11.japi.gz myimpl.japi.gz
You can also get the same effect by running:
-$ japicompat -ho jdk11-myimpl.html -i jdk14.japi.gz jdk11.japi.gz myimpl.japi.gz
+$ japicompat \-ho jdk11-myimpl.html \-i jdk14.japi.gz jdk11.japi.gz myimpl.japi.gz
This is obviously simpler and quicker to type, but requires the comparison between jdk11 and jdk14 to be run every single time. Making the japio file manually allows for it to be saved and used again the next time, which lets japicompat run about twice as fast.
@@ -85,7 +85,7 @@
.br
$ japicompat myimpl.japi.gz jdk12.japi.gz
-It is probably impossible to make an implementation that passes both these tests, since Sun's own JDK1.2 produces numerous errors when tested against JDK1.1. See the discussion of the -i option above for a way to cope with this situation.
+It is probably impossible to make an implementation that passes both these tests, since Sun's own JDK1.2 produces numerous errors when tested against JDK1.1. See the discussion of the \-i option above for a way to cope with this situation.
Either compressed (.japi.gz) or uncompressed (.japi) files can be passed to japicompat: The file extension is used to determine whether or not to pipe input through gzip or not.
Index: debian/changelog
===================================================================
--- debian/changelog (revision 12846)
+++ debian/changelog (revision 12953)
@@ -1,3 +1,18 @@
+japitools (0.9.5+cvs20060115-3) unstable; urgency=low
+
+ * Team upload.
+ * Added patch from James Page to minimize Ubuntu diff.
+ - Replaced Depends on default-jdk with headless JREs
+ - Bumped Standards-Versions to 3.9.1 - no changes required.
+ (Closes: #590910)
+ * Added Homepage and Vcs-* fields.
+ * Removed unused simple-patch system.
+ * Fixed some hyphens that should have been minus signs in the
+ manpages.
+ * Converted source format to 3.0 (quilt).
+
+ -- Niels Thykier <niels@thykier.net> Thu, 02 Sep 2010 09:50:53 +0200
+
japitools (0.9.5+cvs20060115-2) unstable; urgency=low
* (Build-)Depends on default-jdk.
Index: debian/rules
===================================================================
--- debian/rules (revision 12846)
+++ debian/rules (revision 12953)
@@ -3,7 +3,6 @@
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/class/ant.mk
-include /usr/share/cdbs/1/rules/simple-patchsys.mk
export UPSTREAM_VERSION = $(shell head -1 debian/changelog | cut -f2 -d\( | cut -f1 -d\) | cut -f1 -d\-)
Index: debian/source/format
===================================================================
--- debian/source/format (revision 0)
+++ debian/source/format (revision 12953)
@@ -0,0 +1 @@
+3.0 (quilt)
Attachment:
japitools_2-3.patch.sig
Description: Binary data