Zope in Maverick

The Plan

The next version of Zope 3 will be known as BlueBream 1.0 and is due in June 10th. This gives us a stable set of packages and their versions at the right time in Maverick cycle, so we can package that and not chase a moving target.

However, since the only application based on Zope in Ubuntu will be SchoolTool (unless Zope 2/Plone is packaged again in Debian), we are not going to package every library, but only a subset that is needed by SchoolTool, plus libraries like z3c.form that are not included in BlueBream.

Debian

Question: We have added several Zope packages to Lucid that were not in Debian (see SchoolTool/Lucid at the bottom). Do we continue this way or do we have to package to Debian first? Anyone a Debian developer?

Answer: MatthiasKlose said that we upload to Ubuntu with debian revision -0ubuntu1 and may also commit to the pkg-zope subversion repository with debian revision -1. If someone gets to upload this to Debian then good, will be synced to Ubuntu as well, but getting stuff into Debian is not our priority.

Launchpad

Question: There is a team https://launchpad.net/~pkg-zope/ that has some members but is not used. Another team, https://launchpad.net/~pkg-zope-developers/ was automatically created when importing packages from Debian, and is automatically subscribed to bugs reported on zope packages, but not packages exclusive to Debian (e.g. zope.pagetemplate). This team is not owned by anyone, so that cannot be fixed. I (menesis) intend to take over this team. I would like to get notifications about all ubuntu/zope.* bugs.

Answer: Just ignore pkg-zope-developers, the Debian team, and use pkg-zope to subscribe all Zope related packages in Ubuntu. The request to make menesis an administrator of this team was sent.

MOTU Team

There is a Zope/Plone MOTU Team that is non-functioning. I would like to revive it if that makes sense to have in addition to the two aforementioned teams.

Tools

van.pydeb is used by all packages to generate their dependencies and provides. There are two ways to use it, the preferred one is the debhelper 7 extension. However, the tool is not perfect, and is not a proper extension -- should be rewritten in Perl. We are not happy about it's behavior, e.g. namespace packages like python-zope.app added to the dependencies (LP: #563211), and setuptools requirement converted to python-pkg-resources dependency (LP: #563060).

autopkgtest can be used for automated package testing, but no buildbot testing all the packages exists yet.

Package template

All of packages are based on the same template. It is uploaded to http://source.schooltool.org/var/local/bzr/ubuntu/templates/pydeb-dh7-all/ ...

More questions

...