[Pkg-zope-developers] Re: zope-common and dh-zope, new packages

martin f krafft madduck@debian.org
Tue, 29 Mar 2005 14:57:50 +0200


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

also sprach Fabio Tranchitella <kobold@kobold.it> [2005.03.29.1450 +0200]:
> Ok, so I'd like to take over Luca zope packages if nobody disagree.

Well, how about we take them over? I don't believe in single-person
maintainership. I think we should set the Maintainer field to the
list address and you and I and whomever else to the Uploaders field.

> They are pre-release, are new upstream release not yet uploaded in
> sid.

Okay, just making sure.

> > ... well, except it broke my setup, and I cannot find out
> > anymore why.=20
>=20
> You are talking about zope (=3D 2.6), which have a totally different
> behaviour than zope2.7 (and which I hadn't tested at all).

Yeah, but the zope2.7 upgrade over easter broke my 2.6 setup. If
this happens in stable, it's a grave bug. Thus, we cannot let it
enter sarge until it is fixed and/or found to be limited to my
setup.

> > We can upload zope-common, but only if it either does not
> > interfere with 2.6 installations, or if it has been thoroughly
> > tested.
>=20
> I'm preparing a reduced *sarge-specific* zope-common.

What's the benefit?

--=20
 .''`.     martin f. krafft <madduck@debian.org>
: :'  :    proud Debian developer, admin, user, and author
`. `'`
  `-  Debian - when you have better things to do than fixing a system
=20
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!
=20
"there are more things in heaven and earth, horatio,
 than are dreamt of in your philosophy."
                                                             -- hamlet

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

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

iD8DBQFCSVDOIgvIgzMMSnURAnhqAJ9GQPY4noNdQvbJZJdZFJy3GZYbIQCcCmR2
EssseLbIQJrubAFs2SGlz74=
=LPcy
-----END PGP SIGNATURE-----

--fdj2RfSjLxBAspz7--