Package: libpgjava Version: 7.4.2-1 Severity: important Hi,
during investigation of building libpgjava with free tools I found that the jdbc2.jar contains actually a jdb3 driver. This happened as build/libpgjava is called twice during building the package. Therefore during the second call the jdbc2 finds already compiled classes and builds the jar with jdbc3 classes. As I'm not a CDBS expert - I don't know which is the right way to go. But I have to possible solutions: 1) change build/libpgjava:: target to build: This way the build is only triggered one time. 2) include clean ant targets before each jdbc build It will still be build two times - but the clean target before the acutally build will prevent a "wrong" jdbc2 jar. Having the move of libpgjava to main in mind I think we should do the following: - Upload a fixed package as contrib package with urgency=medium to fix this problem - maybe we should use a new upstream as the release notes for 7.4.3 und 7.4.4 give several jdbc fixes - Upload a package for main afterwards I would prepare new packages after we decided which way to go for the "build called twice" problem described above. Wolfgang -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11.6laptop Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages libpgjava depends on: ii blackdown-j2sdk1.3 [j 1.3.1+02b Java(TM) 2 SDK, Standard Edition, ii classpath 2:0.14-1 clean room standard Java libraries ii gij-3.3 [java1-runtim 1:3.3.5-12 The GNU Java bytecode interpreter ii gij-3.4 [java1-runtim 3.4.3-12 The GNU Java bytecode interpreter ii jamvm [java1-runtime] 1.2.5-1 virtual machine which conforms to ii kaffe-pthreads [java1 2:1.1.4.PRECVS12-1 A POSIX threads enabled version of ii sablevm [java1-runtim 1.11.1-2 Free implementation of Java Virtua ii sun-j2sdk1.4 [java2-r 1.4.2+07 Java(TM) 2 SDK, Standard Edition, ii sun-j2sdk1.5 [java2-r 1.5.0+update02 Java(TM) 2 SDK, Standard Edition, -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
