configure tries to pick up the highest version of python. all python scripts should be using the version found by configure. i.e. if configure picks up /usr/bin/python2.6 scripts like provision and net should not try to run '/usr/bin/env python' but rather '/usr/bin/env python2.6' as python is not always a link to the version configure picked up.
samba_dnsupdate is also bitten by this one
Well, I mark this as enhancement, since
1.) on standard installations with only one python installed you aren't affected
2.) only when you have more than one environments the problem appears. But you can always work-around by starting the script using the right python binary.
I will discuss this with Jelmer but don't really know yet if we provide a solution (since the "shebang" header of python scripts is static).
you would hit this one too, when you happen to update to a newer python version (well in that case you would be completely borked I suppose). but since the install creates $SAMBAHOME/lib/pythonX.Y/site-packages which depends on the python version it wouldn't hurt to sed the correct python binary into the scripts.
I think we've started doing this with the waf build. Can somebody verify?
Jelmer, considering your comment: has this been fixed?
Please don't assign me to random bugs.
(In reply to comment #5)
> Jelmer, considering your comment: has this been fixed?
I think it has been (see my last comment), but it would be great if somebody who is actually having this issue could verify that we do this in all situations.
This is fixed in current releases.