[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#294506: zope-textindexng2: Package builds incorrectly on amd64: Python site-packages files do not install

On Wed, 9 Feb 2005, Per Bojsen wrote:

Package: zope-textindexng2
Version: 1:2.0.8-4
Severity: normal

When this package is built on the amd64 architecture, the files that
are to go in the /usr/lib/python2.2/site-packages/zope-textindexng2
directory fail to be installed.  This is not obvious when the
package is being built, but leads to numerous test errors during
installation of the package [1].  I tracked this down to the
debian/install file.  The following patch allowed me to build
the package correctly on amd64 and it now installs with all tests

--- debian/install.orig 2005-02-09 22:25:08.575769172 -0500
+++ debian/install      2005-02-09 22:10:34.499301101 -0500
@@ -1,2 +1,3 @@
build/lib.linux-i686-2.2/*    usr/lib/python2.2/site-packages/zope-textindexng2
+build/lib.linux-x86_64-2.2/* usr/lib/python2.2/site-packages/zope-textindexng2
debian/zope-textindexng2.pth  usr/lib/python2.2/site-packages/

I just added the line for the x86_64 architecture.  This works
because dh_install ignores patterns that do not match.  However,
if someone is building both the i386 and amd64 version of the
package in the same build directory and forgets to do a clean
between each build, then they could end up with a bad package
where the amd64 files overwrite the i386 ones.  The alternative
is to have one install file for each architecture.  Is this
even possible?  How is this situation handled in other packages?
... (see more details on the bug page)

I would like to foreward this problem to this list, because I have no idea
how to handle this bug right.  I guess the patch would solve the problem but
as the bug reporter mentioned it might lead to problems if you try to build
on different machines. I think "forgetting" to clean is not really in issue
if you use the default package building tools, but anyway I would rather fix
this in the build process and do report the problem upstream.

IMHO, the problem is caused by the fact that the package installs for instance

$ file /usr/lib/python2.2/site-packages/zope-textindexng2/Levenshtein.so /usr/lib/python2.2/site-packages/zope-textindexng2/Levenshtein.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped

into /usr/lib/python2.2/site-packages where normally python files (and there
precompiled flavours) belong.  Any hint, how to circumvent this?

Kind regards



Reply to: