Re: Bug#221523: Causes build failures
> > The configure script is checking for 'python' script. > > > > What was the original reason for the 'recommends' instead of > > 'depends'? It's not really clear to me. > > some people wanted to be able to keep the default python version at > version 2.2, but install packages from unstable, when the default > versions were different in testing and unstable. I do doubt such special needs should be forced upon all of us. regards, junichi
Re: Bug#221523: Causes build failures
Junichi Uekawa writes: > > well, I think this is bug in these packages. OTOH, if there are too > > many of these, it might be better to change it back. I did never see > > much sense in keeping pythonX.Y without keeping python. > > The configure script is checking for 'python' script. > > What was the original reason for the 'recommends' instead of > 'depends'? It's not really clear to me. some people wanted to be able to keep the default python version at version 2.2, but install packages from unstable, when the default versions were different in testing and unstable. > The policy recommends using pythonx.x-dev for build-depends, > and that implies one must call python via python2.3 etc. ? > > I'm not sure if I'm really comfortable with having to do that. yes, that the consequence. Well, I don't like it either very much. Maybe I'll change that back, unless nobody complains. Matthias
Re: Bug#221523: Causes build failures
> > python2.3 (2.3.2-3) unstable; urgency=low > > > > * Downgrade the dependency of python2.3 on python (>= 2.3) to > > a recommendation. > > > > this seems to have caused buildds to fail because 'python' does not > > exist when building packages build-depending on python2.3-dev > > > > For example: > > > > http://buildd.debian.org/fetch.php?&pkg=ecasound2.2&ver=2.3.0-4&arch=hppa&stamp=1069186627&file=log&as=raw > > well, I think this is bug in these packages. OTOH, if there are too > many of these, it might be better to change it back. I did never see > much sense in keeping pythonX.Y without keeping python. The configure script is checking for 'python' script. What was the original reason for the 'recommends' instead of 'depends'? It's not really clear to me. The policy recommends using pythonx.x-dev for build-depends, and that implies one must call python via python2.3 etc. ? I'm not sure if I'm really comfortable with having to do that. regards, junichi
