On Sun, 15, Jun, 2008 at 09:36:54PM -0400, Jay Berkenbilt spoke thus..
> Package: ftp.debian.org
> Severity: normal
> 
> I am requesting removal of the xerces28 source package and its
> associated binary packages from unstable.  Since April 20, the version
> of xerces28 in lenny has been a transitional package, and I think two
> months is long enough for it to do its job considering the low popcon
> of xerces28 and the fact that it had hardly any reverse dependencies.
> The only package that I'm aware of that has a build dependency on
> libxerces28-dev is xqilla which I see has been removed from testing as
> of 2008-06-15 and which I filed a bug against already.  There appear
> to be no packages with a dependency on libxerces28 since the most
> recent rebuild of xqilla already took care of that (via the
> transitional packages).

xqilla still has a Build-Dependency on libxerces28-dev:

[EMAIL PROTECTED]:~$ dak rm -n -p -d 486430 -R -C package -m "ROM; renamed: 
replaced by xerces-c2" xerces28
Working... done.
Will remove the following packages from unstable:

libxerces28 | 2.8.0+dummy-1 | alpha, amd64, arm, armel, hppa, hurd-i386, i386, 
ia64, m68k, mips, mipsel, powerpc, s390, sparc
libxerces28-dev | 2.8.0+dummy-1 | alpha, amd64, arm, armel, hppa, hurd-i386, 
i386, ia64, m68k, mips, mipsel, powerpc, s390, sparc
libxerces28-doc | 2.8.0+dummy-1 | all
  xerces28 | 2.8.0+dummy-1 | source

Maintainer: Jay Berkenbilt <[EMAIL PROTECTED]>
Will also close bugs: 486430
Will also send CCs to: [EMAIL PROTECTED], [EMAIL PROTECTED]

------------------- Reason -------------------
ROM; renamed: replaced by xerces-c2
----------------------------------------------

Checking reverse dependencies...
** xqilla has an unsatisfied build-dependency: libxerces28-dev
Dependency problem found.

-- 
Mark Hymers <mhy at debian dot org>

"Oh simple thing, Where have you gone?
 I'm getting old and I need something to rely on."
     Somewhere Only We Know, Keane



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to