ok -- just last call... what about Build-Conflicts: python-epydoc (= 3.0.1-3) ?
Reasons: > Honestly, I don't see why dropping: you need that version, and that > version only, to build it correctly. Consider an outdated environment nope -- would work just fine in lenny with epydoc (3.0.1-1); and we will build a backport probably. > Unlikely such an env exists, but versioned depends are here for > specifying a precise version needed, or from one onward. exactly, and in this situation there is no precise versioning -- there is a buggy version of epydoc (3.0.1-3) in conjunction with fresh docutils. I see no perfect resolution (which would be Build-Conflicts on versions of epydoc <= 3.0.1-4 whenever docutils are >= 0.6), > From all the version released after lenny, you need that one to be > usable with python-docutils 0.6, so I suggest to leave it as it is. We are somewhat eager to backport things (see http://neuro.debian.net/) and still have lenny used quite a lot, and that is the reason why I am trying to avoid this boost ;) -- .-. =------------------------------ /v\ ----------------------------= Keep in touch // \\ (yoh@|www.)onerussian.com Yaroslav Halchenko /( )\ ICQ#: 60653192 Linux User ^^-^^ [175555] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
