Delivery Status Notification (Failure)

2007-02-13 Thread postmaster
This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed. [EMAIL PROTECTED] Reporting-MTA: dns;exchange.barrettlaw.com Received-From-MTA: dns;wsus Arrival-Date: Fri, 9 Feb 2007 11:39:25 -0500 Final-Recipient:

Re: Bug in java-package 0.28

2007-02-13 Thread Barry Hawkins
Todd, The issue probably has to do with the new IBM Java 5 binary having a new file name. I'll look into that for you, but be advised it may be a couple weeks because I am in a work crunch at this time. Regards, Barry Todd O'Bryan wrote: I've been trying to package and install the latest

Bug#394689: marked as done (registering gnu crypto security provider for classpath based runtimes)

2007-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2007 02:14:18 +0100 with message-id [EMAIL PROTECTED] and subject line registering gnu crypto security provider for classpath based runtimes has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If

Processing of libxalan2-java_2.7.0-4_i386.changes

2007-02-13 Thread Archive Administrator
libxalan2-java_2.7.0-4_i386.changes uploaded successfully to localhost along with the files: libxalan2-java_2.7.0-4.dsc libxalan2-java_2.7.0-4.diff.gz libxalan2-java_2.7.0-4_all.deb libxsltc-java_2.7.0-4_all.deb libxalan2-java-doc_2.7.0-4_all.deb libxalan2-java-gcj_2.7.0-4_i386.deb

libxalan2-java_2.7.0-4_i386.changes ACCEPTED

2007-02-13 Thread Debian Installer
Accepted: libxalan2-java-doc_2.7.0-4_all.deb to pool/main/libx/libxalan2-java/libxalan2-java-doc_2.7.0-4_all.deb libxalan2-java-gcj_2.7.0-4_i386.deb to pool/main/libx/libxalan2-java/libxalan2-java-gcj_2.7.0-4_i386.deb libxalan2-java_2.7.0-4.diff.gz to

Bug#408729: marked as done (should depend on jaxp1.3, not jaxp1.2)

2007-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2007 03:02:54 +0100 with message-id [EMAIL PROTECTED] and subject line should depend on jaxp1.3, not jaxp1.2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now

Bug#402529: marked as done (libxalan2-java-doc: Ships dangling symlink)

2007-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2007 03:10:34 +0100 with message-id [EMAIL PROTECTED] and subject line libxalan2-java-doc: Ships dangling symlink has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#408729: marked as done (should depend on jaxp1.3, not jaxp1.2)

2007-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2007 02:32:04 + with message-id [EMAIL PROTECTED] and subject line Bug#408729: fixed in libxalan2-java 2.7.0-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is