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. ** Patch added: "go-md2man-lp1510288.patch" https://bugs.launchpad.net/ubuntu/+source/go-md2man/+bug/1510288/+attachment/4553588/+files/go-md2man-lp1510288.patch ** Changed in: go-md2man (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510288 Title: 1.0.2-1ubuntu1~14.04.1 in trusty-proposed needs to depend on gccgo-go not gccgo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/go-md2man/+bug/1510288/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
