While this is indeed a zope3 bug, in the long term gaphor would need to depend directly on the python-zope.* pacakges it requires.
These have just recently entered unstable: http://packages.debian.org/search?keywords=python-zope On Tue, Jul 14, 2009 at 11:59:08AM +0200, Michael Schutte wrote: > severity 536419 serious > thanks > > On Thu, Jul 09, 2009 at 09:28:44PM +0300, Andrew O. Shadoura wrote: > > Hello. > > > > Just have tried to install gaphor which uses zope3, and install was > > completely > > broken: > > > > [???] > > Setting up python-mechanize (0.1.7b-3) ... > > pycentral: pycentral pkginstall: not overwriting local files: > > /usr/lib/python2.5/site-packages/mechanize/__init__.py > > /usr/lib/python2.5/site-packages/mechanize/_auth.py > > /usr/lib/python2.5/site-packages/mechanize/_clientcookie.py > > /usr/lib/python2.5/site-packages/mechanize/_gzip.py > > /usr/lib/python2.5/site-packages/mechanize/_headersutil.py > > /usr/lib/python2.5/site-packages/mechanize/_html.py > > /usr/lib/python2.5/site-packages/mechanize/_lwpcookiejar.py > > /usr/lib/python2.5/site-packages/mechanize/_mechanize.py > > /usr/lib/python2.5/site-packages/mechanize/_mozillacookiejar.py > > /usr/lib/python2.5/site-packages/mechanize/_msiecookiejar.py > > /usr/lib/python2.5/site-packages/mechanize/_opener.py > > /usr/lib/python2.5/site-packages/mechanize/_pullparser.py > > /usr/lib/python2.5/site-packages/mechanize/_request.py > > /usr/lib/python2.5/site-packages/mechanize/_urllib2.py > > /usr/lib/python2.5/site-packages/mechanize/_useragent.py > > /usr/lib/python2.5/site-packages/mechanize/_util.py > > [???] > > zope3 ships private copies of a lot of Python packages, which is bad > enough on its own, but it additionally installs them system-wide in > /usr/lib/python2.5/site-packages. This is a huge problem because it not > only replaces symlinks placed there by python-central (potentially newer > library versions!), but also breaks later installations of affected > python-* packages, like python-tz or python-mechanize. For these > reasons I consider this bug release-critical. > > The best solution would be to create a zope3 (or, even better, > python-zope) package which only ships the ???zope??? module hierarchy and > depends on all the other stuff it needs; of course, some of the included > modules have yet to be packaged. If this is impossible because, say, > zope absolutely requires the modules as included, a private Python > module directory in /usr/share/zope might be an alternative. > > Cheers, > -- > Michael Schutte <mi...@uiae.at> > _______________________________________________ > pkg-zope-developers mailing list > pkg-zope-develop...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-zope-developers -- Brian Sutherland -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org