Re: Update for libcsvjdbc-java

Dear Mechtilde, Thanks for updating the package. When I did my first Java package I seem to recall being told by someone that the pkg-java team doesn't follow the convention of adding +ds or +dfsg to the version string on the grounds that virtually all Java source packages contain binaries or

Re: The quilt / maven-helper dance

Dear Emmanuel, Thank you for looking into this. However, I can see a problem: debclean calls "debuild -- clean" which calls dh_auto_clean, which invokes the clean function in maven.pm. If the debian/maven-repo folder exists, maven is then invoked to run its own clean target using the unmodified

The quilt / maven-helper dance

In order to achieve a successful build, it is sometimes it is necessary to modify a pom.xml file in a way which cannot be achieved purely through using mh_patchpoms. In these cases, one falls back on using quilt as the standard mechanism for patching an upstream source. See for example:

Re: libbatik-java: Changed artifacts?

wrote: > Am 09.09.2017 um 20:22 schrieb Christopher Hoskin: >>> >>> One suggestion: If you update a library, it would be good to test >>> whether any r-dep fails to build. There are not many for the case of >>> batik. >>> >> >> Is there an

Re: libbatik-java: Changed artifacts?

> > One suggestion: If you update a library, it would be good to test > whether any r-dep fails to build. There are not many for the case of > batik. > Is there an automated way to rebuild all of the reverse dependencies of a package and see a summary of the outcome? libbatik-java has 25

Re: libbatik-java: Changed artifacts?

reverse dependencies expecting the ant layout build? Christopher On 9 September 2017 at 15:22, Christopher Hoskin <mans0...@debian.org> wrote: > Dear Felix, > > One of the changes between batik 1.7 and 1.9 is that upstream now > provides pom files, although I'm still doing

Re: libbatik-java: Changed artifacts?

Dear Felix, One of the changes between batik 1.7 and 1.9 is that upstream now provides pom files, although I'm still doing the build with ant. batik-i18n gets included in the batic-util.jar, but the pom file for batic-util includes: ${project.groupId} batik-constants

Re: autopkgtest for pkg-java

I'd welcome something like this. Christopher On 29 July 2017 at 15:56, Carnë Draug wrote: > Hi > > The pkg-perl team has a series of tests that can be easily set for > autopkgtest [1]. One only has to declare on d/control > > Testsuite: autopkgtest-pkg-perl > > This

Re: Need for help: Eclipse Neon

, Christopher Hoskin <christopher.hos...@gmail.com> wrote: > My current hunch is that we might need to add > org.eclipse.osgi.services_3.5.0.v20150714-1510.jar to > tycho-bundles-external-0.25.0.zip to provide EnvironmentInfo. > > Christopher > > On 18 July 2017 a

Re: Need for help: Eclipse Neon

My current hunch is that we might need to add org.eclipse.osgi.services_3.5.0.v20150714-1510.jar to tycho-bundles-external-0.25.0.zip to provide EnvironmentInfo. Christopher On 18 July 2017 at 22:21, Christopher Hoskin <christopher.hos...@gmail.com> wrote: > My line of enquiry has bee

Re: Need for help: Eclipse Neon

My line of enquiry has been to look at what's happening in eclipse-bundles/org.eclipse.osgi/container/src/org/eclipse/core/runtime/adaptor/EclipseStarter.java. In the startup function, context.getServiceReference(FrameworkLog.class); and context.getServiceReference(EnvironmentInfo.class) are

Bug#845789: ITP: spymemcached -- simple, asynchronous, single-threaded memcached client written in java

Package: wnpp Severity: wishlist Owner: Christopher Hoskin <christopher.hos...@gmail.com> * Package name: spymemcached Version : 2.12.1 Upstream Author : Dustin Sallings, Couchbase, Inc. * URL : https://github.com/couchbase/spymemcached * License :

Bug#838749: RFS: csvjdbc/1.0.31-1

ch * Add bundled lib/dans-dbf-lib-*.jar file to Files-Excluded * Import new upstream (1.0.31) * debian/copyright: change Copyright-Format 1.0 URL to HTTPS. -- Christopher Hoskin <christopher.hos...@gmail.com> Sat, 24 Sep 2016 10:07:12 +0100 Regards, Christopher Hoskin

