Bug#268786: marked as done (libxml-commons-resolver1.1-java: does not install CatalogManager.properties file)
Debian Bug Tracking System
owner@bugs.debian.org
Sun Oct 10 18:24:03 2004
Your message dated Sun, 10 Oct 2004 20:02:05 -0400
with message-id <E1CGndd-0003Ew-00@newraff.debian.org>
and subject line Bug#268786: fixed in libxml-commons-resolver1.1-java 1.1-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 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; 29 Aug 2004 04:36:02 +0000
>From msmith@sideshowbarker.net Sat Aug 28 21:36:02 2004
Return-path: <msmith@sideshowbarker.net>
Received: from sideshowbarker.vm.bytemark.co.uk [212.13.211.65]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C1HQA-0006Fb-00; Sat, 28 Aug 2004 21:36:02 -0700
Received: from msmith by sideshowbarker.vm.bytemark.co.uk with local (Exim 4.34)
id 1C1HQ6-0000CX-Dl; Sun, 29 Aug 2004 13:35:58 +0900
Date: Sun, 29 Aug 2004 13:35:58 +0900
From: Michael Smith <smith@xml-doc.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Bcc: Michael Smith <msmith@sideshowbarker.net>
Subject: libxml-commons-resolver1.1-java: does not install CatalogManager.properties file
Message-ID: <20040829043557.GA32172@sideshowbarker.net>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="r5Pyd7+fXNt84Ff3"
Content-Disposition: inline
X-Reportbug-Version: 2.63
User-Agent: Mutt/1.5.6i
Sender: Michael Smith <msmith@sideshowbarker.net>
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: msmith@sideshowbarker.net
X-SA-Exim-Scanned: No (on sideshowbarker.vm.bytemark.co.uk); SAEximRunCond expanded to false
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Package: libxml-commons-resolver1.1-java
Version: 1.1-3
Severity: normal
Hi,
Is there a reason why libxml-commons-resolver1.1-java doesn't
install a CatalogManager.properties file?
I think it should and /etc/xml-commons-resolver/CatalogManager.properties
seems like an appropriate location.
As far as the content of the file, there's an upstream example at:
http://xml.apache.org/commons/components/resolver/CatalogManager.properties
But that shouldn't be used off-the-self. At a minimum, the value
for the 'catalogs' property should be changed. It should be:
catalogs=/etc/xml/catalog
Also, maybe the default for the 'verbosity' property should be
cranked down. The default in the upstream example file is '99',
which is the max. I reckon most users will probably get annoyed by
the amount of reporting that generates.
If/when the package is updated to install CatalogManager.properties,
the README.Debian file should be updated to tell people how to use -
This package installs a CatalogManager.properties file in the
/etc/xml-commons-resolver directory. Among other things, the
CatalogManager.properties file tells the resolver where to find
XML catalog files to use. Debian uses a single master catalog
file -- /etc/xml/catalog -- so the CatalogManager.properties
that this package installs points to that file.
In order for the resolver to be able to find and use the
CatalogManager.properties files, you need to include the
*directory* that contains it -- the /etc/xml-commons-resolver
directory -- in your Java classpath, either by specifying it on
the Java command-line or via the CLASSPATH environment variable:
export CLASSPATH=/etc/xml-commons-resolver:$CLASSPATH
That's it. Thanks,
--Mike Smith
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (70, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-bytemark-uml-20040706-1
Locale: LANG=C, LC_CTYPE=C
Versions of packages libxml-commons-resolver1.1-java depends on:
hi j2re1.3 [java2-runtime] 1.3.1.02b-2 Blackdown Java(TM) 2 Runtime Envir
ii j2re1.4 [java2-runtime] 1.4.1.99rc1-2 Blackdown Java(TM) 2 Runtime Envir
ii sablevm [java1-runtime] 1.1.6-2 Free implementation of Java Virtua
-- no debconf information
--r5Pyd7+fXNt84Ff3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="CatalogManager.properties"
########################################################################
# CatalogManager provides an interface to the catalog properties.
# Properties can come from two places: from system properties or
# from a CatalogManager.properties file. This class provides a
# transparent interface to both, with system properties preferred
# over property file values.
#######################################################################
# Catalog Files:
# The semicolon-delimited list of catalog files.
# Example: catalogs=./xcatalog;/share/doctypes/catalog
catalogs=/etc/xml/catalog
#######################################################################
# Relative Catalogs:
# If false, relative catalog URIs are made absolute with respect to the
# base URI of the CatalogManager.properties file. This setting only
# applies to catalog URIs obtained from the catalogs property in the
# CatalogManager.properties file
# Example: relative-catalogs = [yes|no]
relative-catalogs=yes
#######################################################################
# Verbosity:
# If non-zero, the Catalog classes will print informative and debugging
# messages. The higher the number, the more messages.
# Example: verbosity = [0..99]
verbosity=99
#######################################################################
# Prefer:
# Which identifier is preferred, "public" or "system"?
# Example: xml.catalog.prefer = [public|system]
prefer=system
#######################################################################
# Static-catalog:
# Should a single catalog be constructed for all parsing, or should a
# different catalog be created for each parser?
# Example: static-catalog = [yes|no]
static-catalog=yes
#######################################################################
# Allow-oasis-xml-catalog-pi
# If the source document contains "oasis-xml-catalog" processing
# instructions, should they be used?
# Example: allow-oasis-xml-catalog-pi = [yes|no]
allow-oasis-xml-catalog-pi=yes
#######################################################################
# catalog-class-name
# If you're using the convenience classes
# org.apache.xml.resolver.tools.*, this setting allows you to specify
# an alternate class name to use for the underlying catalog.
# Example: catalog-class-name=org.apache.xml.resolver.Resolver
--r5Pyd7+fXNt84Ff3--
---------------------------------------
Received: (at 268786-close) by bugs.debian.org; 11 Oct 2004 00:08:01 +0000
>From katie@ftp-master.debian.org Sun Oct 10 17:08:01 2004
Return-path: <katie@ftp-master.debian.org>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CGnjN-0000Qc-00; Sun, 10 Oct 2004 17:08:01 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1CGndd-0003Ew-00; Sun, 10 Oct 2004 20:02:05 -0400
From: Arnaud Vandyck <avdyk@debian.org>
To: 268786-close@bugs.debian.org
X-Katie: $Revision: 1.51 $
Subject: Bug#268786: fixed in libxml-commons-resolver1.1-java 1.1-4
Message-Id: <E1CGndd-0003Ew-00@newraff.debian.org>
Sender: Archive Administrator <katie@ftp-master.debian.org>
Date: Sun, 10 Oct 2004 20:02:05 -0400
Delivered-To: 268786-close@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Source: libxml-commons-resolver1.1-java
Source-Version: 1.1-4
We believe that the bug you reported is fixed in the latest version of
libxml-commons-resolver1.1-java, which is due to be installed in the Debian FTP archive:
libxml-commons-resolver1.1-java-doc_1.1-4_all.deb
to pool/main/libx/libxml-commons-resolver1.1-java/libxml-commons-resolver1.1-java-doc_1.1-4_all.deb
libxml-commons-resolver1.1-java_1.1-4.diff.gz
to pool/main/libx/libxml-commons-resolver1.1-java/libxml-commons-resolver1.1-java_1.1-4.diff.gz
libxml-commons-resolver1.1-java_1.1-4.dsc
to pool/main/libx/libxml-commons-resolver1.1-java/libxml-commons-resolver1.1-java_1.1-4.dsc
libxml-commons-resolver1.1-java_1.1-4_all.deb
to pool/main/libx/libxml-commons-resolver1.1-java/libxml-commons-resolver1.1-java_1.1-4_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 268786@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Arnaud Vandyck <avdyk@debian.org> (supplier of updated libxml-commons-resolver1.1-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 ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Mon, 11 Oct 2004 01:41:20 +0200
Source: libxml-commons-resolver1.1-java
Binary: libxml-commons-resolver1.1-java-doc libxml-commons-resolver1.1-java
Architecture: source all
Version: 1.1-4
Distribution: unstable
Urgency: low
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Changed-By: Arnaud Vandyck <avdyk@debian.org>
Description:
libxml-commons-resolver1.1-java - XML entity and URI resolver library
libxml-commons-resolver1.1-java-doc - XML entity and URI resolver library -- documentation
Closes: 268786
Changes:
libxml-commons-resolver1.1-java (1.1-4) unstable; urgency=low
.
* added CatalogManager.properties to /etc/xml/resolver (closes: #268786)
Files:
bc6cabd98efe38aec247085ae036c5b8 897 libs optional libxml-commons-resolver1.1-java_1.1-4.dsc
3e27d70bc1300478a96b1c27473dca91 3876 libs optional libxml-commons-resolver1.1-java_1.1-4.diff.gz
3056e2c35b1fb84d903893882c162fb1 70256 libs optional libxml-commons-resolver1.1-java_1.1-4_all.deb
9d014b22b35e9de31322fee0dcba7f10 116530 doc optional libxml-commons-resolver1.1-java-doc_1.1-4_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFBacud4vzFZu62tMIRAgTAAJoCk0lRvEetwbbNExYucuyAdqP1oACfZgJK
N0pi67Vc4r73lCqc4DaeWSU=
=dUzu
-----END PGP SIGNATURE-----