On Mon, Dec 10, 2012 at 2:35 AM, Ben Finney <[email protected]> wrote:
> Now the build is failing differently:
>
> =====
> running install_scripts
> Traceback (most recent call last):
>   File "setup.py", line 115, in <module>
>     setup(**setup_args)
>   File "/usr/lib/python3.2/distutils/core.py", line 148, in setup
>     dist.run_commands()
>   File "/usr/lib/python3.2/distutils/dist.py", line 917, in run_commands
>     self.run_command(cmd)
>   File "/usr/lib/python3.2/distutils/dist.py", line 936, in run_command
>     cmd_obj.run()
>   File 
> "/tmp/buildd/python-coverage-3.4/distribute-0.6.13-py3.2.egg/setuptools/command/install.py",
>  line 53, in run
>   File "/usr/lib/python3.2/distutils/command/install.py", line 619, in run
>     self.run_command(cmd_name)
>   File "/usr/lib/python3.2/distutils/cmd.py", line 313, in run_command
>     self.distribution.run_command(command)
>   File "/usr/lib/python3.2/distutils/dist.py", line 936, in run_command
>     cmd_obj.run()
>   File 
> "/tmp/buildd/python-coverage-3.4/distribute-0.6.13-py3.2.egg/setuptools/command/install_scripts.py",
>  line 37, in run
>   File 
> "/tmp/buildd/python-coverage-3.4/distribute-0.6.13-py3.2.egg/setuptools/command/easy_install.py",
>  line 1736, in get_script_args
>   File 
> "/tmp/buildd/python-coverage-3.4/distribute-0.6.13-py3.2.egg/setuptools/command/easy_install.py",
>  line 1588, in get_script_header
> TypeError: can't use a bytes pattern on a string-like object
> make[1]: *** [install-python3.2] Error 1
> make[1]: Leaving directory `/tmp/buildd/python-coverage-3.4'
> make: *** [install] Error 2
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2

What is distribute-0.6.13-py3.2.egg? There is no such directory in
upstream tarball.

The package builds for me, but python3-coverage package is empty
because the .install file is missing. Also, dh_python2 and dh_python3
should be run *only* against python- and python3- packages,
respectively.

--
Dmitry Shachnev


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to