[Pkg-zope-developers] Re: python-mysqldb in sarge and python2.2 support (for zope-mysqlda)

Steve Langasek vorlon@debian.org
Sat, 30 Apr 2005 20:59:51 -0700


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

Hi Jonas,

On Fri, Apr 29, 2005 at 04:51:17PM +0200, Jonas Meurer wrote:
> i've a problem with packaging python-mysqldb. version 1.2 is already
> uploaded to unstable, and has no bugs while version 1.1.6
> - currently in testing - has a rc bug: #306906

> on the other side python-mysqldb 1.2 lacks python2.2 support, and
> thus no python2.2-mysqldb package exists any longer.
> the problem with that is, that zope-mysqlda depends on python2.2-mysqldb,
> and really requires it, as zope (2.6) doesn't run with python !=3D 2.2.

> the only possibilities i see are
> 1. remove zope-mysqlda from the archive and push python-mysqldb 1.2
>    [without python2.2 support] into sarge, but i don't like that idea
>    too much.
>    for this solution i've already prepared zope2.7-mysqlda packages that
>    use python2.3-mysqldb to provide at least a mysql db adapter for
>    zope2.7 even if none will be included for zope2.6.

> 2. backport the fixes for bug#306906 from 1.2 to 1.1.6 and prepare a
>    sarge release with python2.2. i do like this idea but up to now i
>    couldn't find out which one is the corresponding code change in
>    python-mysqldb to fix #306906.

Release-wise, whichever of these options that you believe is most
appropriate would be acceptable.

Thanks,
--=20
Steve Langasek
postmodern programmer

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

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

iD8DBQFCdFQzKN6ufymYLloRAuyNAJsHr1JOQ3VP/NfKTPTrzaoMpnqvBwCguaMI
3Txv5/wrlq9cndHHZB83MHA=
=4fCD
-----END PGP SIGNATURE-----

--t0UkRYy7tHLRMCai--