So, it is possible to compile mia-2.4.6, changing a couple of source files (HUGE should be std::numeric_limits<double>::max(); sorry I don't know C).

However, the project seems a bit unmaintained upstream?

Uh, yeh---we could mark it as low priority and leave it for the time being. Ideally, we should poke upstream to ask if they are active etc.

Uh. Sorry.
I've seen the commits in the repository. In reality there are various recent commits.
While current tarred release is 2.4.6 and dates back 2017, there are git commits talking about version 2.4.7 and comments dated August 2019 like "Prep for new bugfix release".

Just for fun and to learn packaging, I wrote a spec file and created a copr repository.
I think it is very dirty, and my goal was to learn packaging (and how to use copr :smile:), nothing more.
At the end of the day such software looks complex and I never used it; and I don't think it will be useful for my daily job.
Another note: I filed an issue to upstream a week ago, but they never replied.

Btw, this is the copr repository: https://copr.fedorainfracloud.org/coprs/alciregi/mia/

Would you like to submit this for review @alciregi ? In the meantime, would you like to join the package-maintainer team as a neuro-sig co-maintainer? You can work on simple updates and learn along the way?

Would you like to submit this for review @alciregi ?

I don't think it is a good move :smile: It is a little mess.
Maybe when upstream will release the new version (looking at git comments it seems they are working on it, sometime)

In the meantime, would you like to join the package-maintainer team as a neuro-sig co-maintainer?

Honestly I don't know if I could really be of any help here.

You can work on simple updates and learn along the way?

If it is for that, I'm a proud never ending learner (it doesn't mean that I always learn something :sweat_smile: ).

Would you like to submit this for review @alciregi ?

I don't think it is a good move 😄 It is a little mess.
Maybe when upstream will release the new version (looking at git comments it seems they are working on it, sometime)

Sure, no worries. Projects with slow/inactive upstreams always a bit hard to work with.

In the meantime, would you like to join the package-maintainer team as a neuro-sig co-maintainer?

Honestly I don't know if I could really be of any help here.

You can work on simple updates and learn along the way?

If it is for that, I'm a proud never ending learner (it doesn't mean that I always learn something 😅 ).

I'll sponsor you now. You can see the neuro-fedora bugs here: https://tinyurl.com/neurofedora-bugs

Feel free to assign them to yourself, update the specs and open PRs. (Please log out and back in to src.fedoraproject.org for it to show you in the neuro-sig).