[Pkg-zope-developers] Re: Removing zope

[Steve Langasek]

--jousvV0MzM2p6OtC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Apr 01, 2004 at 07:08:18AM +0200, Andreas Tille wrote:
> On Wed, 31 Mar 2004, Steve Langasek wrote:
>=20
> > 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.
> Uhm - what????
> Well, today is Aprils fools, but the initial mail was not from today.

I'm sorry, no.  The zope package appears to be in bad shape right now,
and requires the attention of a concerned maintainer, or it will not be
releasable with sarge; and that unfortunately means 51 other source
packages will have to be removed with it.

> You do not really intend to remove, do you?

I don't particularly look forward to writing the hint to remove 52
packages from testing -- I'd much prefer that somebody step forward to
fix the one package at the root of the problem.  Thank you very much for
doing so.

On Thu, Apr 01, 2004 at 07:29:16AM +0200, Andreas Tille wrote:
> On Wed, 31 Mar 2004, 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.

> While I regard this more or less as an Aprils fools joke I think we should
> definitely clean up BTS:

>   #238878: I do not really understand this bug but I guess it's "normal"
>            and not "grave"
>   #229368 + #232648: Same bug - should be merged.
>            -> hey is something stoping zope package uploaders from fixing=
 this???
>   #222443: the state to this bug is unclear to me.
>            Could somebody verify whether this bug exists also in the curr=
ent
>            Zope version (2.6.4)?
>   #196590: No issue for sarge release.

> So the situation seems to be easy: Merge and fix #229368 + #232648,
> downgrade #238878 and veryfy #222443  -> done for Sarge release.

One RC bug is still one too many, of course.  And the latest follow-up
=66rom Gregor on 222443 suggests that the bug is still present in the
current version of the package.  That leaves two should-be-trivial RC
bugs that need to be fixed.

Thanks,
--=20
Steve Langasek
postmodern programmer

--jousvV0MzM2p6OtC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAa7D9KN6ufymYLloRAiKmAJ4+N9hi06XupYv9WdvNS89LmKDAzQCdHUJi
/uUaTZ6aHdajds9Nw9M/A38=
=SJUL
-----END PGP SIGNATURE-----

--jousvV0MzM2p6OtC--