Re: [tryton-debian] Any volunteer to update GNUHealth packages
Hi Mathias, On Fri, Feb 20, 2015 at 01:25:38PM +0100, Mathias Behrle wrote: ... (stripped since no need to add anything) In short: If you think you found a proper way to create GNUHealth packages on debian.tryton.org it would probably a nice comfort for some GNUHealth users who intend to run Debian (or one of its derivatives). I think, it will be a good concept to make the gnuhealth packages in the same way as the current Tryton packages, to provide them suitable and with bugfixes included for the relative Debian and Tryton release via debian.tryton.org. For a demo package, that could serve as a base also for production environments I am leaning to some dockerized environment. The first step has been done here[0], more to follow. [0] https://github.com/mbehrle/docker-tryton-server Cool. Any volunteer here on this list to test this work? Kind regards Andreas. PS: Emilien, thanks for your ACK-mail. This kind of information is very productive. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150220130922.gb15...@an3as.eu
Re: [tryton-debian] Any volunteer to update GNUHealth packages
* Andreas Tille: Re: [tryton-debian] Any volunteer to update GNUHealth packages (Thu, 12 Feb 2015 16:29:26 +0100): Hi Andreas, sorry for not answering this issue earlier. thanks for your answer anyway. On Mon, Feb 09, 2015 at 11:37:09AM +0100, Mathias Behrle wrote: * Andreas Tille: Any volunteer to update GNUHealth packages (Mon, 9 Feb 2015 08:40:47 +0100): GNUHealth 2.8.1 was released which is using tryton 3.4.0. We lost the official GNUHealth package recently due to incompatibilities with tryton. Any volunteer to prepare a package for exoerimental is more than welcome. Could you please point out, what's your motivation to call for this work again in this way Just for clarification: I did not intended to specify any way how the GNUHealth packages are created. My intention was that some work that was done previously should not be thrown away. Any enhancement that might serve our users properly is welcome. - against the pronounced will of the gnuhealth maintainers (I talked once again to the gnuhealth maintainers at this years Tryton Unconference in Leipzig, which are not in favor of having Debian packages but prefer a distribution agnostic way of installation) Generally speaking I'm careful about the pronounced will of a certain representative of a project that is given orally on a conference. I personally met another member of the project at 2011 at Med@Tel who was very keen on packages. It might depend from the time (my information is not as current as yours) and the representative (may be the person I have met is not a technican coming from the Tryton programmers). Thanks for posting those interesting links from debian-med, I joined the list later and didn't have any knowledge ot them. Summarizing the aspects around the gnuhealth packaging it becomes evident to me, that there were some lacks in communication(s), that added one to the other resulting in a more or less unusable package (as is the current state in svn). Just to be clear (I think to know you that you like clear words) and without the intention to accuse anyone I would see the main lacks in - gnuhealth people talking to different debian people without saying, that they are in contact with respectively the other - debian-med people not getting in contact with debian tryton maintainers early to coordinate the packaging (perhaps not seeing at the time, that gnuhealth modules are just another set of Tryton modules) - the packager not getting into contact with the framework upstream (i.e. Tryton) related to questions for the setup of the application in what concerns the framework. Those facts added to the result of the communication being later much more complicated, often frustrating and quite some work having been done to no avail (the latter not about the whole gnuhealth package, because some aspects can hopefully be reused in the new concept). I will try to learn from those facts to be clairaudient and curious enough to ask the participants about what contacts and which work were already done. - according to [0][1] the moderate interest in the subject I'm not sure that these links are telling something about the moderate interest but I agree that for specific software like software in medicine the interest measured in popcon users is low. I personally do see some sense in delivering packages anyway and I have good reasons for this but I would like to discuss this in a more generic thread like this GNUHealth related one. - still with the problematic concept of doing *one* package As I said above: I do not insist on this concept. I strongly believe in the Do-O-cracy principle of Debian where the doer decides how things will be done. - still with the unsolved problem to have gnuhealth modules compatible with the rest of the Tryton suite inside Debian with a justifiable amount of effort to do for the maintainer as well as for the release and security team I am volunteering to do the gnuhealth packages under the following prerequistes: - you give me a number of people interested in Debian gnuhealth packages apart from you and Emilien ;) (please take this from the humorous side...) I would need to check whether the recipients of the mail to the Debian Med list back in 2011[3] remains and might qualify as number of people interested - gnuhealth packages made by me will be in the well-proven generic way of the current Tryton modules I have no technical background of Tryton and thus I will simply trust the people who are dealing with this. - gnuhealth packaging (VCS) will be like for all Tryton modules on alioth +1 - gnuhealth packages will be made available outside of Debian on debian.tryton.org (the only way to make them currently available in a clean and seasoned way to the users with having the relative gnuhealth suite always being dedicated to the correct Tryton series and thus
Re: [tryton-debian] Any volunteer to update GNUHealth packages
2015-02-20 13:25 GMT+01:00 Mathias Behrle mathi...@m9s.biz: * Andreas Tille: Re: [tryton-debian] Any volunteer to update GNUHealth packages (Thu, 12 Feb 2015 16:29:26 +0100): [snip] Just a quick ACK to indicate that I agree with the statements in this email and Andreas' previous message. Cheers, Emilien
Re: Bug#778852: RFS: ismrmrd/1.2.1-1 [ITP #732360] -- ISMRM Raw Data Format.
Thanks Andreas, Can I ask you to re-upload ismrmrd please ? I forgot to change the maintainer field to d-med, but more importantly, did not license the debian/ folder under a license compatible with upstream, which could cause problems with patches in the future. Thanks ! For the D-M application, 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 the imaging task file. Since I am a member of d-med on Alioth, I am supposed to have access, right ? The following user groups have commit permissions: 1. Debian Developers 2. Members of Blends team This has advantages and disadvantages - you have hit the latter. :-) If you want to have commit permissions you can join group 1. (we talked about this recently ;-)) or 2. (which is simple). Or you simply ask me to commit something like this: $ svn diff Index: imaging === --- imaging (Revision 4142) +++ imaging (Arbeitskopie) @@ -542,6 +542,8 @@ Depends: mia-tools, mialmpick, mia-viewit +Depends: ismrmrd-tools + ; Added by blends-inject 0.0.7. [Please note here if modified manually] Suggests: connectomeviewer Published-Authors: Gerhard S, Daducci A, Lemkaddem A, Meuli R, Thiran J-P and Hagmann P Index: imaging-dev === --- imaging-dev (Revision 4136) +++ imaging-dev (Arbeitskopie) @@ -169,3 +169,5 @@ Depends: libedf-dev Depends: python-imageio + +Depends: libismrmrd-dev ... which I did right now. Thanks for your work on this Andreas. -- http://fam-tille.de
Re: Bug#778852: RFS: ismrmrd/1.2.1-1 [ITP #732360] -- ISMRM Raw Data Format.
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 the imaging task file. Since I am a member of d-med on Alioth, I am supposed to have access, right ? The following user groups have commit permissions: 1. Debian Developers 2. Members of Blends team This has advantages and disadvantages - you have hit the latter. :-) If you want to have commit permissions you can join group 1. (we talked about this recently ;-)) or 2. (which is simple). Or you simply ask me to commit something like this: $ svn diff Index: imaging === --- imaging (Revision 4142) +++ imaging (Arbeitskopie) @@ -542,6 +542,8 @@ Depends: mia-tools, mialmpick, mia-viewit +Depends: ismrmrd-tools + ; Added by blends-inject 0.0.7. [Please note here if modified manually] Suggests: connectomeviewer Published-Authors: Gerhard S, Daducci A, Lemkaddem A, Meuli R, Thiran J-P and Hagmann P Index: imaging-dev === --- imaging-dev (Revision 4136) +++ imaging-dev (Arbeitskopie) @@ -169,3 +169,5 @@ Depends: libedf-dev Depends: python-imageio + +Depends: libismrmrd-dev ... which I did right now. Thanks for your work on this Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150220173626.gb23...@an3as.eu
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 Programming Lang: C++ Description : ISMRM Raw Data Format The ISMRM raw data format is a specification of a common format to represent and share magnetic resonance imaging raw and image data. The ISMRMRD library is a C++ implementation of such format, plus a set of tools to generate and validate ISMRMRD datasets. It builds the following binary packages: libismrmrd1.2 -- shared library libismrmrd-dev -- header and development files libismrmrd-doc -- html documentation ismrmrd-tools -- standalone executables ismrmrd-schema -- validation schema These binary packages have been successfully tested over the past few months using the following PPA: https://launchpad.net/~ghisvail/+archive/ubuntu/ismrmrd The source package can be checked out at: http://anonscm.debian.org/gitweb/?p=debian-med/ismrmrd.git This package will be maintained by the Debian-med Team and sponsored via the Sponsorship of Blends. Best regards, Ghis -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54e762b6.5030...@gmail.com
Re: Bug#778852: RFS: ismrmrd/1.2.1-1 [ITP #732360] -- ISMRM Raw Data Format.
On Fri, Feb 20, 2015 at 08:34:06PM +, Ghislain Vaillant wrote: Thanks Andreas, Can I ask you to re-upload ismrmrd please ? I forgot to change the maintainer field to d-med, but more importantly, did not license the debian/ folder under a license compatible with upstream, which could cause problems with patches in the future. Thanks ! I can certainly do but I think it is better to answer the package in new mail from ftpmaster with Please reject and wait until this has happened. Otherwise there will be some conflict with equally named files ... For the D-M application, I am seriously considering it. :-) Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150220204759.ge23...@an3as.eu
