Re: need help in resolving the Apache-Expat-XML::Parser conflict

2001-09-12 Thread Ardo van Rangelrooij
Jonathan McDowell ([EMAIL PROTECTED]) wrote: On Sun, Sep 09, 2001 at 03:51:05PM -0500, Ardo van Rangelrooij wrote: [AxKit not working due to Apache expat linkage] I've no problem NMU'ing apache, but that might break other packages (which?). There are two ways to NMU: 1. leave out

Re: need help in resolving the Apache-Expat-XML::Parser conflict

2001-09-12 Thread Ardo van Rangelrooij
Bart Schuller ([EMAIL PROTECTED]) wrote: I've no problem NMU'ing apache, but that might break other packages (which?). There are two ways to NMU: 1. leave out expat: this is the simplest way since it only requires a small change in the debian/rules file 2. build with the

need help in resolving the Apache-Expat-XML::Parser conflict

2001-09-09 Thread Ardo van Rangelrooij
Hi, One of the packages I maintain is AxKit (an XML Application Server for Apache). It depends for a part of its functionality on the latest version of Expat (via XML::Parser). Unfortunately, the version of Apache currently in sid is build with its own (older!) version of Expat. This results in

Re: need help in resolving the Apache-Expat-XML::Parser conflict

2001-09-09 Thread Jonathan McDowell
On Sun, Sep 09, 2001 at 03:51:05PM -0500, Ardo van Rangelrooij wrote: [AxKit not working due to Apache expat linkage] I've no problem NMU'ing apache, but that might break other packages (which?). There are two ways to NMU: 1. leave out expat: this is the simplest way since it only