Bug#693970: tpu: libitext-java/2.1.7-3+deb7u1
On 2012-12-19 19:10, Julien Cristau wrote:
On Thu, Nov 22, 2012 at 13:45:57 +0100, Niels Thykier wrote:
Unfortunately, it turns out that libitext-java declares no
dependnecies relations (except libitext-java-gcj) in testing at all,
which is obvously wrong.
In sid, I have taken the liberty of properly fixing this by using
javahelper to compute the proper dependency relations automatically
(as that version cannot migrate to testing anyway being built against
the bouncycastle in sid).
The question is then, should I backport the changes for
auto-generating the dependencies and insert the upper bound on the
bouncycastle dependency -OR- should I simply manually hardcode all the
missing dependencies in the tpu upload?
The former seems safer, so I think I'd go with that.
Done; I took the liberty of uploading to TPU already given you have
basically already seen the diff (modulo the version and some version
boubds). The full testing - tpu diff is attached as itext_tpu.diff and
I also included an interdiff.
I have attached the debdiff between libitext-java in sid and testing
to give you an idea of the changes involved. In case you are
wondering about the explicit version'ed dependencies in the diff, it
is because the tools involved are not able to properly give version
bounds on the dependencies[0].
~Niels
[0] Sadly, Java packages do not have a shlibs/symbols system (nor the
rename package on ABI breakage-proceedure).
They really should start doing at least the latter.
Cheers,
Julien
Yeah, just need to reschool most of our Java developers first. Though
I suspect if we did manage that, we could make Java libraries smooth
updateable.
~Niels
itext_tpu.diff
Description: application/wine-extension-patch
diff -u libitext-java-2.1.7/debian/changelog
libitext-java-2.1.7/debian/changelog
--- libitext-java-2.1.7/debian/changelog2012-09-15 09:02:39.0
+
+++ libitext-java-2.1.7/debian/changelog2012-12-20 13:44:58.0
+0100
@@ -1,11 +1,11 @@
-libitext-java (2.1.7-4) unstable; urgency=low
+libitext-java (2.1.7-3+deb7u1) wheezy; urgency=low
* Team upload.
* Add missing the Class-Path for the java packages.
- Use javahelper to set the classpath.
- Use javahelper to compute dependencies.
- * Add versioned (Build-)Dependency on libbcprov-java due to
-#687694.
+ * Add versioned upper bound on (Build-)Dependency on libbcprov-java
+due to #687694.
-- Niels Thykier ni...@thykier.net Sat, 15 Sep 2012 11:02:37 +0200
diff -u libitext-java-2.1.7/debian/control libitext-java-2.1.7/debian/control
--- libitext-java-2.1.7/debian/control 2012-09-15 08:58:02.0 +
+++ libitext-java-2.1.7/debian/control 2012-12-20 13:44:02.0 +0100
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Debian Java Maintainers
pkg-java-maintain...@lists.alioth.debian.org
Uploaders: Adriaan Peeters apeet...@lashout.net, Torsten Werner
twer...@debian.org
-Build-Depends: debhelper (= 9), cdbs, default-jdk, ant, libbcprov-java (=
1.46),
+Build-Depends: debhelper (= 9), cdbs, default-jdk, ant, libbcprov-java (
1.45~),
libbcmail-java, libbctsp-java, libdom4j-java, libpdfrenderer-java,
gcj-native-helper,
javahelper (= 0.43)
Standards-Version: 3.9.3
@@ -13,7 +13,7 @@
Package: libitext-java
Architecture: all
-Depends: ${misc:Depends}, libbcprov-java (= 1.46), ${java:Depends}
+Depends: ${misc:Depends}, libbcprov-java ( 1.45~), ${java:Depends}
Suggests: libitext-java-gcj
Description: Java Library to create and manipulate PDF on the fly
iText is a library that allows you to generate PDF files on the fly.
Bug#693970: tpu: libitext-java/2.1.7-3+deb7u1
Hi, I am still waiting for responds on the below. ~Niels On 2012-11-22 13:45, Niels Thykier wrote: Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: tpu Hi, A user reported an issue with libitext-java in testing (#687692). In short, the problem was an ABI issue in bouncycastle. The diff between bouncycastle/1.44 and bouncycastle/1.46 is far to large to sanely review and libitext-java is the only package which has any (reported) issues caused by the ABI change. Therefore, simply rebuilding libitext-java in testing (with an upper bound on its dependency) should suffice for this particular problem. Unfortunately, it turns out that libitext-java declares no dependnecies relations (except libitext-java-gcj) in testing at all, which is obvously wrong. In sid, I have taken the liberty of properly fixing this by using javahelper to compute the proper dependency relations automatically (as that version cannot migrate to testing anyway being built against the bouncycastle in sid). The question is then, should I backport the changes for auto-generating the dependencies and insert the upper bound on the bouncycastle dependency -OR- should I simply manually hardcode all the missing dependencies in the tpu upload? I have attached the debdiff between libitext-java in sid and testing to give you an idea of the changes involved. In case you are wondering about the explicit version'ed dependencies in the diff, it is because the tools involved are not able to properly give version bounds on the dependencies[0]. ~Niels [0] Sadly, Java packages do not have a shlibs/symbols system (nor the rename package on ABI breakage-proceedure). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693970: tpu: libitext-java/2.1.7-3+deb7u1
On Thu, Nov 22, 2012 at 13:45:57 +0100, Niels Thykier wrote: Unfortunately, it turns out that libitext-java declares no dependnecies relations (except libitext-java-gcj) in testing at all, which is obvously wrong. In sid, I have taken the liberty of properly fixing this by using javahelper to compute the proper dependency relations automatically (as that version cannot migrate to testing anyway being built against the bouncycastle in sid). The question is then, should I backport the changes for auto-generating the dependencies and insert the upper bound on the bouncycastle dependency -OR- should I simply manually hardcode all the missing dependencies in the tpu upload? The former seems safer, so I think I'd go with that. I have attached the debdiff between libitext-java in sid and testing to give you an idea of the changes involved. In case you are wondering about the explicit version'ed dependencies in the diff, it is because the tools involved are not able to properly give version bounds on the dependencies[0]. ~Niels [0] Sadly, Java packages do not have a shlibs/symbols system (nor the rename package on ABI breakage-proceedure). They really should start doing at least the latter. Cheers, Julien signature.asc Description: Digital signature
Bug#693970: tpu: libitext-java/2.1.7-3+deb7u1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: tpu
Hi,
A user reported an issue with libitext-java in testing (#687692). In
short, the problem was an ABI issue in bouncycastle.
The diff between bouncycastle/1.44 and bouncycastle/1.46 is far to
large to sanely review and libitext-java is the only package which has
any (reported) issues caused by the ABI change.
Therefore, simply rebuilding libitext-java in testing (with an upper
bound on its dependency) should suffice for this particular problem.
Unfortunately, it turns out that libitext-java declares no
dependnecies relations (except libitext-java-gcj) in testing at all,
which is obvously wrong.
In sid, I have taken the liberty of properly fixing this by using
javahelper to compute the proper dependency relations automatically
(as that version cannot migrate to testing anyway being built against
the bouncycastle in sid).
The question is then, should I backport the changes for
auto-generating the dependencies and insert the upper bound on the
bouncycastle dependency -OR- should I simply manually hardcode all the
missing dependencies in the tpu upload?
I have attached the debdiff between libitext-java in sid and testing
to give you an idea of the changes involved. In case you are
wondering about the explicit version'ed dependencies in the diff, it
is because the tools involved are not able to properly give version
bounds on the dependencies[0].
~Niels
[0] Sadly, Java packages do not have a shlibs/symbols system (nor the
rename package on ABI breakage-proceedure).
Base version: libitext-java_2.1.7-3 from testing
Target version: libitext-java_2.1.7-4 from unstable
No hints in place.
changelog | 11 +++
control | 11 ++-
rules | 21 -
3 files changed, 29 insertions(+), 14 deletions(-)
gpgv: keyblock resource `/home/nthykier/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made 2012-04-18T20:11:23 UTC using RSA key ID 974B3E96
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on /tmp/tmpOCU1uZ/libitext-java_2.1.7-3.dsc
gpgv: keyblock resource `/home/nthykier/.gnupg/trustedkeys.gpg': file open error
gpgv: Signature made 2012-09-15T09:09:08 UTC using RSA key ID 7D806442
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on /tmp/tmpOCU1uZ/libitext-java_2.1.7-4.dsc
diff -Nru libitext-java-2.1.7/debian/changelog libitext-java-2.1.7/debian/changelog
--- libitext-java-2.1.7/debian/changelog 2012-04-18 19:47:02.0 +
+++ libitext-java-2.1.7/debian/changelog 2012-09-15 09:02:39.0 +
@@ -1,3 +1,14 @@
+libitext-java (2.1.7-4) unstable; urgency=low
+
+ * Team upload.
+ * Add missing the Class-Path for the java packages.
+- Use javahelper to set the classpath.
+- Use javahelper to compute dependencies.
+ * Add versioned (Build-)Dependency on libbcprov-java due to
+#687694.
+
+ -- Niels Thykier ni...@thykier.net Sat, 15 Sep 2012 11:02:37 +0200
+
libitext-java (2.1.7-3) unstable; urgency=low
[ Miguel Landaeta ]
diff -Nru libitext-java-2.1.7/debian/control libitext-java-2.1.7/debian/control
--- libitext-java-2.1.7/debian/control 2012-04-18 15:08:25.0 +
+++ libitext-java-2.1.7/debian/control 2012-09-15 08:58:02.0 +
@@ -3,8 +3,9 @@
Priority: optional
Maintainer: Debian Java Maintainers pkg-java-maintain...@lists.alioth.debian.org
Uploaders: Adriaan Peeters apeet...@lashout.net, Torsten Werner twer...@debian.org
-Build-Depends: debhelper (= 9), cdbs, default-jdk, ant, libbcprov-java,
- libbcmail-java, libbctsp-java, libdom4j-java, libpdfrenderer-java, gcj-native-helper
+Build-Depends: debhelper (= 9), cdbs, default-jdk, ant, libbcprov-java (= 1.46),
+ libbcmail-java, libbctsp-java, libdom4j-java, libpdfrenderer-java, gcj-native-helper,
+ javahelper (= 0.43)
Standards-Version: 3.9.3
Homepage: http://www.lowagie.com/iText/
Vcs-Svn: svn://svn.debian.org/svn/pkg-java/trunk/libitext-java
@@ -12,7 +13,7 @@
Package: libitext-java
Architecture: all
-Depends: ${misc:Depends}
+Depends: ${misc:Depends}, libbcprov-java (= 1.46), ${java:Depends}
Suggests: libitext-java-gcj
Description: Java Library to create and manipulate PDF on the fly
iText is a library that allows you to generate PDF files on the fly.
@@ -37,14 +38,14 @@
Package: libitext-rtf-java
Architecture: all
-Depends: libitext-java (= ${binary:Version}), ${misc:Depends}
+Depends: libitext-java (= ${binary:Version}), ${misc:Depends}, ${java:Depends}
Description: Java Library to create and manipulate RTF files on the fly
iText RTF is a library that allows you to generate RTF files on the fly in
a similar fashion to iText itself.
Package: libitext-rups-java
Architecture: all
-Depends: libitext-java (= ${binary:Version}), ${misc:Depends}
+Depends: libitext-java (= ${binary:Version}), ${misc:Depends}, ${java:Depends}
