Your message dated Sat, 10 Sep 2005 13:32:57 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#326207: fixed in libsaxon-java 1:6.5.4-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 your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 2 Sep 2005 12:22:02 +0000
>From [EMAIL PROTECTED] Fri Sep 02 05:22:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from bedivere.rjm.de [217.24.217.20]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EBAYT-0004uM-00; Fri, 02 Sep 2005 05:22:02 -0700
Received: from p54ad2107.dip0.t-ipconnect.de ([84.173.33.7] helo=merlin)
by bedivere.rjm.de with asmtp (OpenMailstore Relay 1.0)
id 1EBAYT-0004WX-00
for <[EMAIL PROTECTED]>; Fri, 02 Sep 2005 14:22:02 +0200
Received: from gwion.intern.rjm.de ([192.168.150.150])
by merlin with asmtp (Exim 3.35 #1 (Debian))
id 1EBAYO-000679-00
for <[EMAIL PROTECTED]>; Fri, 02 Sep 2005 14:21:56 +0200
Message-ID: <[EMAIL PROTECTED]>
Date: Fri, 02 Sep 2005 14:21:52 +0200
From: Reinhard Vicinus <[EMAIL PROTECTED]>
User-Agent: Debian Thunderbird 1.0.6 (X11/20050802)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: Twofold MANIFEST.MF in saxon.jar
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: libsaxon-java
Version: 6.5.4-1
When I invoke the Saxon XSLT Processor an error occurs.
$ java -jar /usr/share/java/saxon-6.5.4.jar
Failed to load Main-Class manifest attribute from
/usr/share/java/saxon-6.5.4.jar
I think the java processor gets confused because there are two MANIFEST.MF
in the jar-file:
$ unzip -l /usr/share/java/saxon-6.5.4.jar
Archive: /usr/share/java/saxon-6.5.4.jar
Length Date Time Name
-------- ---- ---- ----
54843 08-17-05 01:53 META-INF/MANIFEST.MF
0 08-17-05 01:53 META-INF/
68 08-17-05 01:53 META-INF/MANIFEST.MF
...
I am using Debian GNU/Linux unstable kernel 2.6.12.3 build with
kernel-package
9.007 libc6 2.3.5-6 Sun Java 2 SDK 1.5 update 04 build with java-package
0.26
---------------------------------------
Received: (at 326207-close) by bugs.debian.org; 10 Sep 2005 20:38:29 +0000
>From [EMAIL PROTECTED] Sat Sep 10 13:38:29 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
id 1EEC1x-0001kS-00; Sat, 10 Sep 2005 13:32:57 -0700
From: Wolfgang Baer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#326207: fixed in libsaxon-java 1:6.5.4-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sat, 10 Sep 2005 13:32:57 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Source: libsaxon-java
Source-Version: 1:6.5.4-2
We believe that the bug you reported is fixed in the latest version of
libsaxon-java, which is due to be installed in the Debian FTP archive:
libsaxon-java-doc_6.5.4-2_all.deb
to pool/contrib/libs/libsaxon-java/libsaxon-java-doc_6.5.4-2_all.deb
libsaxon-java_6.5.4-2.diff.gz
to pool/main/libs/libsaxon-java/libsaxon-java_6.5.4-2.diff.gz
libsaxon-java_6.5.4-2.dsc
to pool/main/libs/libsaxon-java/libsaxon-java_6.5.4-2.dsc
libsaxon-java_6.5.4-2_all.deb
to pool/main/libs/libsaxon-java/libsaxon-java_6.5.4-2_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Wolfgang Baer <[EMAIL PROTECTED]> (supplier of updated libsaxon-java package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Tue, 06 Sep 2005 12:28:39 +0200
Source: libsaxon-java
Binary: libsaxon-java-doc libsaxon-java
Architecture: source all
Version: 1:6.5.4-2
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers
<[email protected]>
Changed-By: Wolfgang Baer <[EMAIL PROTECTED]>
Description:
libsaxon-java - The Saxon XSLT Processor
libsaxon-java-doc - The Saxon XSLT Processor's documentation and javadoc
Closes: 326207
Changes:
libsaxon-java (1:6.5.4-2) unstable; urgency=low
.
* Provide a Manifest file with Main-class entry and suppress
the automatic generation of a second Manifest file (closes: #326207)
* Added lintian override for wrong-name-for-upstream-changelog
as this is a needed html file of the manual
.
* Upload sponsored by Petter Reinholdtsen
Files:
5fcf37d5881ca75d2133dfa49b4129f7 780 libs optional libsaxon-java_6.5.4-2.dsc
e9f287c40b553c15dc1e2ba762aea81f 6115 libs optional
libsaxon-java_6.5.4-2.diff.gz
b3a2c2d271dd9c6286d42765fe350193 557420 libs optional
libsaxon-java_6.5.4-2_all.deb
370dc9a831afe4a47463e91030e7ffe2 1072788 contrib/doc optional
libsaxon-java-doc_6.5.4-2_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDIy4u20zMSyow1ykRAhCGAKC63Va0B3o8kUF9eW54DbnNYgR3pgCePB83
rcYHBEI9duGm37ZrsRa4Ayg=
=lvrP
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
