jamovi

hi,

let me think about this. i think it would be useful if we could provide a function to do this. i've created an issue here where you can track my progress.

https://github.com/jamovi/jamovi/issues/1501

jonathon

ah, now what you write is interesting ... i don't think i realised that packagemanager hosted files from that far back. i've updated jmvtools (2.5.5) to use the packagemanager repos. ... it may turn out we can build for the 2.3

jonathon

no, sorry. it really is single user (well, you can have multiple users using it, but they all have the same access). if you need multi-user, i'd suggest our cloud offering:

https://cloud.jamovi.org

cheers

Hi, I've pushed a fix, and once the build machinery is finished, version 2.5.5 should be available for linux. The flatpak build toolchain uses quite aggressive compiler optimisations, which involves making assumptions that aren't always true. I've provided a few more hints to the compiler, so it doe...

hi,

are you able to provide me with steps to reproduce this issue? we'll push out a high priority fix.

jonathon

hi,

sounds like a corrupt file. if you either attach it here, or email it through to contact <at> jamovi.org i'll take a look.

jonathon

hi joao, take a look at the tutorial seol has pointed you towards, and don't hesitate to get in touch if you need help along the way. generally speaking, modules don't require too much maintenance once they're developed, but it comes down to what breaking changes occur in upstream R packages ... if ...

i think binary is what you want.

jonathon

awesome!

yes, python.exe is probably the most important one.

cheers

jonathon

hi, yes it looks as though the firewall is preventing jamovi from opening those ports. it might be worth contacting the firewall vendor, as if it's going to block the ports, jamovi isn't going to run. normally firewalls simply block/filter incoming network traffic, and leave access to the 'loopback'...