bug#31991: Packages enki and aseba fail. Organizations behind software restructured

[Sarah Morgensen]

Hi, just following up on this old bug.

Björn Höfling <bjoern.hoefling@bjoernhoefling.de> writes:

> I saw that enki fails due to Qt 5.11.

Enki is now building fine.

> Note that aseba doesn't have a good build history anyway:
>
> https://hydra.gnu.org/job/gnu/master/aseba-1.6.0-0.3b35de8.x86_64-linux/all
> https://hydra.gnu.org/job/gnu/master/aseba-1.6.0-0.3b35de8.i686-linux/all
> https://hydra.gnu.org/job/gnu/master/aseba-1.6.0-0.3b35de8.armhf-linux
>
> Anyone using it?
>
> General note:
>
> As far as I know, this package is here for the Thymio robot, not for
> the asaba Framework as such.
>
> In spring 2018, Mobsya (the organisation behind Thymio) decided to go
> their own way, because they don't have the capacity to maintain the
> whole aseba framework as such. Maintainer wanted for the old aseba
> project. See this announcement for more details:
>
> https://github.com/aseba-community/aseba#thymio-and-mobsya-fork
> https://docs.google.com/document/d/1ijY2dZR2TbSySMqFfbCgG_ifZPGoxrAQaVuZVQZHKlY/edit#
>
> So, in the long term, we should base the package definition on their
> repository:
>
> https://github.com/Mobsya/aseba
>
> They don't have a released version yet. And they pull in a lot more
> dependencies via git.

It looks like they have a released version now (2.2.0, in fact).

There is also the Debian-maintained fork of the original:

https://salsa.debian.org/science-team/aseba

Since aseba continues to fail building, we should either remove it, or
switch to one of those two.

--
Sarah