Hi Chuck,
in Debian exists a system to verify web sites for new upstream sources
to register changes automatically and enable automatic download. For
this purpose it is extremely helpful if the download file contains the
proper version in the file name. For instance in the case of mriconvert
it would be really helpful to have some downloadable file
mriconvert-2.0.235.source.zip
or something similar. We had really large trouble to find a tricky
solution to enable the automatic version detection (see for instance the
discussion here [1]) and as this conversation shows the habit to not use
the version number in the source download file is somehow error prone.
Could you do us the favour and follow the advise and use the version
number also for the sources as well as you are doing it for the binary
downloads?
Thanks for your understanding
Andreas.
[1] http://lcni.uoregon.edu/~jolinda/MRIConvert/
On Tue, Sep 25, 2012 at 07:43:23AM -0700, Chuck wrote:
> Hi Steve,
>
> Thank you for the report. I will look into this distribution issue.
> FYI, the binaries for OS X and all Linux versions available on the
> MRIConvert web site should be up-to-date with 32-bit code.
>
> Regards,
> Chuck
>
>
> On 12-09-24 07:12 PM, Steve M. Robbins wrote:
> >Hello Chuck,
> >
> >While working my way through my Debian bug list, I noticed this one
> >[1] is still open: MRIConvert does not support 32 bits
> >
> >I tried Mathieu's image on the latest Debian MRIConvert (2.0.235), and
> >it failed as noted in the report: the output is 16 bits, not 32.
> >
> >
> >On Thu, Oct 13, 2011 at 12:43:17PM -0700, Chuck Theobald wrote:
> >>I've made some changes so that MRIConvert emits 32-bit .raw files,
> >>but do not have a way to test. Attached is a tarball with Debian
> >>binaries for testing.
> >Then I tried the binary you attached, and obtained 32 bit output.
> >
> >Scratching my head, I tried the Debian binary again. Same result.
> >Then I noticed the Debian binary's "Help|About" box claims the version
> >is 2.0.217.
> >
> >I went back to my source archives and discovered that the upstream
> >versions in Debian are THE SAME for 2.0.217 and 2.0.235. I went to
> >the download site [2] and discovered that the mriconvert_sources.zip
> >is also the same as 2.0.217.
> >
> >Is it possible that the sources link was not updated when 2.0.235 was
> >released? Could I trouble you to create a new release?
> >
> >Thanks,
> >-Steve
> >
> >[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617342
> >[2] http://lcni.uoregon.edu/~jolinda/MRIConvert/mriconvert_sources.zip
>
>
> --
> Chuck Theobald
> System Administrator
> The Robert and Beverly Lewis Center for Neuroimaging
> University of Oregon
> P: 541-346-0343
> F: 541-346-0345
>
> _______________________________________________
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
