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 0.6. It is > simply what > > uscan --verbose --report I now created the v0.7rc1 tag and updated the debian branch. The lintian warnings you mentioned have been fixed with Yaroslav's guidance a few weeks ago now. > was resulting - so I downloaded this for the moment and did > > git import-orig --pristine-tar mne-python-0.6.tar.gz I tried : 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 > When trying this I realised that for running the tests the Build-Depends > python-coverage was missing. I added now : python-coverage let me know what's next besides what's below thanks for your help Alex > to import this source. The next step would be > > dch -i > > and adjust the version of the changelog entry to 0.7~rc1 (we might drop > my 0.6 version later since it was never released anyway). Now you can > do > > git-buildpackage --git-ignore-new > > (perhaps also check with droping the comments I injected in the tests). > > Once you might face any stumbling stone you might `git push` and just > ask here for further help. We might iterate that way until you tag > 0.7 and we will work on the final release. From my point of view it > looks promising for some timely upload to the Debian New queue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
