by WarheadsSE » Tue Dec 13, 2016 3:54 pm
Currently, the rebuild on rethinkdb is blocked on the skipped package gcc5, and this is why this has occurred. If rethinkdb from i686 were to be upgraded to not depend on gcc5, this would magically go away. (as we source it from the ABS for community/rethinkdb i686)