Cleaning upstream tarballs

I'm considering how to remove .jar files and convenience copies of other libraries from upstream tar balls. It seems to me that there are several ways of approaching repacking: 1) Add Files-Excluded to debian/copyright 2) Create a debian/orig-tar.sh script and call it from debian/watch 3) Call

Re: Gradle and transitive dependencies

Dear Emmanuel, Yes, that works in this case. For the benefit of anyone with a similar problem, the issue arises in this case because by default, gradle-debian-helper only applies its ruleset if the version isn't already generic (i.e. 'debian' or ends in '.x'). Since the transitive dependency

Re: Gradle and transitive dependencies

Thanks for your help at the weekend - it solved that issue, but I now seem to have the problem the other way around: ... :bson:checkstyleMain Replacing com.puppycrawl.tools:checkstyle:jar:6.2 -> com.puppycrawl.tools:checkstyle:jar:debian Passing through

Re: Gradle and transitive dependencies

Dear Markus, Thanks! It looks like CodeNarc switched to using Junit 4.x somewhere between 0.17 and 0.23, but the CodeNarc's debian/maven.rules didn't get updated, so the CodeNarc pom is generated incorrectly. Rebuilding the CodeNarc package with an updated debian/maven.rules and installing it

Re: Gradle and transitive dependencies

Dear Markus, Thanks for the reply. I've changed the debian/maven.rules file so that it just has: junit junit jar s/4\..*/4.x/ * * But if I run debuild, I still get the same error message. Looking in /usr/share/maven-repo/org/codenarc/CodeNarc/0.23/CodeNarc-0.23.pom CodeNarc's pom appears to

Gradle and transitive dependencies

Hello, I'm trying to update the mongo-java-driver package to 3.3.0, using gradle-debian-helper. I've got a package which builds, now I'm trying to run the tests with dh_auto_build --buildsystem=gradle -- check Currently, the tests fail with: Replacing org.codenarc:CodeNarc:jar:0.24

Dependencies packaged without POMs

Hello, Some libraries (e.g. Jython) are packaged for Debian, but don't use Maven. In these cases it may be that nothing is installed into /usr/share/maven-repo. How should Maven projects which reference such dependencies be packaged? According to the spec [0], and should be used to reference

Re: Java Team blog

Thanks for setting up the blog. Regarding "Outlook, goals and request for help", I'm interested in helping out. I've been trying to get involved for a while, but to be honest, I'm finding the learning curve rather steep. Some blog posts covering how to get started and how to tackle some of the

Bug#823270: RFS: csvjdbc/1.0.29-1

ackage with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/csvjdbc/csvjdbc_1.0.29-1.dsc More information about csvjdbc can be obtained from http://csvjdbc.sourceforge.net/. Changes since the last upload: * Initial release (Closes: #823234) Regards, Christopher Hoskin

Re: plans for eclipse luna in debian

; Il 11/03/2016 09:32, Luca Vercelli ha scritto: > > > > > > Il 11/03/2016 00:18, Christopher Hoskin ha scritto: > >> Dear Luca, > >> > >> Great! I've built and installed the sat4j package, however, when I try > >> to build tycho maven is

Re: plans for eclipse luna in debian

Dear Luca, Great! I've built and installed the sat4j package, however, when I try to build tycho maven is unable to find sat4j (extract from the build log below). Any ideas? Also, the following packages are missing from Build-Depends in debian/control: debhelper, rsync,

Re: plans for eclipse luna in debian

Out of curiosity, I thought I'd give this a try and see how far I got. I downloaded https://git.eclipse.org/c/tycho/org.eclipse.tycho.git/snapshot/tycho-0.24.0.tar.gz and copied the files http://pkgs.fedoraproject.org/cgit/rpms/tycho.git/tree/tycho-bootstrap.sh

Re: plans for eclipse luna in debian

Dear Luca, I know very little about this, but I was wondering if something like this might be possible? 1) Create a "tycho bootstrap" package using the partial bootstrap method from Fedora and build depending on Eclipse 3.8 (the version currently in Sid); 2) Create an Eclipse 4.x package which