Comment 30 for bug 150068

For those of you who've left comments about your frustrations, Scott Balneaves (mostly) and myself have been working on Sabayon to get it running again in Ubuntu.

I realize a lot have you have been frustrated by the lack of response. I would like to say that the issue has not been "nobody is paying attention", but rather it's hard to get enough time from people with enough skill to work on it. The problem seems to be that Sabayon relies on the desktop environment underneath and there are subtle differences between distros that can make Sabayon a bit fragile. This makes fixing Sabayon a fairly big project, finding out how Gnome has changed in Ubuntu, doing a lot of debugging to figure out what's causing Sabayon to break, and doing it over and over for each crasher. We don't have an army of coders unfortunately so trying to carve out time has been hard. If any of you know Python and would like to help feel free to contact me.

So overall, trust me, I feel your pain. Sabayon has been a top priority for me personally and Edubuntu and we're really hopeful we can get it going in the next couple months (before Jaunty is released) and will definitely try to backport all the fixes to Intrepid and Hardy. That is part of the reason why we left it in. Hopefully it will be fairly straightforward to fix Sabayon in the previous releases once we've got a set of patches and then it will be useful for people again.