Your message dated Sun, 03 Nov 2013 19:32:36 +0100
with message-id <1476084.J2rt649nJA@sephirot>
and subject line Builds ok
has caused the Debian Bug report #725567,
regarding python-cliff: FTBFS: pkg_resources.VersionConflict: (pyparsing 2.0.1
(/usr/lib/python2.7/dist-packages), Requirement.parse('pyparsing==1.5.7'))
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
725567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cliff
Version: 1.4-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20131006 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory `/«PKGBUILDDIR»'
> set -e -x; \
> PYTHONPATH=/«PKGBUILDDIR»/build/lib.* python setup.py nosetests
> + PYTHONPATH=/«PKGBUILDDIR»/build/lib.* python setup.py nosetests
> running nosetests
> running egg_info
> writing requirements to cliff.egg-info/requires.txt
> writing cliff.egg-info/PKG-INFO
> writing namespace_packages to cliff.egg-info/namespace_packages.txt
> writing top-level names to cliff.egg-info/top_level.txt
> writing dependency_links to cliff.egg-info/dependency_links.txt
> writing entry points to cliff.egg-info/entry_points.txt
> reading manifest file 'cliff.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.html' under directory 'docs'
> warning: no files found matching '*.css' under directory 'docs'
> warning: no files found matching '*.js' under directory 'docs'
> warning: no files found matching '*.png' under directory 'docs'
> writing manifest file 'cliff.egg-info/SOURCES.txt'
> running build_ext
> Traceback (most recent call last):
> File "setup.py", line 188, in <module>
> zip_safe=False,
> File "/usr/lib/python2.7/distutils/core.py", line 152, in setup
> dist.run_commands()
> File "/usr/lib/python2.7/distutils/dist.py", line 953, in run_commands
> self.run_command(cmd)
> File "/usr/lib/python2.7/distutils/dist.py", line 972, in run_command
> cmd_obj.run()
> File "/usr/lib/python2.7/dist-packages/nose/commands.py", line 140, in run
> self.distribution.install_requires)
> File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 245, in
> fetch_build_eggs
> parse_requirements(requires), installer=self.fetch_build_egg
> File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 600, in
> resolve
> raise VersionConflict(dist,req) # XXX put more info here
> pkg_resources.VersionConflict: (pyparsing 2.0.1
> (/usr/lib/python2.7/dist-packages), Requirement.parse('pyparsing==1.5.7'))
> make[1]: *** [override_dh_auto_test] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/10/06/python-cliff_1.4-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 31373
--- End Message ---
