I see that package is used at runtime only in reverse dependencies (biojava), this is not a build dependency, so I have no way to validate the library.
Compilation looks fine, and package looks ok. should I go for a package upload (to prevent removal of other packages) ? I have not tried to update to any recent release, focusing on getting the same working release to fix bug. Olivier On 06/20/2016 09:51 PM, Andreas Tille wrote: > On Mon, Jun 20, 2016 at 03:38:46PM +0200, Olivier Sallou wrote: >> I made a quick fix to switch to compat 9 and fix Java version to current >> jdk in sid. >> >> However, i cannot push to pkg-escience / bytecode (permission denied). > Since pkg-escience is closed. > >> It would be best to move package to pkg-java instead of debianmed >> according to me, as it is pure Java package. > That would be also my first idea. > >> Patching is quite easy: >> >> switch d/compat to 9 (no issue) >> >> d/control: update dependencies to use default-jdk and default-jre >> instead of openjdk/sun-jdk/java2-compiler >> >> add a patch to build.xml to add in all javac commands : source="1.6" >> target="1.6" >> >> build is fine with no specific lintian error > Would you volunteer to move it to pkg-java Git? > > Kind regards > > Andreas. > -- Olivier Sallou IRISA / University of Rennes 1 Campus de Beaulieu, 35000 RENNES - FRANCE Tel: 02.99.84.71.95 gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
