I’m aware of existence of the other yggdrasil, but neither “our” yggdrasil nor the other yggdrasil is really ours.
Yeah, yggdrasil doesn’t really do semver so things are a bit tricky with compatibility and keeping up.
Considering we don’t package it I would say no. otoh it is written in go, so one could assume that the binary that gets built should be able to run anywhere as long as the os family and machine architecture matches, but such deployments are left as an exercise to the users.
To solve the naming conflict, we could rename the package we ship, but that feels like it would cause even more pain for everyone involved.
To solve the incompatibility, we could update our worker to be compatible with the latest, but I’d still be hesitant to depend on a package we have no control over (the one from EPEL) as it can change any time without us having time to react to it.
But, as mentioned, the issue is in EPEL, too because of the old version.
Additionally, sooner or later the “other” yggdrasil go package which is curenntly only available for debian/ubuntu might even be packages for EPEL, EL or SUSE. Which will just be a pain.
