zope2.13

[Jonas Meurer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey, and sorry for the late reply as well.

Michael, it's great to read that you're interested in helping out with
Debian/Ubuntu zope packages. This is definitelly the place to ask and
discuss. Obviously all people involved are rather busy and don't even
have the time answer your simple questions. That's very unfortunate,
and I apologize for that.

Unfortunately I don't have enough spare time to work on zope2.13
packages right now, and I would very much appreciate help with this task.


Am 16.12.2011 06:16, schrieb Arnaud Fontaine:
> Hello,
> 
> Sorry for the late reply.
> 
> Michael Terry <michael.terry at canonical.com> writes:
> 
>> For  Ubuntu  12.04, Python  2.7  will  be  the only  supported
>> Python version.   After  talking  to  some  other  Zope  people,
>> they  don't recommend trying  to cobble python2.7 and  zope2.12
>> together.  Rather, they suggested packaging zope2.13 and/or
>> dropping zope2.12 altogether.
> 
> Yes, uploading Zope2.13 is better  as the official supported
> version for 2.12 is Python 2.6 only.

As Debian bug #653802 shows, this will be a issue for the Debian
Wheezy release as well. Python maintainers intend to drop python2.6 in
time for Wheezy. This is blocked by the zope2.12 package, the last
non-trivial package in the unstable/testing archive, that depends on
python2.6.

>> I see that your team has a zope2.13 trunk.  Do you know when that
>> will be released as a package into unstable?
>> 
>> As a person not familiar with zope packaging, I'm curious what
>> kind of problems  do  you expect  from  the  zope2.12 to
>> zope2.13  transition (i.e. is it more than a rebuild of rdepends
>> with bumped versions)?
>> 
>> Is it possible for your team  to release zope2.13 into
>> experimental to be synced  into Ubuntu  and thus maybe  receive
>> some  further testing? From my perspective,  the sooner the
>> transition starts  in Ubuntu, the better.
> 
> I don't  think there  could be  any problem  with uploading
> zope2.13 to experimental,  but  maybe Jonas  or  Gaël  are  more
> familiar  with  the possible issue with  transition from 2.12 to
> 2.13 and  if 2.12 should be dropped in favor of 2.13?

Last time I looked into it, the zope2.13 packages from svn built just
fine, but the Zope2 server didn't work out of the box. I didn't find
time until then to dig into the issue, thus I don't have further
information. But I would object against uploading unusable zope2.13
packages to experimental.

If you want to help with zope2.13 packages, and plan to bring them in
shape for Ubuntu 12.04., I suggest that you start with the packages
from svn, build them yourself, install them and give them a try. Don't
hesitate to ask on this list, if you experience any problems and don't
know yourself how to fix them.

Regards,
 jonas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPCHm+AAoJEFJi5/9JEEn+UjQP/je3Z3UGQnRqefyBevd269SE
5CPCq5JVe2hUAD456Dm/iWmHI4faIQZYaJLwW6udpvVd0BCDQFFPNfq1AJTxOb62
n+lEemO4s+xGbQTr1WWHpzk9vB3OTVDm0x3/Jf9rgSTr07n+UjPv570ctZVrlwLl
pMX0DBaWJ9ez4ACd0SVg99EJyi5jWBiMtf5PdkNrPT2GJxh9Ct/7Bdg1dFnpHtFp
UpNABh2XHbr4kLbkgDmD1m/6PaJblN9kXe+jUOURVWTlt+t58lGtDU8mrGTTnNf1
HR+0gaKoGCpe2DGRukW155/IbphycD82wVHUchaS99rlUYQOhfzS1nI+msFDYrrU
GQEmpBriWQi4aHNCI3tdGRhqDse7FDvyxQP9L3wtR2Qot20ivzBsOLdcgaAGPxsG
PurqACkw0MabUIKYcjJb6DhMVMF3krk97hWCAT8we69ZKnH4y3PsjsUS6Q1dHJeB
dW3Q3NukfzxjPDu5E7m/PFI1ZNTYWjiW5P5kJ/EEEFvYcK+i4ss9CXxVaK88pS/c
i/r/regxelWpTteBktlmP0cmPJZbag1xfhhrA0SH42mPaUmECvQ2YZDVmFk0ujKW
8QQLOZxWayt0FC0y0jgxDfPVoA1E/R4RRfY6hwD5XbIgjsOT7u9cFlFhGohzSRa2
+NVDidDXqx8UutieNJrJ
=mrj1
-----END PGP SIGNATURE-----