tags 575551 + patch thanks * Jakub Wilk <jw...@debian.org>, 2010-03-21, 11:43:
I'm not entirely sure what is happening here, but I have some clues. The most important part of diff between mips (good) and mipsel (failed) builds is:checking for SWSCALE_LIBS... -lswscale checking for python version... 2.6 checking for python platform... linux2 -checking for python script directory... ${prefix}/lib/python2.6/site-packages -checking for python extension module directory... ${exec_prefix}/lib/python2.6/site-packages +checking for python script directory... ${prefix}/lib/python2.6/dist-packages +checking for python extension module directory... ${exec_prefix}/lib/python2.6/dist-packages checking for headers required to compile python extensions... found checking for libpython2.6... found checking whether the compiler implements namespaces... yes(I don't known where does this difference come from. But, oh well, running aclocal and company at build time is always a risky business.)Normally it doesn't matter that much if you install files to pyhton2.6/site-packages or python2.6/dist-packages, as python-central will move the former one to the latter anyway.However, in your debian/rules you also install files directly into python2.6/site-packages, and python-central is confused if there are files in both directories.
I attached a revised patch. -- Jakub Wilk
diff -Nru libavg-0.8.0/debian/rules libavg-0.8.0/debian/rules --- libavg-0.8.0/debian/rules 2010-03-20 22:21:55.000000000 +0100 +++ libavg-0.8.0/debian/rules 2010-05-02 13:29:54.000000000 +0200 @@ -29,7 +29,7 @@ debian/stamp-install%: -make -C build$*/src check SUBDIRS="$(CHECK_DIRS)" make -C build$* install DESTDIR=$(DEB_DESTDIR) - dh_install debian/libavg.pth /usr/lib/python$*/site-packages/ + cp debian/libavg.pth debian/*/usr/lib/python$*/*-packages/ rmdir -p --ignore-fail-on-non-empty $(DEB_DESTDIR)/usr/share/avg mv $(DEB_DESTDIR)/usr/bin/avg_showfont.py \ $(DEB_DESTDIR)/usr/bin/avg_showfont
signature.asc
Description: Digital signature
