[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#683292: marked as done (unblock: nipy/0.2.0-1)

Your message dated Sat, 1 Dec 2012 11:54:47 +0100
with message-id <20121201105447.GC5634@radis.cristau.org>
and subject line Re: Bug#683292: unblock: nipy/0.2.0-1
has caused the Debian Bug report #683292,
regarding unblock: nipy/0.2.0-1
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 owner@bugs.debian.org
immediately.)


-- 
683292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683292
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package nipy

unblock nipy/0.2.0-1

Before the freeze point, 0.2.0~rc2+git27-g7b9b5a5-1 was uploaded in June
targetting wheezy, but it has not propagated to wheezy due to FTBFS on mips
[1].  By the time mips issues got resolved, upstream has put a lot of effort
into fixing examples and documentation -- there were only few core
functionality fixes and 0.2.0 was released in July.  At the moment nipy 0.2.0-1

- builds and passes an extensive unittests battery (> 4400 tests) across 
  all ports [2]
- (somewhat irrelevant for Debian proper) builds and passes unittests
  across previous releases of Debian (>= squeeze) and Ubuntu (>= 10.10)
  (for all supported python versions!) [3]

I am attaching a gzipped debdiff on .dsc from 0.2.0~rc2+git27-g7b9b5a5-1 --
there is a bulk of changes indeed BUT most of them are examples and
documentation fixes; all functionality changes/fixes were accompanied with
unittests and passed peer-review.  Neither of those changes should effect
python-nipy -- the only package (loosly) depending on nipy.

Altogether I have a strong believe that this release is stable to warrant its
inclusion in wheezy release so that Debian wheezy shines with the best recent
neuroimaging software.

Please let me know if there is any additional information I could provide to
advocate this unblocking request any further.

[1] https://buildd.debian.org/status/logs.php?pkg=nipy&arch=mips
[2] https://buildd.debian.org/status/package.php?p=nipy
[3] http://neuro.debian.net/pkgs/python-nipy.html#neurodebian

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Attachment: nipy_0.2.0~rc2+git27-g7b9b5a5-1--0.2.0-1-debdiff.txt.gz
Description: GNU Zip compressed data


--- End Message ---
--- Begin Message --- 
On Mon, Jul 30, 2012 at 11:22:04 -0400, Yaroslav Halchenko wrote:

> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock package nipy
> 
> unblock nipy/0.2.0-1
> 
Looks like this is too big and too late.  Closing, sorry.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: