uima-addons_2.3.1-3_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 11 Sep 2013 23:27:25 +0200 Source: uima-addons Binary: libuima-addons-java libuima-addons-java-doc Architecture: source all Version: 2.3.1-3 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers C

Processing of uima-addons_2.3.1-3_amd64.changes

uima-addons_2.3.1-3_amd64.changes uploaded successfully to localhost along with the files: uima-addons_2.3.1-3.dsc uima-addons_2.3.1-3.debian.tar.gz libuima-addons-java_2.3.1-3_all.deb libuima-addons-java-doc_2.3.1-3_all.deb Greetings, Your Debian queue daemon (running on host fra

Bug#722518: marked as done (icu4j: Please install Maven metadata)

Your message dated Sat, 14 Sep 2013 04:18:12 + with message-id and subject line Bug#722518: fixed in icu4j 4.2.1.1-2 has caused the Debian Bug report #722518, regarding icu4j: Please install Maven metadata to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#643631: marked as done (Typo in package description)

Your message dated Sat, 14 Sep 2013 04:18:12 + with message-id and subject line Bug#643631: fixed in icu4j 4.2.1.1-2 has caused the Debian Bug report #643631, regarding Typo in package description to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#639848: marked as done (Description uses inconsistent English-es)

Your message dated Sat, 14 Sep 2013 04:18:12 + with message-id and subject line Bug#639848: fixed in icu4j 4.2.1.1-2 has caused the Debian Bug report #639848, regarding Description uses inconsistent English-es to be marked as done. This means that you claim that the problem has been dealt wit

Bug#568351: marked as done ([libicu4j-java] "unicode" in short description)

Your message dated Sat, 14 Sep 2013 04:18:12 + with message-id and subject line Bug#568351: fixed in icu4j 4.2.1.1-2 has caused the Debian Bug report #568351, regarding [libicu4j-java] "unicode" in short description to be marked as done. This means that you claim that the problem has been dea

icu4j_4.2.1.1-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 11 Sep 2013 23:59:36 +0100 Source: icu4j Binary: libicu4j-java Architecture: source all Version: 4.2.1.1-2 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers Changed-By: Andrew Ross Descriptio

Processing of icu4j_4.2.1.1-2_amd64.changes

icu4j_4.2.1.1-2_amd64.changes uploaded successfully to localhost along with the files: icu4j_4.2.1.1-2.dsc icu4j_4.2.1.1-2.debian.tar.gz libicu4j-java_4.2.1.1-2_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) __ This is the maintainer address of Debi

Processed: submitter

Processing commands for cont...@bugs.debian.org: > submitter 722667 ! Bug #722667 [mpich,mpich-bin] mpich-bin and mpich: error when trying to install together Changed Bug submitter to 'Ralf Treinen ' from 'Ralf Treinen ' > submitter 722666 ! Bug #722666 [libmpich-dev,libmpich1.0-dev] libmpich1.0

weka 3.6.10-1 MIGRATED to testing

FYI: The status of the weka source package in Debian's testing distribution has changed. Previous version: 3.6.6-1 Current version: 3.6.10-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive l

Bug#685298: Impossible to simultaneously install libtomcat7-java and libtomcat6-java

I'm in favor of option 2: don't put tomcat libs in /usr/share/java, much less unversioned ones. When was the last time anybody looked in /usr/share/java when they wanted to build or run anything? :) It seems to me that the real users of the tomcat* packages are developers. Sure, there could be

Bug#685298: Impossible to simultaneously install libtomcat7-java and libtomcat6-java

I think option 1 is probably the best approach - it's worked well in other areas -- James Page Technical Lead, Ubuntu Server Team On 13 Sep 2013, at 12:19, Emmanuel Bourg wrote: > Hi, > > I started working on the tomcat8 package and I'd like to avoid the same > conflict with tomcat7. What wou

Bug#685298: Impossible to simultaneously install libtomcat7-java and libtomcat6-java

Hi, I started working on the tomcat8 package and I'd like to avoid the same conflict with tomcat7. What would be the best solution? 1. Change the name of the unversioned jars to tomcat8-xxx.jar. That would give the following links in /usr/share/java: tomcat8-catalina-ant.jar -> tomcat-catali

Bug#579122: marked as done (testng: new upstream version)

Your message dated Fri, 13 Sep 2013 07:03:18 + with message-id and subject line Bug#579122: fixed in testng 6.8.7-1 has caused the Debian Bug report #579122, regarding testng: new upstream version to be marked as done. This means that you claim that the problem has been dealt with. If this is

testng_6.8.7-1_amd64.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 07 Sep 2013 10:42:29 + Source: testng Binary: testng Architecture: source all Version: 6.8.7-1 Distribution: experimental Urgency: low Maintainer: Debian Java Maintainers Changed-By: Eugene Zhukov Description: