DEP: Update Neurodebian AFNI pin

[effigies]

Builds seem to be breaking on this.

@yarikoptic Is this a bug, or does Neurodebian not keep old versions of packages around?

[yarikoptic]

yes -- ATM there is no multiple versions support (we use reprepro). BUT if you really need specific previous version -- I could make it happen ... let me know

[chrisgorgo]

Tested locally

[effigies]

@yarikoptic Just making sure things are working as expected on your end. It's annoying that the package disappeared, but we weren't depending on the behavior of that specific version.

Perhaps we should consider setting a pin that's resilient to updates like that, but that's an issue for another day.

[satra]

@yarikoptic - afni really needs to be updated, especially post this year's fixes - i'm just making more noise :)

[yarikoptic]

yeap -- I would also love to see it updated, so contributing to you @satra with the whining of my own (while listening to the talk on Pain)! Let's bring the level of complaints even higher -- @mih and @aqw . Time will come... time will come... I guess

[yarikoptic]

although that issue is exactly the opposite to the one in question here @satra -- since desire is to have old pre-specified one :-P

[satra]

@yarikoptic - didn't we do that for fsl in simple workflow script - get any latest version available on a particular date?

[mih]

But who will win: (A) "When is FSL coming?" or (B) "When is AFNI coming?" I'll grab some chips while I watch the race.... ;-)

…

On Wed, Jun 14, 2017 at 4:54 PM, Yaroslav Halchenko < ***@***.***> wrote: although that issue is exactly the opposite to the one in question here @satra <https://github.com/satra> -- since desire is to have old pre-specified one :-P — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#557 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIVH3Fa5paEZycm_jrQP1RnHSvT6LqAks5sD_Q9gaJpZM4N40bN> .

-- Michael Hanke http://psychoinformatics.de

[aqw]

@yarikoptic We're doing a cluster upgrade here in early->mid july, so I can't touch AFNI until then.

AFNI updating stalled because there was an effort (lead by @yarikoptic IIRC) to track upstream more closely, do everything on github, and get the cmake build system upstreamed. I don't know where things stand right now with coordinating with upstream. But I'm 100% for it, and once cluster-fest is finished, I will happily dedicate time to it if it's more than a one man effort. Because there's a lot of complexity right now with brining that package up to date.

---Alex

[yarikoptic]

@satra -- yeap, we did, and that is why I said that it could be done but with elevating some temporary curtain of security through obscurity ;)

@aqw there was effort indeed. upstream is on github, some tests are ran... but I haven't managed yet to replicate full upstream build structure within cmake, thus stalled... should not stop anyone update current debian-specific portion, if anything should be easier since upstream repo is now on github and some tests are already merged...

PS damn - they have no popcorn here