On Sat, Apr 03, 2004 at 12:22:27PM +0200, Matthias Klose wrote: > Steve Langasek writes: > > On Wed, Mar 31, 2004 at 09:34:18PM -0600, Steve Langasek wrote: > > > On Mon, Mar 29, 2004 at 05:33:57AM -0500, Nathanael Nerode wrote: > > > > For zope to be removed, one must also do this: > > > > remove zope-textindexng2/2.05-1 > > > > remove zope-zpatterns/0.4.3p2-17 > > > > > Cc'ing the maintainers of those packages, as they have an obvious vested > > > interest in keeping zope from being removed from sarge. Any takers for > > > NMU'ing (or MU'ing) zope to get these RC bugs fixed? Time is short. > > > > .... also cc:ing the maintainers of the various other zope packages that > > are arch: all, and would also have to be removed in order for zope to be > > removed from testing. > > > > The total list of packages that must be removed if zope is not > > releasable with sarge is as follows: > > > > plone > > python-extclass > > qmtest > The zope maintainers seem to be quiet ... Please before removing > qmtest, let me separate out the python-extclass package from the zope > package. I would expect that if there isn't clear progress on fixing zope's RC bugs within a week, I would be hinting it for removal, along with any packages depending on it at that time. If you are concerned that zope won't be fixed in this time period, I would suggest you start working on qmtest's dependencies immediately, so it can get back into testing ASAP. Since there has been an NMU offer, I'm still hopeful it won't come to that. Thanks, -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature