[xml/sgml-pkgs] Bug#232474: marked as done (libxerces23: adding config.status to -dev package)

Debian Bug Tracking System owner@bugs.debian.org
Wed, 05 May 2004 14:33:15 -0700

Your message dated Wed, 5 May 2004 17:25:38 -0400
with message-id <200405052125.i45LPcWe002972@soup.acv.apexcovantage.com>
and subject line fixed in 2.3.0-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; 13 Feb 2004 01:47:03 +0000
>From ejb@ql.org Thu Feb 12 17:47:03 2004
Return-path: <ejb@ql.org>
Received: from lakemtao01.cox.net [] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1ArSQ3-0007Cs-00; Thu, 12 Feb 2004 17:47:03 -0800
Received: from gwendolyn.in.ql.org ([]) by lakemtao01.cox.net
          (InterMail vM. 201-253-122-130-105-20030824) with ESMTP
          id <20040213014633.JQGB13731.lakemtao01.cox.net@gwendolyn.in.ql.org>;
          Thu, 12 Feb 2004 20:46:33 -0500
Received: from soup.in.ql.org (soup.in.ql.org [])
	by gwendolyn.in.ql.org (8.12.11/8.12.11/Debian-1) with ESMTP id i1D1kWIj025371;
	Thu, 12 Feb 2004 20:46:32 -0500
Received: from soup.in.ql.org (localhost [])
	by soup.in.ql.org (8.12.11/8.12.11/Debian-1) with ESMTP id i1D1kVLN014617;
	Thu, 12 Feb 2004 20:46:31 -0500
Received: (from ejb@localhost)
	by soup.in.ql.org (8.12.11/8.12.11/Debian-1) id i1D1kVkG014615;
	Thu, 12 Feb 2004 20:46:31 -0500
Message-Id: <200402130146.i1D1kVkG014615@soup.in.ql.org>
Content-Type: multipart/mixed; boundary="===============1731897114=="
MIME-Version: 1.0
From: Jay Berkenbilt <ejb@ql.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: libxerces23: adding config.status to -dev package
X-Mailer: reportbug 2.43
Date: Thu, 12 Feb 2004 20:46:31 -0500
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_12 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no 

This is a multi-part MIME message sent by reportbug.

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: libxerces23
Version: 2.3.0-2
Severity: normal
Tags: patch

I am in the process of packaging libxml-xerces-perl version 2.3.0-4.
This package requires the config.status used to build xerces-c in
order to be configured.

This patch causes the file /usr/share/libxerces-c/config.status to be
added to the -dev package.  I'm quite new to Debian, and this is my
first attempt at packaging something or modifying an existing package.
Although I have read the policy and developer's reference, I'm still
not quite sure whether I've handled this correctly.  Is this the right
place to put the file?  I think it has to go in /usr/share.  It
doesn't seem to need to be a version-specific since the libxerces23
packages conflict with those of earlier versions.

This patch is relative to the extracted source for the libxerces23
package.  In other words:

mkdir x
cd x
apt-get source libxerces23
patch -p0 < this-patch
fakeroot dpkg-buildpackage

All I've done is add a few lines to the install-native target to
create this directory and copy config.status into it.  My packaging of
libxml-xerces-perl, which I will discuss in bug 225305, depends upon
this.  I've also added appropriate changelog entries so that I could
test to make sure that "fakeroot dpkg-buildpackage" would build usable
packages.  (Removal of the emacs local variables from the changelog
file was done by M-x debian-changelog-add-entry.)

Note that I am not a Debian developer (though I am planning on
pursuing this goal), so I can't upload, etc.  As we discussed in bug
225305, you are willing to have an NMU done on libxml-xerces-perl.  If
you'd like this also to be an NMU, how should we handle it?  Should I
site this bug and post to debian-mentors looking for a sponsor, or
will you be able to accept/upload this rather than going the NMU
route?  I'm interested in helping out any way I can.

Also, if you disagree with where I put the config.status file, just
let me know so I can change it.  Thanks.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.24-q-xfs
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

Versions of packages libxerces23 depends on:
ii  libc6                      2.3.2.ds1-11  GNU C Library: Shared libraries an
ii  libgcc1                    1:3.3.3-0pre3 GCC support library
ii  libstdc++5                 1:3.3.3-0pre3 The GNU Standard C++ Library v3

