I'd suggest patch the zope3 source package to not create python- zopeinterface binary package. Instead just throw the zope.interface code away when building zope3.
Then make a new source package, based around the zope.interface tarball that provides python-zopeinterface in some way. Then the old zope3 monstrosity will depend on python-zopeinterface (as it now does). Finally, the fun part is to try make sure you don't break the zope3 tarball when there is version skew between zope.interface and zope3. I'd suggest trying to integrate the zope3 tests into the autopkgtest framerwork. (I'm not sure if the 3.3 tests run properly on a read-only directory, which is a problem you will encounter, but I did get some patches in 3.4) -- reports its version number in .egg-info as 0.0.0 https://bugs.launchpad.net/bugs/185418 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
