On Wed, May 27, 2015 at 10:09:45AM +0200, Andreas Tille wrote:
On Wed, May 27, 2015 at 09:32:39AM +0200, Alexandre Gramfort wrote:
I don't know what I can do about mayavi2 packaging.
That's simple: Maintain the package which is currently unmaintained. :-)
As far as I can tell, this is a
hi Andreas,
thanks for clarifying. I'll take care of packaging of v0.9 just released asap.
I'll remove mayavi from Build-Depends to be safe.
Alex
On Wed, May 27, 2015 at 10:09 AM, Andreas Tille andr...@an3as.eu wrote:
Hi Alexandre,
On Wed, May 27, 2015 at 09:32:39AM +0200, Alexandre Gramfort
Hi Alexandre,
On Wed, May 27, 2015 at 09:32:39AM +0200, Alexandre Gramfort wrote:
I don't know what I can do about mayavi2 packaging.
That's simple: Maintain the package which is currently unmaintained. :-)
To avoid removing
python-mne from debian-science
To clarify the terminology:
On Wed, May 27, 2015 at 4:09 AM, Andreas Tille andr...@an3as.eu wrote:
Hi Alexandre,
On Wed, May 27, 2015 at 09:32:39AM +0200, Alexandre Gramfort wrote:
I don't know what I can do about mayavi2 packaging.
That's simple: Maintain the package which is currently unmaintained. :-)
Hi Andreas,
I don't know what I can do about mayavi2 packaging. To avoid removing
python-mne from debian-science one option is to remove it from depends
as mayavi2 is a weak dependency of python-mne. 95% of python-mne
works fine without mayavi.
what do you think?
let me know
Best,
Alex
On
Hi,
the RC bug #785627 did not received any response and according to its
rdepends mayavi2 affects several packages in Debian science which should
be hit by the same autoremoval.
There are other open bugs against mayavi2 which seem not hard to fix and
it is lagging begin upstream. Do we want to
6 matches
Mail list logo
