Bug#552912: python-mechanize: FTBFS: mv: cannot stat `mechanize-0.1.11-py2.5.egg-info': No such file or directory

Lucas Nussbaum lucas at lucas-nussbaum.net
Wed Oct 28 10:51:50 UTC 2009


Source: python-mechanize
Version: 0.1.11-1
Severity: serious
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20091028 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/build/user-python-mechanize_0.1.11-1-amd64-WBolya/python-mechanize-0.1.11'
> python2.5 setup.py install --no-compile --install-layout=deb --single-version-externally-managed --root=debian/python-mechanize
> running install
> running build
> running build_py
> running install_lib
> creating debian/python-mechanize/usr
> creating debian/python-mechanize/usr/lib
> creating debian/python-mechanize/usr/lib/python2.5
> creating debian/python-mechanize/usr/lib/python2.5/site-packages
> creating debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/__init__.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_auth.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_beautifulsoup.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_clientcookie.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_debug.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_file.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_firefox3cookiejar.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_gzip.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_headersutil.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_http.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_lwpcookiejar.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_mechanize.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_mozillacookiejar.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_msiecookiejar.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_opener.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_pullparser.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_request.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_response.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_rfc3986.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_seek.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_sockettimeout.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_testcase.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_upgrade.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_urllib2.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_useragent.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_util.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> copying build/lib/mechanize/_html.py -> debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize
> running install_egg_info
> running egg_info
> writing requirements to mechanize.egg-info/requires.txt
> writing mechanize.egg-info/PKG-INFO
> writing top-level names to mechanize.egg-info/top_level.txt
> writing dependency_links to mechanize.egg-info/dependency_links.txt
> reading manifest file 'mechanize.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'docs-in-progress'
> writing manifest file 'mechanize.egg-info/SOURCES.txt'
> Copying mechanize.egg-info to debian/python-mechanize/usr/lib/python2.5/site-packages/mechanize-0.1.11.egg-info
> running install_scripts
> # Remove python and module version from .egg-info
> echo python:Provides=python2.4-mechanize python2.5-mechanize|sed 's/ /, /g' >> debian/python-mechanize.substvars
> (cd debian/python-mechanize/usr/lib/python2.5/*-packages/; \
> 		mv mechanize-0.1.11-py2.5.egg-info mechanize.egg-info)
> mv: cannot stat `mechanize-0.1.11-py2.5.egg-info': No such file or directory
> make[1]: *** [install-python2.5] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2009/10/28/python-mechanize_0.1.11-1_lsid64.buildlog

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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| lucas at lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr             GPG: 1024D/023B3F4F |





More information about the pkg-zope-developers mailing list