This bug was fixed in the package gaphor - 0.13.0-1ubuntu2
---
gaphor (0.13.0-1ubuntu2) karmic; urgency=low
* debian/control:
- Replace zope3 with python-zope.interface, python-zope.component
(lp: #144377)
- Replace python-gnome2 with python-gconf (closes: #541583)
I've a working package which doesn't depend on zope3 (which is scheduled
for removal from karmic anyways) but I need first to get the needed
dependencies synced before I'll upload it.
--
gaphor depends on zope3
https://bugs.launchpad.net/bugs/144377
You received this bug notification because you
Gaphor also requires Zope Component which is not included in python-
zopeinterface. I found a new Debian package here: http://ftp-
master.debian.org/new/zope.component_3.7.0-1.html but did not come
across a bug report.
--
gaphor depends on zope3
https://bugs.launchpad.net/bugs/144377
You
Apparently a reorg of how Zope is packaged is freshly under way in
Debian. The reorg will ditch the monolithic zope3 package in favour of
packaging all the various parts separately. I guess once this is done
this bug should be easy to fix.
http://lists.alioth.debian.org/pipermail/pkg-zope-
Is this really a wishlist item? I see it as a bug that needs to be
resolved asap.
The dependency on the full zope3 service is entirely unnecessary. As it
is, our packages attach an incredible amount of bloat on Gaphor's
behalf. Installing it from the repository also installs a VERY
significant
