Hi, * Julien Cristau <[email protected]> [2013-07-30 10:38:51 +0200]:
> On Mon, Jul 29, 2013 at 22:00:07 +0000, Gergely Nagy wrote: > > > > I had to reject txzmq, because it Build-Depens on a pure virtual > > package, python-zope. Building succeeds in a chroot now, because there > > is only one provider: python-zope.interface, but would a second one > > appear, the build could not be guaranteed. > > > So, err. Since when is that a reason for reject? There's plenty of > packages with build-deps on a virtual package, which, as you say, is > just fine if that virtual package is guaranteed to only have one > provider at any given time. Is there a reason to believe that's not > true for python-zope? While I don't really have an opinion on the general "B-D on a virtual package" case, txZMQ really only ever imports stuff from zope.interface, so B-/Depending on the python-zope.interface package directly seems right. I'll sponsor an upload with the B-D/D change (and the copyright file change). Cheers, -- Nicolas Dandrimont BOFH excuse #136: Daemons loose in system.
signature.asc
Description: Digital signature
_______________________________________________ Python-modules-team mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
