Your message dated Thu, 8 Oct 2009 15:54:55 +0200
with message-id <20091008135455.gp32...@piotro.eu>
and subject line fixed in cdbs 0.4.61+nmu2
has caused the Debian Bug report #549793,
regarding pycha: FTBFS: ImportError: No module named pycha.bar
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.)
--
549793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pycha
Version: 0.5.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091005 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> /usr/bin/fakeroot debian/rules binary
> pyversions: missing XS-Python-Version in control file, fall back to
> debian/pyversions
> test -x debian/rules
> dh_testroot
> dh_clean -k
> dh_installdirs -A
> mkdir -p "."
> mkdir -p debian/python-module-stampdir
> cd . && python setup.py build
> --build-base="/build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/./build"
> running build
> running build_py
> touch debian/python-module-stampdir/python-pycha
> dh_installdirs -ppython-pycha
> pyversions: missing XS-Python-Version in control file, fall back to
> debian/pyversions
> cd . && python setup.py install
> --root=/build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/
> \
> --install-lib=/usr/lib/python2.4/site-packages/ --prefix=/usr
> --no-compile -O0
> running install
> running build
> running build_py
> running install_lib
> creating
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr
> creating
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib
> creating
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4
> creating
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages
> creating
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/chavier
> copying build/lib/chavier/dialogs.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/chavier
> copying build/lib/chavier/__init__.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/chavier
> copying build/lib/chavier/app.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/chavier
> copying build/lib/chavier/gui.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/chavier
> creating
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/pycha
> copying build/lib/pycha/bar.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/pycha
> copying build/lib/pycha/color.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/pycha
> copying build/lib/pycha/chart.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/pycha
> copying build/lib/pycha/__init__.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/pycha
> copying build/lib/pycha/scatter.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/pycha
> copying build/lib/pycha/pie.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/pycha
> copying build/lib/pycha/stackedbar.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/pycha
> copying build/lib/pycha/line.py ->
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/pycha
> running install_egg_info
> running egg_info
> writing pycha.egg-info/PKG-INFO
> writing top-level names to pycha.egg-info/top_level.txt
> writing dependency_links to pycha.egg-info/dependency_links.txt
> writing entry points to pycha.egg-info/entry_points.txt
> writing manifest file 'pycha.egg-info/SOURCES.txt'
> reading manifest file 'pycha.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> writing manifest file 'pycha.egg-info/SOURCES.txt'
> Copying pycha.egg-info to
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/lib/python2.4/site-packages/pycha-0.5.2-py2.5.egg-info
> running install_scripts
> Installing chavier script to
> /build/user-pycha_0.5.2-1-amd64-cpbPAP/pycha-0.5.2/debian/python-pycha/usr/bin
> python \
> debian/runtests.py debian/python-pycha
> Traceback (most recent call last):
> File "debian/runtests.py", line 15, in <module>
> execfile("tests/runner.py")
> File "tests/runner.py", line 20, in <module>
> import bar
> File "tests/bar.py", line 22, in <module>
> import pycha.bar
> ImportError: No module named pycha.bar
> make: *** [install/python-pycha] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2009/10/05/pycha_0.5.2-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
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
this bug was introduced in cdbs 0.4.61+nmu1 and fixed in 0.4.61+nmu2
sorry again
--- End Message ---
