On Thu, 26 Feb 2009, Josselin Mouette wrote: > Package: python-twitter > Version: 0.5-2 > > Hi, > > The python-twitter rules file contains the following: > > for python in $(PYVERS); do \ > $$python setup.py install --root=$(d);\ > done > … > dh_pysupport > sed -i -e '1,2d' > $(CURDIR)/$(d)/usr/share/python-support/python-twitter/twitter.py > > With the upcoming version of python-support (currently in experimental), > such statements will make the package FTBFS, since the files are now > moved to a different directory (/usr/share/pyshared). > > I suggest to do these things before the dh_pysupport call, and from the > standard installation directory: > > sed -i -e '1,2d' $(CURDIR)/$(d)/lib/python*/site-packages/twitter.py > dh_pysupport > > I’d add two side notes to that: > * There is no reason to build an architecture-independent package > for all Python versions. You can build it for only the current > one, python-support will byte-compile the modules for all the > supported ones. > * Such things could be done in a patch instead of the build > process, but I guess that’s a matter of taste. > > As a general rule, please do not rely on the internals of python-support > in the packaging; this will avoid such issues in the future (although > hopefully there won’t be a need to change the paths any further). > > Thanks, > -- > .''`. Debian 5.0 "Lenny" has been released! > : :' : > `. `' Last night, Darth Vader came down from planet Vulcan and told > `- me that if you don't install Lenny, he'd melt your brain.
From: Mauro Lizaur <[email protected]> To: Josselin Mouette <[email protected]>, [email protected] Cc: Bcc: Subject: Re: Bug#517216: python-twitter: FTBFS with python-support in experimental Reply-To: In-Reply-To: <1235653179.5228.31.ca...@shizuru> X-GPG-Key: http://lusers.com.ar/mliz.asc On Thu, 26 Feb 2009, Josselin Mouette wrote: > With the upcoming version of python-support (currently in experimental), > such statements will make the package FTBFS, since the files are now > moved to a different directory (/usr/share/pyshared). > > I suggest to do these things before the dh_pysupport call, and from the > standard installation directory: > > sed -i -e '1,2d' $(CURDIR)/$(d)/lib/python*/site-packages/twitter.py > dh_pysupport After following the thread [0] on d-devel, I knew this day would come :-) > > I’d add two side notes to that: > * There is no reason to build an architecture-independent package > for all Python versions. You can build it for only the current > one, python-support will byte-compile the modules for all the > supported ones. So you mean that instad of doing: for python in $(PYVERS); do $$python setup.py [....] done i could simply do something like: python setup.py [....] done right? > > As a general rule, please do not rely on the internals of python-support > in the packaging; this will avoid such issues in the future (although > hopefully there won’t be a need to change the paths any further). > Ok, i'll keep that in mind. [0] http://lists.debian.org/debian-devel/2009/02/msg00431.html Regards, Mauro -- JID: [email protected] | http://lusers.com.ar/ 2B82 A38D 1BA5 847A A74D 6C34 6AB7 9ED6 C8FD F9C1 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
