hey, On 06/08/2009 Holger Levsen wrote: > during a test with piuparts I noticed your package starts processes where it > shouldnt. This is very probably due to not using invoke-rc.d as mandated by > policy 9.3.3.2. This is seriously disturbing! ;-) > > See http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3 > and /usr/share/doc/sysv-rc/README.invoke-rc.d.gz as well > as /usr/share/doc/sysv-rc/README.policy-rc.d.gz > > From the attached log (scroll to the bottom...): > > Setting up zope2.11-sandbox (2.11.3-1) ... > . > daemon process started, pid=17342 > Processing triggers for python-support ... > [...] > 0m41.7s ERROR: FAIL: Processes are running inside chroot:
i suggest to fix these bugs the following way: patch the initscripts to support "INSTANCE=<instance>" or "ZEOSERVER=<zeoserver>" as second argument ($2) and start the particular given server/instance. then fix all zope-debhelper scripts to use invoke-rc.d with appropriate arguments instead of using dzhandle zeoctl|zopectl directly. i already commited the relevant changes to zope-debhelper, zope2.11 and zope2.10 to the svn repository. only package that is left is zope3. i left that one open to others as i don't know nothing about zope3. any objections? if not, i would suggest to upload zope-debhelper within the next days, wait until it reached unstable and then upload zope3/zope2.11/zope2.10 with build-depends on new zope-debhelper. only drawback is, that building old zope3/2.11/2.10/... packages with new zope-debhelper will break. do you think that adding a Breaks: header to zope-debhelper for old zope packages would be necessary? greetings, jonas
signature.asc
Description: Digital signature