Bug#733488: libjna-java: Update the jna library to a current upstream version

2013-12-29 Thread Jonas Wolz
Package: libjna-java Version: 3.2.7-4 Severity: important Dear Maintainer, is it possible to update the libjna-java package to a current (or at least newer than 3.4.0) version of the JNA library? Version 3.2.7 has the following bug which makes the package more or less unusable for my code:

clucy REMOVED from testing

2013-12-29 Thread Debian testing watch
FYI: The status of the clucy source package in Debian's testing distribution has changed. Previous version: 0.3.0-1 Current version: (not in testing) Hint: http://release.debian.org/britney/hints/auto-removals # in clojure1.2 The script that generates this mail tries to extract

closure-compiler REMOVED from testing

2013-12-29 Thread Debian testing watch
FYI: The status of the closure-compiler source package in Debian's testing distribution has changed. Previous version: 20130227+dfsg1-2 Current version: (not in testing) Hint: http://release.debian.org/britney/hints/auto-removals # 724081,724098,705565 The script that generates this

clojure1.2 REMOVED from testing

2013-12-29 Thread Debian testing watch
FYI: The status of the clojure1.2 source package in Debian's testing distribution has changed. Previous version: 1.2.1+dfsg-4 Current version: (not in testing) Hint: http://release.debian.org/britney/hints/auto-removals The script that generates this mail tries to extract removal reasons

leiningen REMOVED from testing

2013-12-29 Thread Debian testing watch
FYI: The status of the leiningen source package in Debian's testing distribution has changed. Previous version: 1.7.1-2 Current version: (not in testing) Hint: http://release.debian.org/britney/hints/auto-removals # in clojure1.2 The script that generates this mail tries to extract

libhamcrest-java 1.3-4 MIGRATED to testing

2013-12-29 Thread Debian testing watch
FYI: The status of the libhamcrest-java source package in Debian's testing distribution has changed. Previous version: 1.3-3 Current version: 1.3-4 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

clojure-contrib REMOVED from testing

2013-12-29 Thread Debian testing watch
FYI: The status of the clojure-contrib source package in Debian's testing distribution has changed. Previous version: 1.2.0-2 Current version: (not in testing) Hint: http://release.debian.org/britney/hints/auto-removals # in clojure1.2 The script that generates this mail tries to

libmecab-java REMOVED from testing

2013-12-29 Thread Debian testing watch
FYI: The status of the libmecab-java source package in Debian's testing distribution has changed. Previous version: 0.99.6-1 Current version: (not in testing) Hint: http://release.debian.org/britney/hints/auto-removals # in mecab The script that generates this mail tries to extract

jansi-native 1.0-4 MIGRATED to testing

2013-12-29 Thread Debian testing watch
FYI: The status of the jansi-native source package in Debian's testing distribution has changed. Previous version: 1.0-3 Current version: 1.0-4 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

jgit 3.2.0-1 MIGRATED to testing

2013-12-29 Thread Debian testing watch
FYI: The status of the jgit source package in Debian's testing distribution has changed. Previous version: 3.1.0-2 Current version: 3.2.0-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

Bug#705565: Getting closure compiler back in testing?

