On Mon, Mar 23, 2009 at 01:15:04AM -0000, Andrew Straw wrote:
> Gaël, my patch is more of a band-aid -- since we're past the feature
> freeze for Jaunty, I don't think any more can easily be done.
> For upstream, I think the real problem is that the distutils build
> command gets called twice by the Debian build system. First, it does
> "python setup.py build" and the tvtk zip file is built. Then, during a
> second run, "python setup.py install" (distutils install command calls
> build again), the zip file is there and the bug is triggered. Thus, my
> patch simply lets build start again during the install step, but this is
> actually curing only a symptom, not the cause.
> That said, a band-aid in upstream is better than a complete failure!
Totally agreed with you, with both points. I asked Prabhu for his opinion
on the upstream modification.
On Mon, Mar 23, 2009 at 01:15:04AM -0000, Andrew Straw wrote:
> Gaël, my patch is more of a band-aid -- since we're past the feature
> freeze for Jaunty, I don't think any more can easily be done.
> For upstream, I think the real problem is that the distutils build
> command gets called twice by the Debian build system. First, it does
> "python setup.py build" and the tvtk zip file is built. Then, during a
> second run, "python setup.py install" (distutils install command calls
> build again), the zip file is there and the bug is triggered. Thus, my
> patch simply lets build start again during the install step, but this is
> actually curing only a symptom, not the cause.
> That said, a band-aid in upstream is better than a complete failure!
Totally agreed with you, with both points. I asked Prabhu for his opinion
on the upstream modification.
Gaël