Re: [gradle] 05/05: Merge libgradle-core-java and libgradle-plugins-java into gradle

Hi, Then I am reverting the commit. Avoiding pulling a JRE or even JDK is good practice. There's a problem though that it is sometimes not easy to say a jar should belong to libgradle-core-java or libgradle-plugins-java by judging the file name. Cheers, Kai-Chung Yan Miguel Landaeta

maven_3.3.3-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 09 Jul 2015 14:57:53 +0200 Source: maven Binary: maven libmaven3-core-java Architecture: source all Version: 3.3.3-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

Bug#774745: marked as done (Upgrade to maven 3.1.1/3.2.5)

Your message dated Fri, 10 Jul 2015 07:00:21 + with message-id e1zdsih-tj...@franck.debian.org and subject line Bug#774745: fixed in maven 3.3.3-1 has caused the Debian Bug report #774745, regarding Upgrade to maven 3.1.1/3.2.5 to be marked as done. This means that you claim that the

Bug#792021: libmaven3-core-java: not installable in sid - libeclipse-aether-java (= 1.0) does not exist

Package: libmaven3-core-java Version: 3.3.3-1 Severity: grave Hi, maven and libmaven3-core-java can no longer be installed in sid because the dependency on libeclipse-aether-java cannot be satisfied. $ sudo aptitude install maven The following NEW packages will be installed: libguice-java{a}

Processing of eclipse-aether_1.0.2-1_amd64.changes

eclipse-aether_1.0.2-1_amd64.changes uploaded successfully to localhost along with the files: eclipse-aether_1.0.2-1.dsc eclipse-aether_1.0.2.orig.tar.gz eclipse-aether_1.0.2-1.debian.tar.xz libeclipse-aether-java_1.0.2-1_all.deb Greetings, Your Debian queue daemon (running on

eclipse-aether_1.0.2-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Fri, 10 Jul 2015 13:10:59 +0200 Source: eclipse-aether Binary: libeclipse-aether-java Architecture: source all Version: 1.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

Bug#791523: Removed package(s) from unstable

We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libopenws-java |1.5.1-3 | source, all libopenws-java-doc |1.5.1-3 | all --- Reason --- RoQA; unmaintained upstream

Processing of jruby_1.7.21-1_amd64.changes

jruby_1.7.21-1_amd64.changes uploaded successfully to localhost along with the files: jruby_1.7.21-1.dsc jruby_1.7.21.orig.tar.gz jruby_1.7.21-1.debian.tar.xz jruby_1.7.21-1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) __ This is the maintainer

Bug#792021: marked as done (libmaven3-core-java: not installable in sid - libeclipse-aether-java (= 1.0) does not exist)

Your message dated Fri, 10 Jul 2015 11:38:48 -0300 with message-id 20150710143848.ga19...@alice.nomadium.lan and subject line Re: libmaven3-core-java: not installable in sid - libeclipse-aether-java (= 1.0) does not exist has caused the Debian Bug report #792021, regarding libmaven3-core-java:

Bug#771694: marked as done (jruby: Inconsistency between Maven and package dependencies)

Your message dated Fri, 10 Jul 2015 15:36:24 + with message-id e1zdalg-0003xf...@franck.debian.org and subject line Bug#771694: fixed in jruby 1.7.21-1 has caused the Debian Bug report #771694, regarding jruby: Inconsistency between Maven and package dependencies to be marked as done. This

jruby_1.7.21-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 08 Jul 2015 20:59:46 -0300 Source: jruby Binary: jruby Architecture: source all Version: 1.7.21-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers