Do you mean that they would not force upgrade of python-docutils? or
would crash? or ...?
I've built the updated package with suggested build-depends under
pbuilder no problem (but it had uptodate sid chroot so had to do
nothing)
On Wed, 13 Jan 2010, Jakub Wilk wrote:
> >python-docutils (<< 0.6
* Jakub Wilk , 2010-01-13, 01:10:
If you really want to protect from this bug reoccurring, please add
additional build-dependency on:
python-docutils (<< 0.6) | python-docutils (>= 0.6-3~)
Uhm, sorry, while the above may sound promising, IIRC buildds won't swallow
that. :/
--
Jakub Wilk
* Sandro Tosi , 2010-01-13, 00:56:
ok -- just last call... what about
Build-Conflicts: python-epydoc (= 3.0.1-3)
?
that *might* work, and since you do care about backporting, I'm fine
with that change :)
Not really, previous versions of python-epydoc are likely affected by
changes in docuti
tags 560606 + patch
thanks
Dear maintainer,
I've prepared an NMU for pymvpa (versioned as 0.4.3-1.1) and
uploaded it to DELAYED/2 (I'll upload tomorrow morning, so 2
days from that time).
Regards.
diff -u pymvpa-0.4.3/debian/control pymvpa-0.4.3/debian/control
--- pymvpa-0.4.3/debian/control
+++
4 matches
Mail list logo