Your message dated Tue, 13 Apr 2010 09:33:15 -0400
with message-id <[email protected]>
and subject line Re: Bug#577312: pymvpa: FTBFS: invalid command name
'2.6/site-packages/'
has caused the Debian Bug report #577308,
regarding pymvpa: FTBFS: invalid command name '2.6/site-packages/'
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 [email protected]
immediately.)
--
577308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577308
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pymvpa
Version: 0.4.4-1
Severity: serious
Tags: squeeze sid
User: [email protected]
Usertags: qa-ftbfs-20100410 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-pymvpa_0.4.4-1-amd64-By1CMa/pymvpa-0.4.4/./build"
> --with-libsvm
> running build
> running config_cc
> unifing config_cc, config, build_clib, build_ext, build commands --compiler
> options
> running config_fc
> unifing config_fc, config, build_clib, build_ext, build commands --fcompiler
> options
> running build_src
> building extension "mvpa.clfs.libsmlrc.smlrc" sources
> building extension "mvpa.clfs.libsvmc._svmc" sources
> building data_files sources
> running build_py
> package init file 'mvpa/tests/badexternals/__init__.py' not found (or not a
> regular file)
> package init file 'mvpa/tests/badexternals/__init__.py' not found (or not a
> regular file)
> running build_ext
> customize UnixCCompiler
> customize UnixCCompiler using build_ext
> customize UnixCCompiler
> customize UnixCCompiler using build_ext
> running scons
> running build_scripts
> touch debian/python-module-stampdir/python-mvpa
> Adding cdbs dependencies to debian/python-mvpa.substvars
> dh_installdirs -ppython-mvpa
> cd . && python setup.py install
> --root=/build/user-pymvpa_0.4.4-1-amd64-By1CMa/pymvpa-0.4.4/debian/python-mvpa
> \
> --install-purelib=/usr/lib/python2.5 2.6/site-packages/
> --prefix=/usr --no-compile -O0 --with-libsvm
> invalid command name '2.6/site-packages/'
> make: *** [install/python-mvpa] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2010/04/10/pymvpa_0.4.4-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
| [email protected] http://www.lucas-nussbaum.net/ |
| jabber: [email protected] GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
On Mon, 12 Apr 2010, Jonas Smedegaard wrote:
> >for details -- there it fails to build with the newest available cdbs 0.4.77
> No, this is wrong: CDBS might have bugs, but those are (very very
> likely) not identical to bugs in packages _using_ CDBS.
> So generally do not reassign bugs to cdbs but instead file a new bug
> clarifying why you believe cdbs causes those other bugs, and tag
> your own bugs as blocked by the new cdbs bug.
> If you really really believe a bug should simply be reassigned, then
> at least retitle: cdbs does not FTBFS due to "invalid command name
> '2.6/site-packages/'"!
thanks -- I will follow this retitling recommendation in the
future to prevent blind bouncing of the bug reports.
> It seems you use cdbs-provided variable in constructions of your
> own, which fails due to changes in Python install routines.
nope -- fix to #577580 has fixed FTBFS issues, nothing to be done on my
side (nothing had failed in the actual builders), thus closing those
original bug reports with this email.
--
.-.
=------------------------------ /v\ ----------------------------=
Keep in touch // \\ (yoh@|www.)onerussian.com
Yaroslav Halchenko /( )\ ICQ#: 60653192
Linux User ^^-^^ [175555]
signature.asc
Description: Digital signature
--- End Message ---
