Well, I raised this on #debian-devel again, and since I think
"python2.5 | python (>=2.5)"[1] is just a workaround[2], I was told to
forget about Debian Python policy's spirit ("make your package in a way
that you will not need additional upload [except binNMUs] once new
Python version will be added or removed from supported Python versions
list"[3]), *always* use python2.5 in shebang (at least before python2.5
will be default in Debian) and reassign sbuild's bug to policy (asking
to forbid alternate dependencies there).
Noah, since I don't want your package to suffer from this, please use
python2.5 (only! - without the stuff before the "|") in Build-Depends-Indep
and I will upload it.
[1] please note the order
[2] think what will happen once python2.6 will be default
[3] in this case, we will need additional upload once python2.5 will be
removed from the distribution.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
