Hi Cedric, your package gaphor is affected by a RC bug (#365465) and for this reason it will be excluded from the etch if the bug won't be solved in time.
The actual package in testing/unstable conflicts on zope3 and python-zopeinterface because gaphor makes use of some of the libraries provided by zope3, but they are provided upstream and installed within the same path used by the zope3 package. This makes the package not usable on machines where there are other zope3-related packages. My proposed solution is to split those files into a gaphor-lib (or gaphor-zope) package, conflicting with zope3 and python-zopeinterface, and let gaphor depend on gaphor-lib | zope3. I'm writing this e-mail in order to have your opinion on such a change: as you could imagine, I am not comfortable to do it with a NMU. I'm willing to co-maintain the package if you think it would be the case, too. Thanks in advance, -- Fabio Tranchitella http://www.kobold.it Free Software Developer and Consultant http://www.tranchitella.it _____________________________________________________________________ 1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564
signature.asc
Description: Digital signature
