Processed: unarchiving 652049, user ubuntu-de...@lists.ubuntu.com, usertagging 652049, archiving 652049

Processing commands for cont...@bugs.debian.org: unarchive 652049 Bug #652049 {Done: Miguel Landaeta mig...@miguel.cc} [excalibur-logkit] excalibur-logkit: Fix FTBFS with OpenJDK7 + tidy misc lintian warnings Unarchived Bug 652049 user ubuntu-de...@lists.ubuntu.com Setting user to

Processed (with 2 errors): unarchiving 651422, user ubuntu-de...@lists.ubuntu.com, usertagging 651422, archiving 651422 ...

Processing commands for cont...@bugs.debian.org: unarchive 651422 Bug #651422 {Done: Miguel Landaeta mig...@miguel.cc} [jericho-html] jericho-html: Fix FTBFS with OpenJDK7 Unarchived Bug 651422 user ubuntu-de...@lists.ubuntu.com Setting user to ubuntu-de...@lists.ubuntu.com (was

Bug#675160: sikuli-ide: unable to process one single instruction, NoSuchMethodError: org.jruby.ext.posix.POSIX.isNative()Z

severity 675160 normal tags 675160 + moreinfo unreproducible quit Hi, hennr a écrit , Le 30/05/2012 11:36: Package: sikuli-ide Version: 1.0~x~rc3.tesseract3-dfsg1-3 Severity: grave Justification: renders package unusable sikuli can't process an application like this one:

Processed: Re: Bug#675160: sikuli-ide: unable to process one single instruction, NoSuchMethodError: org.jruby.ext.posix.POSIX.isNative()Z

Processing commands for cont...@bugs.debian.org: severity 675160 normal Bug #675160 [sikuli-ide] sikuli-ide: unable to process one single instruction, NoSuchMethodError: org.jruby.ext.posix.POSIX.isNative()Z Severity set to 'normal' from 'grave' tags 675160 + moreinfo unreproducible Bug

Processing of rxtx_2.2pre2-11_i386.changes

rxtx_2.2pre2-11_i386.changes uploaded successfully to localhost along with the files: rxtx_2.2pre2-11.dsc rxtx_2.2pre2-11.debian.tar.gz librxtx-java_2.2pre2-11_i386.deb librxtx-java-dbg_2.2pre2-11_i386.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)

Processing of rxtx_2.2pre2-11_i386.changes

/rxtx_2.2pre2-11_i386.changes is already present on target host: librxtx-java-dbg_2.2pre2-11_i386.deb Either you already uploaded it, or someone else came first. Job rxtx_2.2pre2-11_i386.changes removed. Greetings, Your Debian queue daemon (running on host franck.debian.org) __ This is

rxtx_2.2pre2-11_i386.changes ACCEPTED into unstable

Accepted: librxtx-java-dbg_2.2pre2-11_i386.deb to main/r/rxtx/librxtx-java-dbg_2.2pre2-11_i386.deb librxtx-java_2.2pre2-11_i386.deb to main/r/rxtx/librxtx-java_2.2pre2-11_i386.deb rxtx_2.2pre2-11.debian.tar.gz to main/r/rxtx/rxtx_2.2pre2-11.debian.tar.gz rxtx_2.2pre2-11.dsc to

Bug#674975: marked as done (librxtx-java: created Java threads are not marked as daemon)

Your message dated Sat, 02 Jun 2012 15:29:52 + with message-id e1saqh2-000564...@franck.debian.org and subject line Bug#674975: fixed in rxtx 2.2pre2-11 has caused the Debian Bug report #674975, regarding librxtx-java: created Java threads are not marked as daemon to be marked as done. This

Processing of trove3_3.0.2-1_i386.changes

trove3_3.0.2-1_i386.changes uploaded successfully to localhost along with the files: trove3_3.0.2-1.dsc trove3_3.0.2.orig.tar.gz trove3_3.0.2-1.debian.tar.gz libtrove3-java_3.0.2-1_all.deb libtrove3-java-doc_3.0.2-1_all.deb Greetings, Your Debian queue daemon (running on host

Processing of trove3_3.0.2-1_i386.changes

trove3_3.0.2-1_i386.changes uploaded successfully to localhost along with the files: trove3_3.0.2-1.dsc trove3_3.0.2.orig.tar.gz trove3_3.0.2-1.debian.tar.gz libtrove3-java_3.0.2-1_all.deb libtrove3-java-doc_3.0.2-1_all.deb Greetings, Your Debian queue daemon (running on host

trove3_3.0.2-1_i386.changes REJECTED

Reject Reasons: 'dpkg-source -x' failed for trove3_3.0.2-1.dsc. (Command '('dpkg-source', '--no-copy', '--no-check', '-q', '-x', 'trove3_3.0.2-1.dsc', '/srv/ftp-master.debian.org/tmp/tmpEWgHjK/root')' returned non-zero exit status 9) === Please feel free to respond to this email if you

Bug#657870: some more struts issues

Hi, I'm sorry, but we've got yet another set of struts vulnerabilities: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2087 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2088 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0838 It would be really helpful if you could