On jeu, 2005-06-09 at 15:58 +0200, Josselin Mouette wrote: > Le jeudi 09 juin 2005 à 08:41 -0400, Jeff Bailey a écrit : > > Package: debhelper > > Version: 4.2.36 > > Tags: patch > > > > dh_python is broken when using the -V argument. The version number > > isn't bumped from the system version to the specified version, which > > causes the wrong site-package directories to be scanned. > > You seem to misunderstand the purpose of the -V argument. All > site-packages directories are always scanned. The -V argument is here > when you are shipping private modules in /usr/lib/somepackage, to tell > dh_python that these modules are meant for a specific python version. > > You say you have a test case that fails, could you please explain what > is it doing? Something else must be wrong.
The case is the bzr package in experimental. It calls the distutils bits with: python2.4 setup.py config python2.4 setup.py build (etc...) Which causes the bzrlib library to be installed into: /usr/lib/python2.4/site-packages/bzrlib/ Right now, Line 76 of dh_python determines the $python_version based on the $python variable. Line 99 and 100 override $python to be python2.4, but don't update the python_version variable. Where this becomes a problem is on line 142, where the site-packages directory is scanned based on usr/lib/python $python_version/site-packages It doesn't see the files in the library, and so doesn't cause the prerm and postinst debhelper stubs to get generated. Your explanation of the -V variable doesn't match what that man page says, which might be the source of my confusion. In this case, the .py files are intended to be used with 2.4, and are not being shipped in /usr/lib/site-python so the usage of -V seems to be right. Corrections appreciated. =) Tks, Jeff Bailey Tks, Jeff Bailey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
