Unfortunately because the offending change is a package change in xenial, we can't immediately fix this without also losing support for building on wily or vivid. So we'll either need a flexible creative workaround in Mir, or a fix in android-headers itself.
Unfortunately because the offending change is a package change in xenial, we can't immediately fix this without also losing support for building on wily or vivid. So we'll either need a flexible creative workaround in Mir, or a fix in android-headers itself.