[Debian-med-packaging] Bug#586830: Bug#586830: Bug#586830: marked as done (hardcodes Python 2.5)
steffen_moeller at gmx.de
Wed Jun 30 08:14:23 UTC 2010
On 06/30/2010 09:05 AM, Piotr Ożarowski wrote:
> [Charles Plessy, 2010-06-30]
>> What makes you think that autodocktools works with python 2.6 if upstream
>> hardcoded it for 2.5. Have you tested the package before uploading?
>> I understand that you may be disapointed that we have not answered your bug
>> report, but please consider that people may be busy, and that the absence of
>> answer does not mean that we were not thinking about the question (can autodock
>> run with python >= 2.5?).
>> I am still puzzled why a NMU with no consultation with the maintainer was
>> chosen instead of simply removing the package from Testing.
> yeah, I did some code reviewing and didn't spot anything that doesn't
> work with 2.6. Could you point me to what is not working so that I can
> fix it since you're busy?
You could do me a great favour if you go for the real thing,
i.e. get the packages from upstream CVS of which they know it is
compatible with 2.6. It is also my experience from the 2.5 transition
that there won't be too many packages affected. But it is not
on us to decide that, really, so I think.
If you are actively using the autodocktools then I am happy
for your contribution and expect you to deal with any problems.
If not, then I am too busy to be offended.
More information about the Debian-med-packaging