the package you mentioned is orphaned and marked out-of-date. i think you can simply adopt and update it. change the PYTHON variable in Makefile to python2 and several shebang lines in .py files may solve the breakage. of course, you need to change the dependency from python to python2.
Date: Fri, 12 Nov 2010 12:00:26 -0600 From: "David C. Rankin" <drankinatty@suddenlinkmail.com> Subject: Re: [arch-general] Could python2 be breaking genpkgmetadata.py? To: General Discussion about Arch Linux <arch-general@archlinux.org> Message-ID: <4CDD80BA.7080004@suddenlinkmail.com> Content-Type: text/plain; charset=ISO-8859-9
On 11/12/2010 11:44 AM, David C. Rankin wrote:
But on how many packages? Just the ones that are breaking or is there some set of base packages I should backup and the do a 'perl -p -i -e s/bin\/python/bin\/python2/' on?
Err.. It doesn't seem to be that simple. After changed the executable line, now the scripts don't find the modules:
Traceback (most recent call last): File "/usr/share/createrepo/genpkgmetadata.py", line 29, in <module> import createrepo ImportError: No module named createrepo
Is there a way to teach the python2 scripts about the modules it used to know?
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
------------------------------