Bug#995829: ITP: itk5 -- extensive suite of software tools for image analysis

Package: wnpp Severity: wishlist Owner: Ghislain Vaillant X-Debbugs-Cc: debian-de...@lists.debian.org, debian-med@lists.debian.org * Package name: itk5 Version : 5.2.1 Upstream Author : NumFOCUS * URL : https://itk.org * License : Apache-2.0 Programming Lang

Re: dcm2niix -- I have an intent to take over (still under Debian Med team), objections?

Le lun. 3 déc. 2018 à 22:39, Yaroslav Halchenko a écrit : > > On Mon, 03 Dec 2018, Andreas Tille wrote: > > > Hi Yaroslav, > > > On Mon, Dec 03, 2018 at 03:36:19PM -0500, Yaroslav Halchenko wrote: > > > > Chris asked me to take over maintenance in Debian as well, and Ghislain > > > blessed me as

Re: RFS: simpleitk/1.0.1-2

Le dimanche 11 mars 2018 à 19:04 -0400, Afif Elghraoui a écrit : > > على الأحد 11 آذار 2018 ‫16:04، كتب Afif Elghraoui: > > > > > > على الأحد 11 آذار 2018 ‫14:04، كتب Ghislain Vaillant: > > > Could someone upload simpleitk/1.0.1-2 [1], please? > >

RFS: simpleitk/1.0.1-2

