jitescript_0.4.1-2_amd64.changes is NEW

binary:libjitescript-java is NEW. binary:libjitescript-java is NEW. source:jitescript is NEW. jitescript_0.4.1.orig.tar.gz is only available in NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a

Processing of jitescript_0.4.1-2_amd64.changes

jitescript_0.4.1-2_amd64.changes uploaded successfully to localhost along with the files: jitescript_0.4.1-2.dsc jitescript_0.4.1-2.debian.tar.xz jitescript_0.4.1-2_amd64.buildinfo libjitescript-java_0.4.1-2_all.deb Greetings, Your Debian queue daemon (running on host

Bug#845606: The Bytecode Should Not Be Targeting Java 1.2

On Wed, Jan 18, 2017 at 11:43:04AM +0100, Emmanuel Bourg wrote: > > I got another look and I think the root issue is the change I made in > asm/5.1-1 when I replaced asm-all.jar by a symlink to asm-debug-all.jar. > I assumed that asm-all was simply a version of the jar stripped from its > debug

Bug#851323: marked as done (jnr-posix: Package recent releases)

Your message dated Wed, 18 Jan 2017 22:49:39 + with message-id and subject line Bug#851323: fixed in jnr-posix 3.0.33-1 has caused the Debian Bug report #851323, regarding jnr-posix: Package recent releases to be marked as done. This means that you claim

jnr-posix_3.0.33-1_source.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 18 Jan 2017 21:44:56 + Source: jnr-posix Binary: libjnr-posix-java libjnr-posix-java-doc Architecture: source Version: 3.0.33-1 Distribution: experimental Urgency: medium Maintainer: Debian Java Maintainers

Processing of jnr-posix_3.0.33-1_source.changes

jnr-posix_3.0.33-1_source.changes uploaded successfully to localhost along with the files: jnr-posix_3.0.33-1.dsc jnr-posix_3.0.33.orig.tar.gz jnr-posix_3.0.33-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This is the maintainer address

Bug#851719: marked as done (libbytelist-java: Package recent releases)

Your message dated Wed, 18 Jan 2017 20:50:25 + with message-id and subject line Bug#851719: fixed in libbytelist-java 1.0.14-1 has caused the Debian Bug report #851719, regarding libbytelist-java: Package recent releases to be marked as done. This means

Processing of libbytelist-java_1.0.14-1_source.changes

libbytelist-java_1.0.14-1_source.changes uploaded successfully to localhost along with the files: libbytelist-java_1.0.14-1.dsc libbytelist-java_1.0.14.orig.tar.gz libbytelist-java_1.0.14-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) __

libbytelist-java_1.0.14-1_source.changes ACCEPTED into experimental

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 18 Jan 2017 20:15:56 + Source: libbytelist-java Binary: libbytelist-java Architecture: source Version: 1.0.14-1 Distribution: experimental Urgency: medium Maintainer: Debian Java Maintainers

jetty9 9.2.20-1 MIGRATED to testing

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

Processed: take ownership of my cam.ac.uk-submitted bugs

Processing commands for cont...@bugs.debian.org: > submitter 716975 matth...@chiark.greenend.org.uk Bug #716975 [twittering-mode] Should deal with lack-of-curl gracefully Changed Bug submitter to 'matth...@chiark.greenend.org.uk' from 'Matthew Vernon '. > submitter 740347

objenesis_2.5.1-1_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 18 Jan 2017 11:54:46 +0100 Source: objenesis Binary: libobjenesis-java libobjenesis-java-doc Architecture: source all Version: 2.5.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

Processing of objenesis_2.5.1-1_amd64.changes

objenesis_2.5.1-1_amd64.changes uploaded successfully to localhost along with the files: objenesis_2.5.1-1.dsc objenesis_2.5.1.orig.tar.gz objenesis_2.5.1-1.debian.tar.xz libobjenesis-java-doc_2.5.1-1_all.deb libobjenesis-java_2.5.1-1_all.deb objenesis_2.5.1-1_amd64.buildinfo

Bug#845606: marked as done (The Bytecode Should Not Be Targeting Java 1.2)

Your message dated Wed, 18 Jan 2017 11:48:30 + with message-id and subject line Bug#845606: fixed in asm 5.2-2 has caused the Debian Bug report #845606, regarding The Bytecode Should Not Be Targeting Java 1.2 to be marked as done. This means that you

asm_5.2-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 18 Jan 2017 12:17:49 +0100 Source: asm Binary: libasm-java libasm-java-doc Architecture: source all Version: 5.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

Processing of asm_5.2-2_amd64.changes

asm_5.2-2_amd64.changes uploaded successfully to localhost along with the files: asm_5.2-2.dsc asm_5.2-2.debian.tar.xz asm_5.2-2_amd64.buildinfo libasm-java-doc_5.2-2_all.deb libasm-java_5.2-2_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org) __

Bug#845606: Pending fixes for bugs in the asm package

tag 845606 + pending thanks Some bugs in the asm package are closed in revision 135bf1aa310533ab6c7e35afcf4e2ad6e64fb582 in branch 'master' by Emmanuel Bourg The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/asm.git/commit/?id=135bf1a Commit message: Replaced the

Processed: Pending fixes for bugs in the asm package

Processing commands for cont...@bugs.debian.org: > tag 845606 + pending Bug #845606 [libasm-java] The Bytecode Should Not Be Targeting Java 1.2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 845606:

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reopen 845606 Bug #845606 {Done: Emmanuel Bourg } [libasm-java] The Bytecode Should Not Be Targeting Java 1.2 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you

Bug#845606: The Bytecode Should Not Be Targeting Java 1.2

Le 15/01/2017 à 16:26, Miguel Landaeta a écrit : > It's probably too late to object this change since it's about to enter > testing but I suspect this change could trigger FTBFS in libasm-java > reverse dependencies. We still have two weeks before the final freeze to examine this actually. I

Bug#845606: The Bytecode Should Not Be Targeting Java 1.2

On Mon, 5 Dec 2016 05:44:46 -0800 tony mancill wrote: > I do note that the JAR files produced by > the "unshrunk" package are much larger (~4x) than what is being > distributed by Maven Central. > > I'll have a look - there could be another cause. I noticed that too, the