see summary
This'll be fixed with the 2.0 ebuild, fwiw. Bug#122337.
this is fixed for 2.0.0 as Josh promised.