Dear all, Could someone upload simpleitk/1.0.1-2 [1], please? Changes since last upload: * Cherry-pick upstream fix for FTBFS on i386. Thanks to Adrian Bunk for reporting (Closes: #892459) * Point the VCS URIs to salsa.debian.org * Bump the debhelper version to 11 * Bump the

Access to salsa

Dear all, Could someone grant me (vaillant-guest) access to the team on salsa? I am already a member. Thanks, Ghis

RFS: dcm2niix/1.0.20171215-1

Hi team, Could someone sponsor this update for dcm2niix [1]? Nothing much to report besides an update to the latest upstream release and version bumping for debhelper and standards. It's already pushed and tagged to the packaging repository and has been validated on debomatic. [1]

Migration to salsa

Hi team, Are there any plans to migrate the team to salsa? What are the blockers, if any? Cheers, Ghis

Re: ismrmrd FTBFS on armhf

Le 17/12/17 à 15:40, Adrian Bunk a écrit : On Sun, Dec 17, 2017 at 02:33:03PM +, Ghislain Vaillant wrote: ISMRMRD uses a non-portable instruction (#pragma pack) which modifies the memory alignment of its data structures. It seems neither armhf nor sparc64 supports it, hence the failure

Re: ismrmrd FTBFS on armhf

ISMRMRD uses a non-portable instruction (#pragma pack) which modifies the memory alignment of its data structures. It seems neither armhf nor sparc64 supports it, hence the failure of the test suite for both architectures. I am not sure what the best course of action is. Either leaving things

Re: src:mypy: Split public modules from mypy package

here is mr-c) Pe 30 oct. 2017 17:38, "Ghislain Vaillant" <ghisv...@gmail.com <mailto:ghisv...@gmail.com>> a scris: No problem. Version 0.550 is just around the corner, so I'll take the opportunity of a new release to implement the necessary changes. Ghis

Re: RFS: simpleitk/1.0.1-1 [ITP]

Hi Afif, thanks for taking care of the review (and uploading dcm2niix). On 02/11/17 02:05, Afif Elghraoui wrote: Based on the Python policy, the python3-dev build-dependency should be either python3-all-dev, or specific to a minor version of python3 (like python3.5-dev) [2]. Since the build

RFS: simpleitk/1.0.1-1 [ITP]

Hi all, Could someone from the team sponsor the initial upload for simpleitk [1]. Perhaps Gert (cc'd), since he is also involved with packaging ITK? [1] https://anonscm.debian.org/cgit/debian-med/simpleitk.git Cheers, Ghis

RFS: dcm2niix/1.0.20171017-1

Hi everyone, Could someone from the team sponsor the latest update to dcm2niix [1]. [1] https://anonscm.debian.org/cgit/debian-med/dcm2niix.git Cheers, Ghis

Re: [Ann] Changed Debian Med policy: SVN is now deprecated

On 22/09/17 11:09, Mattia Rizzolo wrote: On Fri, Sep 22, 2017 at 12:06:03PM +0200, Gert Wollny wrote: As for insighttoolkit ... Has anyone experience on how to manage a multi-source project in git? git-buildpackage (gbp) since not so many months has support for multi-tarball packages. It's

Re: InVesalius new upstream version

On 14/08/17 15:17, Mattia Rizzolo wrote: 2. I created a debian/source/options file with extend-diff-ignore option. During the package generation I'm moving the cython source files to another folder to compile them. This is causing errors with generation of diff file relative to the orig file. So

Re: Fwd: [WSSSPE] WSSSPE5.1 & WSSSPE5.2

I second that. Do you have a particular format in mind? I saw you had something lined up about CWL. Is that for the UKRSE conference, or the workshop before? I should apologize for my lack of knowledge about the format of the conference. FYI, it would be my first attendance to it, assuming I can

RFS: dcm2niix/1.0.20170429-1 [experimental]

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the following package: * Package name: dcm2niix   Version : 1.0.20170429-1   Upstream Author : Chris Rorden * URL : https://github.com/rordenlab/dcm2niix * License : BSD

Re: bits about the future with VTK in Buster

On Thu, 2017-04-06 at 10:27 +0200, Gert Wollny wrote: > Hello all, > > I just drop this here for future reference. Thanks for looking into it and summarizing your findings. > I've experimented a bit with VTK-7.1 and among other, minor issues I > came across the problem that VTK now defaults

Re: Help needed for pandas bug: Could anybody verify the suspicion that tzdata might have some influence?

On 28/03/17 10:37, Andreas Tille wrote: PS: Yaroslav, you know my opinion about using Vcs outside of debian.org and deriving from policies that are widely established. Currently git://github.com/neurodebian/pandas.git is not even featuring the latest uploads - last changelog entry

Re: Request to Join Project Debian Med from Vojtech Kulvait (kulvait-guest)

On 13/03/17 07:29, Andreas Tille wrote: [Please note that I sent a copy to the list since there is no private information in your mail and *all* technical discussion should be archived on the list.] Hi Vojtech, On Mon, Mar 13, 2017 at 12:01:01AM +0100, Vojtech Kulvait wrote: thank you for

Re: Important News for DebMed graphics package maintainers

Good one Le 6 févr. 2017 6:07 PM, "Roland Fehrenbacher" a écrit : > > Please take this important new order into account or else ... > > https://twitter.com/genetics_blog/status/827267187077373952 > > Sorry, couldn't help posting this to you guys :) > > Cheers, > > Roland > >

Re: Help needed for course lecture about Debian packaging

By getting to know the software you are willing to package? Ghis On Wed, 2017-02-01 at 20:43 +0300, Canberk Koç wrote: > Hello Again , > > We are wondering that specially how can we find the building dependencies of > a source code at first. Did we have a tool for that? ( Source code is only

Re: Help needed for compiling libsbml-odesolver

On Fri, 2017-01-27 at 17:13 +0100, Andreas Tille wrote: > Hi, > > I tried to package libsbml-odesolver[1] but I was running into the same > error as it was reportet on the sundials list[2]: > > ... > In file included from sbmlsolver/processAST.h:44:0, >from

Re: Help for next version of freebayes needed: libseqlib build error

On Fri, 2017-01-27 at 15:28 +0100, Andreas Tille wrote: > Hi, > > Version 1.1.x of freebayes needs libseqlib and I commited some > preliminary packaging to Git[1]. My obviously poor attempt to use > Debian packaged libraries instead of code copies endet up in > > ... > g++ -DHAVE_CONFIG_H -I.

Re: dcm2niix

On Wed, 2017-01-11 at 13:19 -0500, Yaroslav Halchenko wrote: > On Wed, 11 Jan 2017, Ghislain Vaillant wrote: > > > On Wed, 2017-01-11 at 11:22 -0500, Yaroslav Halchenko wrote: > > > Hi Ghislain, > > > Thanks for packaging and uploading to dcm2niix! > > You'r

Re: dcm2niix

On Wed, 2017-01-11 at 11:22 -0500, Yaroslav Halchenko wrote: > Hi Ghislain, > > Thanks for packaging and uploading to dcm2niix! You're welcome. > It is a pity though that we duplicated the effort somewhat since > we maintained dcm2niix within NeuroDebian for a while and didn't upload >

Re: cme and stylistic changes in team uploads

On 25/12/16 23:51, Afif Elghraoui wrote: I think it's enough consistency that people are either using dh_make, debmake, or the debian-med packaging template and just adding to that. If people were writing these packaging files from scratch, there would be real consistency issues. Come on, I am

Re: plastimatch/1.6.5+dfsg1-1 prep

On Tue, 2016-12-06 at 14:38 +0100, Andreas Tille wrote: > Hi again, > > On Tue, Dec 06, 2016 at 11:05:02AM +, Ghislain Vaillant wrote: > > > Hmmm, this message droped in my inbox after uploading. I'm not sure how > > > important this might be - in any case t

Re: consensuscore2: Any news?

On Fri, 11 Nov 2016 14:17:13 -0800 Afif Elghraoui wrote: > Hi, Andreas, > > على الأربعاء 9 تشرين الثاني 2016 ‫03:11، كتب > Andreas Tille: > > > > do you have any news with this issue? > > > > I should have posted an update. Upstream has moved

Re: plastimatch/1.6.5+dfsg1-1 prep

On Tue, 2016-12-06 at 11:01 +0100, Andreas Tille wrote: > Hi Ghislain, > > Other comments: > > > > - "Add libblas-dev dependency (sub-dependency of libdlib-dev) to > > plastimatch" > > > > If libdlib-dev is missing a dependency (BLAS), it should be fixed > > there. Transitive dependencies should

plastimatch/1.6.5+dfsg1-1 prep

On Tue, 2016-12-06 at 08:11 +0100, Andreas Tille wrote: > Hi Gregory, > > On Mon, Dec 05, 2016 at 06:52:07PM -0500, Gregory Sharp wrote: > > > > > I admit if there was an explicit reason I simply forgot it (but its also > > > for amd64, right). > > > > The architectures are amd64 and i386

Re: pyBigWig

On 02/12/16 19:14, Diane Trout wrote: I don't think this is a problem. Policy 4.13 [1] says ~~~ Debian packages should not make use of these convenience copies unless the included package is explicitly intended to be used in this way. ~~~ which I think matches the situation here. Thank you

Re: Versioning of snap-aligner

On 02/12/16 10:38, Andreas Tille wrote: Hi Michael, when browsing throught the list of packages with no sensible uscan result in DMD[1] I stumbled upon snap-aligner. I commited a watch file that is able to detect and download the releases tagged by upstream. IMHO the latest version should be

Re: Considerations for pird (Was: pirs/2.0.2+dfsg-2 follow-up)

On 01/12/16 12:33, Andreas Tille wrote: Hi Ghislain, thanks for your bug fixes and the tracking whether everything went fine afterwards. On Thu, Dec 01, 2016 at 10:31:30AM +, Ghislain Vaillant wrote: Looks like there are more non-portable options being used in pirs according to the build

Re: December

On 29/11/16 18:40, Andreas Tille wrote: Hi Thorsten, On Tue, Nov 29, 2016 at 07:18:27PM +0100, Thorsten Alteholz wrote: how time flies! This time of the year has come again and in order to carry on a tradition, I want to remind everybody of our combined efforts to take care of some poor souls.

Re: [Debian-med-packaging] Bug#841560: Could anybody please check the issue in python-skbio

On 15/11/16 11:58, Kevin Murray wrote: Hi Andreas, On 12:13 15/11, Andreas Tille wrote: On Tue, Nov 15, 2016 at 07:15:03PM +1100, Kevin Murray wrote: There are also old binary packages preventing a testing transition, which I'm not sure how to deal with. If you want to get old package

Re: [Mom] Varmatch package situation

On 02/11/16 07:18, Afif Elghraoui wrote: Varmatch is a pretty new software package and they haven't yet made their first official release. I saw the preprint article, thought it was interesting, and made this start in packaging it as a result. Being unreleased yet, the major concern is for it

Re: Remaining gcc-6 errors

On 09/09/16 16:48, Andreas Tille wrote: Hi Gert, On Fri, Sep 09, 2016 at 05:13:01PM +0200, Gert Wollny wrote: On 09.09.2016 15:54, Andreas Tille wrote: #831126 vxl: FTBFS with GCC 6: vcl_compiler.h:127:4: error: #error "Dunno about this gcc" In the ITK embedded copy this is patched, but

Re: otb is marked for autoremoval from testing

On 02/09/16 07:01, Sebastiaan Couwenberg wrote: On 09/02/2016 06:39 AM, Debian testing autoremoval watch wrote: otb 5.6.1+dfsg-1 is marked for autoremoval from testing on 2016-10-08 It (build-)depends on packages with these RC bugs: 835400: libminc: FTBFS: convert.c:13:18: fatal error: hdf5.h:

Re: Packaging wishlist for this week's H3Africa workshop

On 22/08/16 16:42, Michael Crusoe wrote: One more: snpeff http://snpeff.sourceforge.net/download.html On Mon, Aug 22, 2016 at 5:36 PM, Michael Crusoe > wrote: Hello everyone, I'm at the H3Abionet Cloud computing hackathon

Re: Bug#822110: odil: FTBFS when built with dpkg-buildpackage -A (chrpath fails)

On 22/04/16 07:03, Julien Lamy wrote: It seems that my fix actually made things worse since the builds have failed for almost all architectures [1]. I think the cause is me not reading correctly pbuilder's man page and build testing my previous version with "--debbuildopts -B" instead of

Re: Packaging Python extensions and applications

On 13/04/16 17:37, Julien Lamy wrote: Dear all, While preparing the package of the new upstream release of Odil, I had a couple of questions regarding the packaging of Python extensions and applications. I've read the Debian Python Policy and the Python Style Guides on wiki.debian.org, but I'm

Re: Lets maintain libbpp-phyl-omics in Debian Med team

On 06/04/16 15:46, Andreas Tille wrote: As for the git repository, may I ask why you need to create one? Would that be a local debian copy of the one on github? Makes me think that it would be time to synchronize our local repos and the github one... The Debian *packaging* repository is

Re: Strengthening team by fixing other members bugs

On 04/04/16 09:14, Andreas Tille wrote: Hi, last week I had the idea to declare April as a month of fixing bugs in Debian Med packages. While about eight monthes are left until we the freeze for Jessie will start we should constatly make sure that our packages are free of bugs and are

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

On 09/01/16 08:35, Martin Uecker wrote: Ghislain Vaillant <ghisv...@gmail.com>: FYI, the same trick is used for other dependencies with multiple backends such as OpenCL. What is the state of OpenCL on Debian? The OpenCL headers are regularly updated, so are the main open-source d

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

On 09/01/16 08:35, Martin Uecker wrote: Ghislain Vaillant <ghisv...@gmail.com>: FYI, the same trick is used for other dependencies with multiple backends such as OpenCL. What is the state of OpenCL on Debian? The OpenCL headers are regularly updated, so are the main open-source d

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

On 09/01/16 08:03, Martin Uecker wrote: What are the next steps? Submit an RFS bug [1] and upload the package to mentors [2]. That's the usual route. Maybe the MoM process is different though. To be checked with Andreas. [1] http://mentors.debian.net/sponsor/rfs-howto [2]

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

On 08/01/16 19:29, Martin Uecker wrote: Hi Ghisvail! - Binary packages split-up. I am not quite sure about the usefulness of the bart-dev package. The final compilation line shows: ... i.e. the final output is one executable (bart) with private libraries (libbox, libgrecon...) linked

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

Hi Martin, Great to see that your packaging work is progressing. Here are a few remarks on my side: - Binary packages split-up. I am not quite sure about the usefulness of the bart-dev package. The final compilation line shows: gcc -O3 -ffast-math -std=c99 -Wmissing-prototypes

Re: Shark / libshark packaging status

I have pushed the repository to d-science and filed an RFS for the initial upload of Shark. If someone could have a look at it and sponsor it, that would be awesome. Thanks, Ghis

Re: Shark / libshark packaging status

. On Thu, Dec 10, 2015 at 08:00:18PM +, Ghislain Vaillant wrote: I have pushed the repository to d-science and filed an RFS for the initial upload of Shark. If someone could have a look at it and sponsor it, that would be awesome. Thanks, Ghis

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

Hi Martin, some pieces of advice below: On 07/12/15 11:26, Martin Uecker wrote: The only issue is that I have to specify the tag with 'gdb' because it looks for 'upstream/v0.2.09' which does not currently exist. Instead of adding these tags, I would prefer to reconfigure 'gdb' to use the

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

On 07/12/15 08:18, Uecker, Martin wrote: Hi Andreas, On Sun, Dec 06, 2015 at 11:59:02PM +, Uecker, Martin wrote: Put simply, pristine-tar is our way to encapsulate access to the source tarball used for packaging. Someone who checks out a d-science repository does not need to know where

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

On 06/12/15 12:32, Uecker, Martin wrote: Hi Andreas, Ok, I put it in /git/debian-med/bart.git as described in the debian-med policy. I checked this out and added Vcs fields and Homepage to Debian control (please pull). I noticed that the pristine-tar branch is missing in the git

Re: Bug#777043: Shark / libshark packaging status

On 30/11/15 12:42, Goswin von Brederlow wrote: Go ahead and work on. I packaged this as it was a dependency for something one of our customers wanted but interest seems to have been reduced since then. So I'm happy passing this on to someone else. MfG Goswin Thanks for passing this

Re: bart - tools for computational magnetic resonance imaging

On 01/12/15 00:15, Uecker, Martin wrote: Hi all, I would love to see our image reconstruction software for magnetic resonance imaging included in Debian. I filed an ITP with more information here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806762 The source code is on Github:

Re: bart - tools for computational magnetic resonance imaging

On 01/12/15 15:04, Uecker, Martin wrote: Ghislain Vaillant: Hi Martin, Let me know if you need assistance on the packaging side. Glad to see more MRI reconstruction software being packaged for Debian. Cheers, Ghis Thank you, Ghis! I am sure that I will need some help. I see that you

Re: Bug#777043: Shark / libshark packaging status

On 01/12/15 10:33, Andreas Tille wrote: On Tue, Dec 01, 2015 at 09:24:12AM +, Ghislain Vaillant wrote: Thanks for passing this on to me. Is there any further action to take on this ITP as a result ? Uploading? :-P Which might be happening soon, upstream has been very responsive to my

Re: bart - tools for computational magnetic resonance imaging

On 01/12/15 16:37, Uecker, Martin wrote: I can set the packaging repository up on d-med and push your initial work to it if you like. That would make collaborative work with members of d-med much easier, myself included. So I tried to do it myself. See my mail to Andreas. Perfect. Don't

Shark / libshark packaging status

Dear all, I recently pushed a candidate source package for Shark [1] to the d-science package repositories [2]. After more careful reading of the different ITP / RFP bugs filed for Shark [3][4], I just realized that someone had already started working on it a while back (Goswin). Please

Re: [po...@debian.org: Bug#802172: ismrmrd: FTBFS on several arches]

I will, sorry for forgetting to push. I will forward the bug upstream to get the test suite fixed, assuming upstream cares for these architectures. Ghis On 18/10/15 07:38, Andreas Tille wrote: Hi Ghislain, I guess you will care about this bug. I noticed that the repository in Debian Med

Re: Maintenance of freeimage over to d-science

, thanks for your work! Please ping me if you need uploading of this package. Also it would be good to port this security patch for the Jessie to close that vulnerability. Best regards Anton 2015-09-27 16:21 GMT+02:00 Ghislain Vaillant <ghisv...@gmail.com>: Dear all, Following the disc

Re: Proper package relationships when a project depends on CBLAS

On 29/09/15 18:09, Felix Salfelder wrote: On Tue, Sep 29, 2015 at 05:49:50PM +0100, Ghislain Vaillant wrote: what is wrong with a builddep on libopenblas-dev|someotherblas-dev? do you want to discard the second option in case the first is available (don't know how to do that)? If I use say

Re: Proper package relationships when a project depends on CBLAS

On 29/09/15 12:08, Felix Salfelder wrote: On Tue, Sep 29, 2015 at 12:01:26PM +0100, Ghislain Vaillant wrote: At the moment, I am building against libopenblas-dev, but the latter is not available on all architectures and therefore restricts the build of the source package (ArrayFire

Maintenance of freeimage over to d-science

Dear all, Following the discussion in Bug#797165, both Anton and I took the initiative of moving the maintenance of freeimage over to Debian Science, since quite a few of our dependencies depend on it. I have pushed a pristine clone of the collab-maint repository in

Re: Lena licensing, how to patch?

On 20/08/15 20:54, olivier sallou wrote: Hi, I have a colleague who have the lena image licensing issue in his package. He tried to patch it but get fuzzing issue when building the package. As it is a binary file and never patched a binary file, has anyone an idea on how to correctly patch this

Re: Policy and Best Practices

On 29/07/15 16:12, Steve M. Robbins wrote: On July 29, 2015 09:40:41 AM Ghislain Vaillant wrote: FYI, I am intending to write a piece on the d-science / d-med policies regarding DEP-14 and its relationship with import-orig and pure Git workflows. Just need to find the time for it. Just like

Re: Git repository of htslib is lacking pristine-tar

On 29/07/15 08:54, Andreas Tille wrote: Hi Charles, On Wed, Jul 29, 2015 at 03:26:55PM +0900, Charles Plessy wrote: ... instead, I used: pristine-tar commit /tmp/htslib-1.2.1.tar.gz 1.2.1 As a result, git-buildpackage did not manage to find the pristine-tar information. This is

Re: Git repository of htslib is lacking pristine-tar

On 28/07/15 11:19, Andreas Tille wrote: Hi Charles, $ gbp clone ssh://git.debian.org/git/debian-med/htslib.git $ cd htslib $ gbp buildpackage gbp:info: Orig tarball 'htslib_1.2.1.orig.tar.gz' not found at '../tarballs/' gbp:error: Pristine-tar couldn't checkout htslib_1.2.1.orig.tar.gz: fatal:

Re: [MoM] Re: Help with Debian packaging of DCMTK++

On 17/07/15 17:33, Julien Lamy wrote: Le 16/07/2015 20:39, Andreas Tille a écrit : That's OK now. I guess your next commits will be a debian/ dir. Feel free to commit your latest stuff you just did and improve from there. I just pushed the first version of the debian dir, which raised a

Re: python-pysam version lagging

Hi guys, just a few additional comments 2015-06-09 9:14 GMT+01:00 Charles Plessy ple...@debian.org: Le Tue, Jun 09, 2015 at 12:38:31AM -0700, Afif Elghraoui a écrit : I was able to build it and clean it up a little more, but the package still has some lint: Hi Afif, thanks a lot for

Access to collab-maint

Dear all, Is there anyone in the team who can grant me access to collab-maint ? I have sent a enquiry email via the Alioth page a while back and never got any reply. I have got some non-science related packages that I'd like to host on collab-maint instead of d-science / d-med. Thank you very

Re: Access to collab-maint

Hi Andreas, On Wed, 15 Apr, 2015 at 3:14 PM, Andreas Tille andr...@an3as.eu wrote: Hi Ghislain, On Wed, Apr 15, 2015 at 02:16:07PM +0100, Ghislain Vaillant wrote: Dear all, Is there anyone in the team who can grant me access to collab-maint ? I have sent a enquiry email via the Alioth

Re: Broken irtk repository

2015-03-19 13:10 GMT+00:00 Andreas Tille andr...@an3as.eu: Hi Ghislain, On Tue, Mar 17, 2015 at 11:51:28PM +, Ghislain Vaillant wrote: Hi Andreas, For this package, I have experimented on an alternative layout for the git repository, following the section entitled When upstream

Re: Broken irtk repository

Hi Andreas, For this package, I have experimented on an alternative layout for the git repository, following the section entitled When upstream uses Git in the git-buildpackage manual [1]. Since the repository only contains the debian/sid and pristine-tar branches (no upstream or master), it

best practice to move a package to team maintainership

Hi everyone, I'd like your opinion regarding the following matter. There is a package I need an update for (h5py), which is now particularly outdated. It is currently being maintained by a solo Debian maintainer, who I contacted regarding this but has yet to reply. So I worked on my own, fixed

Re: Bug#778852: RFS: ismrmrd/1.2.1-1 [ITP #732360] -- ISMRM Raw Data Format.

, I am seriously considering it. Cheers, 2015-02-20 17:36 GMT+00:00 Andreas Tille andr...@an3as.eu: Hi Ghislain, On Fri, Feb 20, 2015 at 05:05:50PM +, Ghislain Vaillant wrote: I have added an entry to the SoB tasks [1]. However, I cannot access the blends svn repository to update

RFS: ismrmrd/1.2.1-1 [ITP #732360] -- ISMRM Raw Data Format.

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for the following package: * Package name: ismrmrd Version : 1.2.1-1 Upstream Author : The ISMRMRD developers * URL : http://ismrmrd.github.io/ * License : Expat

Re: Bug#777000: ITP: limereg -- Lightweight Image Registration. Commandline application for image registration (automatically aligning two images with similar content).

Added cc to debian-med. I personally disagree with your statement on medical image registration. I believe both fast and sophisticated registration tools can live together. Your package would fit perfectly in d-science or d-med, if not both. Regarding your naming scheme, I have nothing against

Re: Bug#772949: RFS: imageio/1.0-1 [ITP] -- Library for reading and writing a wide range of image formats

I have added this package to the debian-science imageanalysis and debian-med imaging-dev tasks. Cheers, - Ghis

Task for MRI (Magnetic Resonance Imaging) development

Dear all, I originally started to contribute to the Debian ecosystem to help make available some of the development library, such as [1], necessary to work with MRI data. In the field of MRI processing, we are currently witnessing a growing interest towards the release of opensource tools /

Re: Task for MRI (Magnetic Resonance Imaging) development

Hi Yaroslav, Thanks for your insights. 2014-12-08 17:36 GMT+00:00 Yaroslav Halchenko deb...@onerussian.com: On Mon, 08 Dec 2014, Ghislain Vaillant wrote: Dear all, I originally started to contribute to the Debian ecosystem to help make available some of the development

Re: Fwd: [iva] - Python 3 code depends on pysam

At worst, can't you just disable the test suite for the Python 3 builds ? Pybuild should allow to do that easily. Ghis 2014-11-24 16:36 GMT+00:00 Jorge Sebastião Soares j.s.soa...@gmail.com: Hi guys, So essentially the package build halts when it tries to run the test suite: This is the