ok - done, 0.7.1-2 went into neurodebian, wheezy users should become
happier ;) cheers
On Sun, 12 Jan 2014, Alexandre Gramfort wrote:
> all good for me.
> I'll let you know when we merge the PR with the py 2.6 fixes.
> I'll then backport and tag 0.7.2
> thanks
> Alex
> On Sun, Jan 12, 201
all good for me.
I'll let you know when we merge the PR with the py 2.6 fixes.
I'll then backport and tag 0.7.2
thanks
Alex
On Sun, Jan 12, 2014 at 7:39 PM, Yaroslav Halchenko
wrote:
> ok -- while "support 2.6" actions are cooking I thought it would be
> worthwhile to reupload to NeuroDebian
ok -- while "support 2.6" actions are cooking I thought it would be
worthwhile to reupload to NeuroDebian a build without 2.6.
Would there be objections if I push to git the following commit and upload
generated packages to NeuroDebian. Marked changelog as 'neurodebian' since
that is where it is
>
> or may be you would prefer to adjust that one to stay 2.6 compatible?
>
I guess that would be better as it should stay compatible with 2.6 ...
it's a mistake on our side... I'll setup a jenkins on 2.6 to avoid this
issue
in the future.
> also for testing, I am usually trying to test with al
On Sat, 11 Jan 2014, Yaroslav Halchenko wrote:
> ah -- so the minimal supported Python is 2.7? then we should add
> X-Python-Version: >=2.7
or may be you would prefer to adjust that one to stay 2.6 compatible?
also for testing, I am usually trying to test with all supported
versions, which cou
ah -- so the minimal supported Python is 2.7? then we should add
X-Python-Version: >=2.7
to source package paragraph (top) within debian/control then
I am yet to furnish package for the new release... since it is
backports/NeuroDebian specific -- I will do that... hopefully later
today and push
hi,
I just gave a try to "apt-get install python-mne" on a fresh neurodebian VM
downloaded at:
http://neuro.debian.net/vm.html
and I get the error below.
any idea what's going on?
@yarik can you reproduce?
Thanks,
Alex
--
brain@neurodebian:~$ sudo apt-get install python-mne
Reading package
hi Andreas,
I just pushed to the repo version 0.7.1 with:
git import-orig --pristine-tar ../mne-python_0.7.1.orig.tar.gz
let me know if we're good.
Best,
Alex
--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.d
hi guys,
FYI I just tagged v0.7.1 on github.
For some obscure reasons I still depend on Andreas to
update the package on debian.org...
thanks
Alex
On Thu, Nov 28, 2013 at 3:52 PM, Yaroslav Halchenko wrote:
>
> On Wed, 27 Nov 2013, Alexandre Gramfort wrote:
>
>> >> Let me know when we can adv
On Wed, 27 Nov 2013, Alexandre Gramfort wrote:
> >> Let me know when we can advertise debian packaging.
> > Since I just uploaded this now only depends from ftpmaster accepting the
> > package (sorry, currently this simply takes about one month for
> > accepting new packages). As the owner of t
Hi,
On Wed, Nov 27, 2013 at 11:12:51PM +0100, Alexandre Gramfort wrote:
> > Since I just uploaded this now only depends from ftpmaster accepting the
> > package (sorry, currently this simply takes about one month for
> > accepting new packages). As the owner of the ITP bug you will be
> > notifie
hi,
> Great. I have importet the new upstream tarball and pushed including
> pristine-tar.
perfect
> Done. Please remind that also the Git repository is now
>
>ssh://git.debian.org/git/debian-med/python-mne.git
I updated my .git/config
> If I were you I would stop maintaining this. Peop
Hi Alexandre,
On Tue, Nov 26, 2013 at 06:50:13PM +0100, Alexandre Gramfort wrote:
> we have now released mne-python. See tag v0.7
Great. I have importet the new upstream tarball and pushed including
pristine-tar.
> > Packaging is fine. The only change I would propose to move the VCS from
> >
hi Andreas,
we have now released mne-python. See tag v0.7
> Packaging is fine. The only change I would propose to move the VCS from
> mne-python to python-mne and also name the source package python-mne.
> This would be way more comfortable from my personal feeling how things
> should be.
feel
Hi Alexandre,
On Mon, Nov 25, 2013 at 10:02:07PM +0100, Alexandre Gramfort wrote:
> hi Andreas,
>
> I've pushed a new tag v0.7rc5
>
> all PRs have now been merged and the release should happen tomorrow.
>
> Can you just confirm that we're good on the debian side?
I tested the packaging and com
hi Andreas,
I've pushed a new tag v0.7rc5
all PRs have now been merged and the release should happen tomorrow.
Can you just confirm that we're good on the debian side? I'd love to avoid
a hot fix tomorrow due to a problem with debian packaging :)
yaroslav : I've updated the github debian branch
hi Andreas,
> Well, having a target in debian/rules is not sufficient. You could even
> put a target "take_over_world_domination" and finally nothing will
> happen if you have no rule that depends from this target. :-)
indeed :)
> I just merged this target into override_dh_installman and now it
Hi Alexandre,
On Sun, Nov 24, 2013 at 04:06:34PM +0100, Alexandre Gramfort wrote:
> > Would you mind writing a man page for mne? Moreover you did not yet
> > commented my suggestion to drop the term "python" inside the software
> > name.
>
> the man page for the mne command should be generated a
hi,
> just builded successfully and pushed some slight polishing changes.
great thanks.
> Would you mind writing a man page for mne? Moreover you did not yet
> commented my suggestion to drop the term "python" inside the software
> name.
the man page for the mne command should be generated aut
Hi,
just builded successfully and pushed some slight polishing changes.
Would you mind writing a man page for mne? Moreover you did not yet
commented my suggestion to drop the term "python" inside the software
name.
Kind regards
Andreas.
On Sat, Nov 23, 2013 at 10:46:07PM +0100, Alexa
hi,
> I adapted packaging in Git to 0.7~rc3 and we are down to only one failed
> test:
>
> -
> TOTAL 20945 817361%
> --
> Ran 290
Hi Alexandre,
On Sat, Nov 23, 2013 at 03:50:20PM +0100, Alexandre Gramfort wrote:
> > I have tried to build the package and noticed that not all the test
> > are passing. For instance:
>
> the full test suite requires a large download but it can be skipped while
> maintaining > 60% coverage of t
hi Andreas,
> Hmmm, I tried the same and it went fine so far (see latest commit;
weird
>> here is my git config:
>>
>> gramfort@tsilinuxd74:mne-python(master)$ cat .git/config
>> [core]
>> repositoryformatversion = 0
>> filemode = true
>> bare = false
>> logallrefupdates = true
>> [remote "origi
Hi Alexandre,
On Fri, Nov 22, 2013 at 04:26:42PM +0100, Alexandre Gramfort wrote:
> I created a v0.7rc2 tag. git does not accept ~ in tag name.
OK.
> gramfort@tsilinuxd74:mne-python(master)$ uscan --verbose --force-download
> -- Scanning for watchfiles in .
> -- Found watchfile in ./debian
> --
hi,
I created a v0.7rc2 tag. git does not accept ~ in tag name.
see log:
gramfort@tsilinuxd74:mne-python(master)$ uscan --verbose --force-download
-- Scanning for watchfiles in .
-- Found watchfile in ./debian
-- In debian/watch, processing watchfile line:
opts="dversionmangle=s/.dfsg$//,fil
Hi Alexandre,
On Thu, Nov 21, 2013 at 05:40:44PM +0100, Alexandre Gramfort wrote:
> > enough.
>
> gramfort@tsilinuxd74> git import-orig --pristine-tar
> ../mne-python_0.7rc1.orig.tar.gz
In my first mail about the RC candidate I suggested the version
mne-python_0.7~rc1.orig.tar.gz
(please m
Hi Alexandre,
On Wed, Nov 20, 2013 at 11:20:10PM +0100, Alexandre Gramfort wrote:
> are the services back online?
Yep - since yesterday evening. That's a good timing. ;-)
> we were thinking about releasing next tuesday and were hoping
> to have proper debian packaging then.
> thanks again for
>> uscan --verbose --force-download
>> git import-orig --pristine-tar mne-python-0.7rc1.tar.gz
>>
>> but it does not seem to work. It refuses to find the tar.gz
>
> You need to call this when beeing inside the Git repository dir but
> usually the tarball is somewhere else (after using uscan it shou
hi Andreas,
> Yep - since yesterday evening. That's a good timing. ;-)
good
> You might like to try:
>
>gbp-clone ssh://git.debian.org/git/debian-med/mne-python.git
>
> to check out what I injected into the Debian Med git. Please be
> not astonished about the fact that I was using version
Hi Alexandre,
On Thu, Nov 21, 2013 at 04:29:10PM +0100, Alexandre Gramfort wrote:
> > to check out what I injected into the Debian Med git. Please be
> > not astonished about the fact that I was using version 0.6. It is
> > simply what
> >
> >uscan --verbose --report
>
> I now created the v
Hi Yaroslav,
can you please fill in this short form:
[ ] I will keep on with python-mne and NeuroDebian team will be
maintainer
[ ] Andreas, please take over python-mne into Debian Med
maintenance
Both is fine for me, but we need some decision.
Alexandre, I think it is a good i
hi,
thanks Andreas and Yaroslav for this lively discussion :)
To be honest, I have no opinion of what's the best way of doing
things and I don't really read between the lines in your comments.
I also don't see me understanding all the details of debian packaging
as I am not likely to do this ever
On Wed, Nov 06, 2013 at 11:06:16PM +0100, Andreas Tille wrote:
> Hi,
>
> just one point I always forget to append at the end of my mails: I'm
> personally quite irritated when the language a program is written in is
> part of the name. Considering a
>
>linux-c/asm
>apache-c
>kde-c++
Hi,
just one point I always forget to append at the end of my mails: I'm
personally quite irritated when the language a program is written in is
part of the name. Considering a
linux-c/asm
apache-c
kde-c++
eclipse-java
...
you get the idea. From a users perspective it is perfec
On Wed, 06 Nov 2013, Andreas Tille wrote:
> > > 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 go
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`.
>
hi Andreas,
> On Tue, Nov 05, 2013 at 05:52:29PM +0100, Alexandre Gramfort wrote:
>> please have a look at our debian branch:
>>
>> https://github.com/mne-tools/mne-python/tree/debian
>
> Looks good from quick view without doing an actual build. I have
> attached a fix for the debian/watch file -
Hi Alexandre,
On Tue, Nov 05, 2013 at 05:52:29PM +0100, Alexandre Gramfort wrote:
> please have a look at our debian branch:
>
> https://github.com/mne-tools/mne-python/tree/debian
Looks good from quick view without doing an actual build. I have
attached a fix for the debian/watch file - the fi
hi Andreas,
please have a look at our debian branch:
https://github.com/mne-tools/mne-python/tree/debian
let me know if I can do anything.
Our official 0.7 release should be in the next couple of weeks.
It would be great to have it then in debian.
Cheers,
Alex
On Tue, Nov 5, 2013 at 5:03 PM
Hi Alexandre,
thanks for your ITP which is very interesting for Debian Med. We would
be really happy if you would maintain this package in the Debian Med
team. The procedure to do so is described in our team policy[1].
Please do not hesitate to contact us via our (see CC) mailing list if
someth
Package: wnpp
Severity: wishlist
Owner: Alexandre Gramfort
* Package name: python-mne
Version : 0.7.git
Upstream Author : Alexandre Gramfort
* URL : https://github.com/mne-tools/mne-python
* License : BSD
Programming Lang: Python
Description : Python m
41 matches
Mail list logo
