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

Bug#728797: ITP: python-mne -- Python modules for MEG and EEG data analysis



Hi Alexandre,

On Wed, Nov 06, 2013 at 05:26:13PM +0100, Alexandre Gramfort wrote:
> > Looks good from quick view without doing an actual build.  I have
> > attached a fix for the debian/watch file - the file in your repository
> > does not report anything when trying `uscan --verbose --report`.
> 
> fixed in debian branch

:-)
 
> > In any case it has several advantages to at least maintain a clone in
> > one of our repositories at git.debian.org because we have some tools
> > browsing the repositories and doing some general analysis over the
> > VCS status.  It would be good if we could do this also for mne-python
> > but the NeuroDebian people might have the last word in case they agree
> > that they take over the package.  In any case it would be really
> > interesting to describe the workflow they are using in some kind of
> > policy document.  In case this sounds convincing we could take over
> > this into Debian Med policy[1].
> 
> having python-mne in both would be great. Yaroslav has helped me
> up to now to meet neurodebian's requirements. I'd appreciate any
> help (pull request) to meet Debian Med policy.

"Having in both" is the wrong expression.  Debian Med is pure Debian and
thus we bring the package into official Debian and it is available for
all users in medicine and neuroscience.  You might like to understand
the idea of Debian Pure Blends[1].

The actual Debian Med policy describes some conventions and workflows we
have agreed upon inside the packaging team.  I somehow have the feeling
that it might create less work for you if you follow the advise of
Yaroslav and he might sponsor the package.  However, in case NeuroDebian
people might face some time constraints I'd happily work as fallback for
the final push to the Debian mirror.  We have some record of teaching
people inside our team[2] and considering, that the packaging status
looks quite advanced I see no problem to finalise the process.

> > I do not see any general problem here, except that you need to remember
> > that new packages can only go to unstable / testing and if you want to
> > have the package in Debian stable you need to wait for the next release
> > (Jessie, Debian 8).
> 
> no problem.
> 
> Thanks for your insights and help

You are welcome

      Andreas.


[1] http://blends.alioth.debian.org/blends/
[2] http://wiki.debian.org/DebianMed/MoM

-- 
http://fam-tille.de


Reply to: