Hello, > In the meanwhile, adding a conflicts between python-zodb and zope3 is the > quickest way to solve the issue. For lenny, we'll modularize the whole zope > package as upstream is planning.
So, who is adding this conflict? It looks like it's easier to add the conflict in python-zodb, which has matching versions in etch and sid right now (zope3 has a new upstream version in unstable that won't be considered for etch). Should this bug, or at least the RC aspect of it, be reassigned to python-zodb? Fabio, you seem to be the sole uploader of python-zodb; so I guess if you think the conflict is the right solution for etch, it's ok for someone to NMU this change as well if you don't have time for it? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
