Your message dated Wed, 20 Jun 2012 12:48:45 +0000
with message-id <e1shkkz-000191...@franck.debian.org>
and subject line Bug#671978: fixed in nitime 0.4-1
has caused the Debian Bug report #671978,
regarding nitime: FTBFS: ImportError: cannot import name factorial
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.)


-- 
671978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nitime
Version: 0.3.1-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 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[2]: Entering directory `/«PKGBUILDDIR»/doc'
> ../tools/make_examples.py
> Traceback (most recent call last):
>   File "../tools/make_examples.py", line 94, in <module>
>     execfile(script)
>   File "seed_analysis.py", line 47, in <module>
>     import nitime.fmri.io as io
>   File 
> "/«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/nitime/fmri/__init__.py",
>  line 18, in <module>
>     import hrf
>   File 
> "/«PKGBUILDDIR»/debian/tmp/usr/lib/python2.7/dist-packages/nitime/fmri/hrf.py",
>  line 2, in <module>
>     from scipy import factorial
> ImportError: cannot import name factorial
> make[2]: *** [rstexamples] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2012/05/08/nitime_0.3.1-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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.



--- End Message ---
--- Begin Message ---
Source: nitime
Source-Version: 0.4-1

We believe that the bug you reported is fixed in the latest version of
nitime, which is due to be installed in the Debian FTP archive:

nitime_0.4-1.debian.tar.gz
  to main/n/nitime/nitime_0.4-1.debian.tar.gz
nitime_0.4-1.dsc
  to main/n/nitime/nitime_0.4-1.dsc
nitime_0.4.orig.tar.gz
  to main/n/nitime/nitime_0.4.orig.tar.gz
python-nitime-doc_0.4-1_all.deb
  to main/n/nitime/python-nitime-doc_0.4-1_all.deb
python-nitime_0.4-1_all.deb
  to main/n/nitime/python-nitime_0.4-1_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 671...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yaroslav Halchenko <deb...@onerussian.com> (supplier of updated nitime package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 06 Jun 2012 16:04:24 -0400
Source: nitime
Binary: python-nitime python-nitime-doc
Architecture: source all
Version: 0.4-1
Distribution: unstable
Urgency: low
Maintainer: NeuroDebian Team <t...@neuro.debian.net>
Changed-By: Yaroslav Halchenko <deb...@onerussian.com>
Description: 
 python-nitime - timeseries analysis for neuroscience data (nitime)
 python-nitime-doc - timeseries analysis for neuroscience data (nitime) -- 
documentati
Closes: 614220 671978
Changes: 
 nitime (0.4-1) unstable; urgency=low
 .
   * New upstream release
     - fix commit for lazyimports pickling
     - compatible with scipy 0.10 API breakage (Closes: #671978)
   * debian/control:
     - added XS-Python-Version >= 2.6 (for squeeze backports)
     - reindented/untabified *Depends
     - boosted policy compliance to 3.9.3 (no further changes)
     - upcased Depends in ${python:Depends}.  Hopefully finally it
       (Closes: #614220)
   * debian/copyright:
     - updated years and fixed for DEP5 compliance
   * debian/rules
     - disable test_lazy_reload test (known to fail whenever ran by nosetest)
     - export HOME=$(CURDIR)/build just to avoid possible FTBFs
   * debian/watch
     - adjusted to fetch from tags
Checksums-Sha1: 
 3a3085ec97689692d34c452331863e077d1a2555 1463 nitime_0.4-1.dsc
 ef8d9a59947bd252a7df4c1632c49eaaa6a9ef59 6192096 nitime_0.4.orig.tar.gz
 7b86892ef4a9b94dbc7a520ce5b26cb320754884 4711 nitime_0.4-1.debian.tar.gz
 b4afda2d25b54e26cbee96be5c3802911c35d974 3908050 python-nitime_0.4-1_all.deb
 c9a294bf3c6c1fe1474a1c581be6f60089409a08 5277116 
python-nitime-doc_0.4-1_all.deb
Checksums-Sha256: 
 beca5eaefd9e8e4f6a543369b630ff699c5fa40ec428146fe90a4cbdb25448c5 1463 
nitime_0.4-1.dsc
 c54af12a335e47c8916647da940b3377f18f415f3363d60899cd6f3c03db1809 6192096 
nitime_0.4.orig.tar.gz
 9ff3e431a1b5363f195a4733a0e441dbb8829daa6d170f1b011e71f4dfd7a2e8 4711 
nitime_0.4-1.debian.tar.gz
 b21040ca772f87681fb592b4922e96337d3599a4d8d575612dd088f043c0ac38 3908050 
python-nitime_0.4-1_all.deb
 121375100fe8d5cde24aa71359955eccc9a671d0f1796178d19eef1ad8973a29 5277116 
python-nitime-doc_0.4-1_all.deb
Files: 
 f5ff70164ee465001640dacf5f34057d 1463 python extra nitime_0.4-1.dsc
 4ffcb634356607357eb5b24cb5f316c1 6192096 python extra nitime_0.4.orig.tar.gz
 6b9163857feab5e1a5fc6477976c9cc3 4711 python extra nitime_0.4-1.debian.tar.gz
 32f0cc8ba036de9e25ae2804b783be40 3908050 python extra 
python-nitime_0.4-1_all.deb
 56ec903e9bbebe5703f7b13ba29fbba6 5277116 doc extra 
python-nitime-doc_0.4-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk/hwr0ACgkQjRFFY3XAJMhA5QCgvJotBjF6E3Ec9iq0XwHqQbgg
RRAAoKm3g9rnzF3kctzWR1hFAzdsYkBe
=TAIH
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to