-- no debconf information

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="libxerces23-config_status.diff"

diff -urw ../xerc23.orig/xerces23-2.3.0/debian/changelog xerces23-2.3.0/debian/changelog
--- ../xerc23.orig/xerces23-2.3.0/debian/changelog	2004-02-12 20:25:01.000000000 -0500
+++ xerces23-2.3.0/debian/changelog	2004-02-12 19:29:48.000000000 -0500
@@ -1,3 +1,11 @@
+xerces23 (2.3.0-2) unstable; urgency=low
+  * Changes to -dev package to support building libxml-xerces-perl version
+    2.3.0.
+  * debian/rules: install config.status for -dev package
+ -- Jay Berkenbilt <ejb@ql.org>  Thu, 12 Feb 2004 19:27:32 -0500
 xerces23 (2.3.0-1) unstable; urgency=low
   * New upstream version.  (Package is based on xerces21.)
@@ -59,6 +67,4 @@
  -- Guillaume Morin <gemorin@debian.org>  Tue, 03 Sep 2002 11:50:24 +0200
-Local variables:
-mode: debian-changelog
diff -urw ../xerc23.orig/xerces23-2.3.0/debian/rules xerces23-2.3.0/debian/rules
--- ../xerc23.orig/xerces23-2.3.0/debian/rules	2004-02-12 20:25:01.000000000 -0500
+++ xerces23-2.3.0/debian/rules	2004-02-12 19:21:47.000000000 -0500
@@ -89,6 +89,10 @@
 	# rm $(pkg_root)/$(package_libxerces_dev)/usr/
+	# Install config.status, which is needed to build libxml-xerces-perl.
+	mkdir -p $(pkg_root)/$(package_libxerces_dev)/usr/share/$(libname)
+	cp $(BUILD_DIR)/src/xercesc/config.status $(pkg_root)/$(package_libxerces_dev)/usr/share/$(libname)
 install-icu: build-icu


Received: (at 232474-done) by bugs.debian.org; 5 May 2004 21:25:46 +0000
>From ejb@apexcovantage.com Wed May 05 14:25:46 2004
Return-path: <ejb@apexcovantage.com>
Received: from through.apexcovantage.com (through.acv.apexcovantage.com) [] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BLTth-0006c9-00; Wed, 05 May 2004 14:25:46 -0700
Received: from apex.acv.apexcovantage.com (apex.acv.apexcovantage.com [])
	by through.acv.apexcovantage.com (8.12.8/8.12.8/apexcovantage-gateway-1.0) with ESMTP id i45LPcbc024687;
	Wed, 5 May 2004 17:25:38 -0400
Received: from soup.acv.apexcovantage.com (soup.acv.apexcovantage.com [])
	by apex.acv.apexcovantage.com (8.12.8/8.12.8/ads-apexcovantage-hub-1.1.b1) with ESMTP id i45LPcaP028448;
	Wed, 5 May 2004 17:25:38 -0400
Received: from soup.acv.apexcovantage.com (soup [])
	by soup.acv.apexcovantage.com (8.12.11/8.12.11/Debian-5) with ESMTP id i45LPceN002976;
	Wed, 5 May 2004 17:25:38 -0400
Received: (from ejb@localhost)
	by soup.acv.apexcovantage.com (8.12.11/8.12.11/Debian-5) id i45LPcWe002972;
	Wed, 5 May 2004 17:25:38 -0400
Date: Wed, 5 May 2004 17:25:38 -0400
Message-Id: <200405052125.i45LPcWe002972@soup.acv.apexcovantage.com>
From: Jay Berkenbilt <ejb@ql.org>
To: 234230-done@bugs.debian.org, 232474-done@bugs.debian.org
Subject: fixed in 2.3.0-2
X-Apex-MailScanner-Information: Scanned by Apex with MailScanner
X-Apex-MailScanner: Found to be clean
X-MailScanner-From: ejb@apexcovantage.com
Delivered-To: 232474-done@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=-2.0 required=4.0 tests=BAYES_00 autolearn=no 
X-CrossAssassin-Score: 1

This is fixed in 2.3.0-2.  The upload was interpreted as an NMU, but
the maintainer field is now correct, so these bugs are being closed