On 07/03/13 07:00, Ken McDonell wrote:
OK this is more broken than I thought ... pyversions -vr (no -n) returns
as follows:
LinuxMint _sometimes_
2.6 2.7
but most of time
pyversions: error parsing Python-Version attribute
On all the other Debian and Ubuntu systems the answer is
pyversions: error parsing Python-Version attribute
_if_ it returns "2.6 2.7" the build breaks, otherwise the for loop in
debian/rules is not run (which also seems bad).
This is not doing anything to make we want to learn python!
OK, the output from pyversions -vr depends on where you are in the file
system!!
in $HOME - pyversions: error parsing Python-Version attribute
in $HOME/src - pyversions: error parsing Python-Version attribute
in $HOME/src/pcp - 2.6 2.7 on LinuxMint, 2.7 on Ubuntu
in $HOME/src/pcp/src - pyversions: error parsing Python-Version attribute
believe it or not, pyversions appears to be reading _our_ debian/control
file not one belonging to the python installation
and on my LinuxMint I have /usr/lib/python2.6 and /usr/lib/python2.7 but
on Ubuntu only /usr/lib/python2.7. In both distros, only python2.7 is
installed (the LinuxMint has a bunch of pkgs using /usr/lib/python2.6,
there are none on the Ubuntu systems)
|