----- Original Message -----
> On 07/03/13 08:28, Nathan Scott wrote:
> >
> > nathans@verge:/source/git/pcp$ grep Python-Version debian/control
> > X-Python-Version: >= 2.6
> >
> > So, with my change from yesterday I was expecting you'd get an
> > unsatisfied build dependency (thanks to the "python-all" req),
> > and once you install "python2.6" alongside your "python2.7" it
> > would magically start to work.
> >
>
> I changed pyversion -vr to pyversion -i which seems more correct in
> debian/rules ... do you agree?
>
I thought the same when I did this packaging, but actually its not.
See "man dh_python2" - the list is not supposed to be what is installed
but rather the list you intend to build support for in the package -
the build-requires is meant to ensure the appropriate supporting python
versions are installed (before pyversion is run during the build).
> == dpkg-buildpackage: binary-arch
> warning: install_lib: 'build/lib.linux-x86_64-2.6' does not exist --
> no
> Python modules to install
> readelf: Error:
> debian/python-pcp/usr/lib/python2.6/dist-packages/pmapi.so: Failed to
> read file's magic number
>
Is this just a warning or does it cause the build to fail? I also
see that initial "does not exist" warning, IIRC its known/expected
and is not something the Debian python people intend to go back and
fix (AIUI, from googling).
Just did a quick check build - I think you are close - check to see
if packages exist? In my logs I see...
running install
running install_lib
warning: install_lib: 'build/lib.linux-i686-2.6' does not exist -- no Python
modules to install
running install_egg_info
...
dh_python2 --package python-pcp
readelf: Error: debian/python-pcp/usr/lib/python2.6/dist-packages/pmapi.so:
Failed to read file's magic number
...
So, scary, but expected - you might actually have packages now?
cheers.
--
Nathan
|