While at it, could you please add some rudimentary smoke test to fsleyes and 
run it at build time?
Before uploading this nibabel I did run package rebuilds for all dependants to 
see if there were no regression...
Do you know what particular function changed its API? May be there could be a 
safe default to introduce to maintain compatibility

On October 20, 2017 9:11:45 AM EDT, Michael Hanke <[email protected]> 
wrote:
>Thanks, we saw that too yesterday. It is on my list of things to fix,
>by
>updating fsleyes, presumably.
>
>michael
>
>
>
>On Oct 20, 2017 14:58, "marco tettamanti" <[email protected]>
>wrote:
>
>> Dear Neurodebianers,
>> a recent upgrade from python-nibabel 2.1.0 to 2.2.0 broke the
>> functionality of fsleyes 0.10.1-2 installed on my Debian testing
>distro:
>>
>> Linux bll4 4.12.0-2-amd64 #1 SMP Debian 4.12.13-1 (2017-09-19) x86_64
>> GNU/Linux
>>
>> Nifti images were not displayed and loading caused the error message:
>> "read_arguments takes exactly 3 arguments (4 given)"
>>
>> Reverting back to python-nibabel 2.1.0 solved the problem.
>>
>> Best wishes,
>> Marco
>>
>> --
>> Marco Tettamanti, Ph.D.
>> Nuclear Medicine Department & Division of Neuroscience
>> IRCCS San Raffaele Scientific Institute
>> Via Olgettina 58
>> I-20132 Milano, Italy
>> Phone ++39-02-26434888 <+39%2002%202643%204888>
>> Fax ++39-02-26434892 <+39%2002%202643%204892>
>> Email: [email protected]
>> Skype:
>mtettamantihttp://scholar.google.it/citations?user=x4qQl4AAAAAJ
>>
>>
>>
>>
>> *Rispetta l’ambiente: non stampare questa mail se non è necessario.
>> Respect the environment: if it's not necessary, don't print this
>mail.*
>>
>> _______________________________________________
>> Neurodebian-users mailing list
>> [email protected]
>>
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/neurodebian-users
>>

-- 
Sent from a phone which beats iPhone.
_______________________________________________
Neurodebian-users mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/neurodebian-users

Reply via email to