Comment 3 for bug 1510288

Though I agree this is not a regression, it does fall under hardware enablement IMO. The attached patch resolves this by allowing gccgo-go fulfill the build-dep if gccgo > 5 is not available.

Could we avoid future special casing by adding the same to wily iff it is ever updated? If so - maybe we could add a reminder in your backport script so it isn't forgotten.