Bug#390321: Re #390321: zope3-sandbox removal is also ugly

[Ross Boylan]

After receiving the same errors reported in this bug on the latest
upgrade to zope3-sandbox (3.3.0-6) from 3.3.0-5, I decided the easiest
thing was to get rid of it.  That produced quite a few errors:

# date; apt-get -q --purge remove zope3-sandbox
Thu Feb  8 11:18:46 PST 2007
Reading package lists...
Building dependency tree...
The following packages will be REMOVED:
  zope3-sandbox*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives.
After unpacking 106kB disk space will be freed.
Do you want to continue [Y/n]?
(Reading database ... 298003 files and directories currently installed.)
Removing zope3-sandbox ...
Traceback (most recent call last):
  File "/var/lib/zope3/instance/sandbox/bin/zopectl", line 43, in ?
    run()
  File "/var/lib/zope3/instance/sandbox/bin/zopectl", line 37, in run
    import zope.app.server.controller
ImportError: No module named controller
Traceback (most recent call last):
  File "/var/lib/zope3/instance/sandbox/bin/zopectl", line 43, in ?
    run()
  File "/var/lib/zope3/instance/sandbox/bin/zopectl", line 37, in run
    import zope.app.server.controller
ImportError: No module named controller
Purging configuration files for zope3-sandbox ...

However, the operation seems to have worked.  /var/lib/zope3/instance
is empty (I think the sandbox was my only one) and the dpkg status of
zope3-sandbox is pn.