2013-12-29 Thread Rogério Brito
Hi there. Can we have a late Christmas present (or even an New Year's present)? The closure compiler: * has already been removed from testing [1] * has many applications and users that depend/want it * already has patches in the BTS [2] [1]:

Bug#705565: Getting closure compiler back in testing?

2013-12-29 Thread tony mancill
On 12/29/2013 03:48 PM, Rogério Brito wrote: Hi there. Can we have a late Christmas present (or even an New Year's present)? The closure compiler: * has already been removed from testing [1] * has many applications and users that depend/want it * already has patches in the BTS [2]

Processed: tagging 705565

2013-12-29 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: tags 705565 + pending Bug #705565 [libclosure-compiler-java] closure-compiler.jar: Exits immediately with “Failed to load Main-Class manifest attribute” Added tag(s) pending. thanks Stopping processing here. Please contact me if you need

Processing of closure-compiler_20130227+dfsg1-3_amd64.changes

2013-12-29 Thread Debian FTP Masters
closure-compiler_20130227+dfsg1-3_amd64.changes uploaded successfully to localhost along with the files: closure-compiler_20130227+dfsg1-3.dsc closure-compiler_20130227+dfsg1-3.debian.tar.gz libclosure-compiler-java_20130227+dfsg1-3_all.deb

Bug#733586: closure-compiler: new upstream version available

2013-12-29 Thread tony mancill
Source: closure-compiler Severity: wishlist Dear Java Team, Please consider updating closure-compiler to a newer upstream version. The most recent tagged release is v20131118. Thank you, tony (filing a reminder bug) __ This is the maintainer address of Debian's Java team

closure-compiler_20130227+dfsg1-3_amd64.changes ACCEPTED into unstable

2013-12-29 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 Dec 2013 21:11:30 -0800 Source: closure-compiler Binary: libclosure-compiler-java libclosure-compiler-java-doc Architecture: source all Version: 20130227+dfsg1-3 Distribution: unstable Urgency: low Maintainer:

Bug#705565: marked as done (closure-compiler.jar: Exits immediately with “Failed to load Main-Class manifest attribute”)

2013-12-29 Thread Debian Bug Tracking System
Your message dated Mon, 30 Dec 2013 06:18:30 + with message-id e1vxwbk-0004tt...@franck.debian.org and subject line Bug#705565: fixed in closure-compiler 20130227+dfsg1-3 has caused the Debian Bug report #705565, regarding closure-compiler.jar: Exits immediately with “Failed to load

Bug#724098: marked as done (jssip: FTBFS: Exception in thread main java.lang.NoClassDefFoundError: com/google/common/io/LimitInputStream)

2013-12-29 Thread Debian Bug Tracking System
Your message dated Mon, 30 Dec 2013 06:18:30 + with message-id e1vxwbk-0004u3...@franck.debian.org and subject line Bug#724098: fixed in closure-compiler 20130227+dfsg1-3 has caused the Debian Bug report #724098, regarding jssip: FTBFS: Exception in thread main java.lang.NoClassDefFoundError:

Bug#724081: marked as done (closure-compiler: FTBFS: [javac] /«BUILDDIR»/closure-compiler-20130227+dfsg1/src/com/google/javascript/jscomp/CommandLineRunner.java:25: error: cannot find symbol)

2013-12-29 Thread Debian Bug Tracking System
Your message dated Mon, 30 Dec 2013 06:18:30 + with message-id e1vxwbk-0004ty...@franck.debian.org and subject line Bug#724081: fixed in closure-compiler 20130227+dfsg1-3 has caused the Debian Bug report #724081, regarding closure-compiler: FTBFS: [javac]

Bug#726286: marked as done (libclosure-compiler-java: missing dependency on a Java runtime environment)

2013-12-29 Thread Debian Bug Tracking System
Your message dated Mon, 30 Dec 2013 06:18:30 + with message-id e1vxwbk-0004u8...@franck.debian.org and subject line Bug#726286: fixed in closure-compiler 20130227+dfsg1-3 has caused the Debian Bug report #726286, regarding libclosure-compiler-java: missing dependency on a Java runtime

Bug#726294: marked as done (libclosure-compiler-java: Exits immediately with “no main manifest attribute”)

2013-12-29 Thread Debian Bug Tracking System
Your message dated Mon, 30 Dec 2013 06:18:30 + with message-id e1vxwbk-0004ud...@franck.debian.org and subject line Bug#726294: fixed in closure-compiler 20130227+dfsg1-3 has caused the Debian Bug report #726294, regarding libclosure-compiler-java: Exits immediately with “no main manifest