Bug#483919: classpath-qtpeer: Classpath AWT support still royally broken

Package: classpath-qtpeer Version: 2:0.97.1-3 Severity: normal I'm trying to run a hybrid Java applet/application on an AMD64 sid machine. While my goal would be to get the applet running, I'm already stuck with some Classpath bugs regarding any GUI activity of the application. When using

Processed: tagging as pending bugs that are closed by packages in NEW

Processing commands for [EMAIL PROTECTED]: # Sun Jun 1 08:03:31 UTC 2008 # Tagging as pending bugs that are closed by packages in NEW # http://ftp-master.debian.org/new.html # # Source package in NEW: libpicocontainer-java tags 482863 + pending Bug#482863: libpicocontainer-java: New

Processing of libhibernate-validator-java_3.1.0.CR1-1_i386.changes

libhibernate-validator-java_3.1.0.CR1-1_i386.changes uploaded successfully to localhost along with the files: libhibernate-validator-java_3.1.0.CR1-1.dsc libhibernate-validator-java_3.1.0.CR1.orig.tar.gz libhibernate-validator-java_3.1.0.CR1-1.diff.gz

libhibernate-validator-java_3.1.0.CR1-1_i386.changes ACCEPTED

Accepted: libhibernate-validator-java_3.1.0.CR1-1.diff.gz to pool/contrib/libh/libhibernate-validator-java/libhibernate-validator-java_3.1.0.CR1-1.diff.gz libhibernate-validator-java_3.1.0.CR1-1.dsc to pool/contrib/libh/libhibernate-validator-java/libhibernate-validator-java_3.1.0.CR1-1.dsc

Processed (with 5 errors): Confirmed - need to add manifest

Processing commands for [EMAIL PROTECTED]: tags 481571 +confirmed Bug#481571: [libjtidy-java] Failed to load Main-Class manifest attribute There were no tags set. Tags added: confirmed Thanks for the report. Yes, we need to add an explicit manifest. Unknown command or malformed arguments to

Bug#481571: Confirmed - need to add manifest

tags 481571 +confirmed Thanks for the report. Yes, we need to add an explicit manifest. Upstream's looks like: Main-Class: org.w3c.tidy.Tidy Name: org/w3c/tidy/Tidy.class Java-Bean: True Thanks, Paul ___ pkg-java-maintainers mailing list

classpath_0.97.1-5_amd64.changes ACCEPTED

Accepted: classpath-common-unzipped_0.97.1-5_all.deb to pool/main/c/classpath/classpath-common-unzipped_0.97.1-5_all.deb classpath-common_0.97.1-5_all.deb to pool/main/c/classpath/classpath-common_0.97.1-5_all.deb classpath-doc_0.97.1-5_all.deb to

Processing of kaffe_1.1.8-5_amd64.changes

kaffe_1.1.8-5_amd64.changes uploaded successfully to localhost along with the files: kaffe_1.1.8-5.dsc kaffe_1.1.8-5.diff.gz kaffe_1.1.8-5_all.deb kaffe-common_1.1.8-5_all.deb kaffe-dev_1.1.8-5_all.deb jikes-kaffe_1.1.8-5_all.deb kaffe-doc_1.1.8-5_all.deb

kaffe_1.1.8-5_amd64.changes ACCEPTED

Accepted: jikes-kaffe_1.1.8-5_all.deb to pool/main/k/kaffe/jikes-kaffe_1.1.8-5_all.deb kaffe-common_1.1.8-5_all.deb to pool/main/k/kaffe/kaffe-common_1.1.8-5_all.deb kaffe-dev_1.1.8-5_all.deb to pool/main/k/kaffe/kaffe-dev_1.1.8-5_all.deb kaffe-doc_1.1.8-5_all.deb to

Bug#479716: marked as done (Kaffe FTBFS)

Your message dated Mon, 02 Jun 2008 05:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#479716: fixed in kaffe 2:1.1.8-5 has caused the Debian Bug report #479716, regarding Kaffe FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#477868: marked as done (kaffe: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386))

Your message dated Mon, 02 Jun 2008 05:47:04 + with message-id [EMAIL PROTECTED] and subject line Bug#477868: fixed in kaffe 2:1.1.8-5 has caused the Debian Bug report #477868, regarding kaffe: adjust build-dependency (gcj not built on alpha, arm, hppa and hurd-i386) to be marked as done.