[Python-modules-team] Bug#592714: Bug#592714: [FTBFS]: lib directory in python and in debian/rules does not match

[Alfonso Cepeda Caballos]

First of all, can you check that the package does not build in debian?
In Ubuntu it doesn't:
http://launchpadlibrarian.net/50119957/buildlog_ubuntu-maverick-i386.creoleparser_0.7.2-3_FAILEDTOBUILD.txt.gz

and I think that provided that testing uses the same python package,
it won't build, but I can be wrong, and right now I cannot download a
debian pbuilder image to test. I mean, maybe this is just an ubuntu
issue, but I think it isn't.


About the patch, I think there is no previously generated files, and
as far as it is arch:all, the lib should be build/lib and not
build/lib-$ARCH.

Anyway the current build outputs:

creating build
creating build/lib.linux-i686-2.6
creating build/lib.linux-i686-2.6/creoleparser
copying creoleparser/core.py -> build/lib.linux-i686-2.6/creoleparser
copying creoleparser/dialects.py -> build/lib.linux-i686-2.6/creoleparser
copying creoleparser/__init__.py -> build/lib.linux-i686-2.6/creoleparser
copying creoleparser/elements.py -> build/lib.linux-i686-2.6/creoleparser

as you can see, python setup function does not create build/lib, so
there should not be any overwriting.

If you think it is better to maintain the build/lib.$ARCH structure,
then, in debian/rules:

PYTHONPATH=$(CURDIR)/build/lib $$py
$(CURDIR)/build/lib/creoleparser/__init__.py; \

should be changed to $(CURDIR)/build/lib.$PLAT where $PLAT is the
output of  distutils.util.get_platform(), but I'd rather the
--build-lib=build/lib solution.

I have tested that package build with the patch is equal to
python-creoleparser_0.7.2-3_all.deb

Anyway I do not use python very much, so I can be wrong.

On 16 August 2010 16:21, Piotr Ożarowski <piotr at debian.org> wrote:
> I don't think it's the right fix. You will overwrite previously
> generated files this way (it's arch:all package so if .py files are
> equal, it will not break the module).

-- 
Proudly working on an Ubuntu lucid 10.04