Golang pkg sources are imported by build-deps/Built-Using only,
don’t include them via package binary as it triggers false positives.
Remove the now duplicated rule for ubuntu-report.
From this discussion after a bunch of golang dev packages appears in
component-mismatches:
didrocks I’m puzzled to see why germinate against groovy-proposed outputs: golang-google-api-dev | golang-google-api | Rescued from golang-google-api golang-google-api is in universe, I don’t find anything in any seed
and it’s only against proposed. Rationale is: this one and some
others are showing up as root nodes on component-mismatches.
cjwatson This is legitimately extremely confusing, but I think it *might* be
because golang-goprotobuf in -proposed has gained a dependency on golang-google-protobuf-dev, or similar? Basically a bunch of golang
stuff ends up in the build-sources closure of the supported-cloud
seed and that then activates the "Extra-Include: ... *-dev" seed in supported.
I think it might be worth adding "Extra-Exclude: golang-*-dev" to
override that for golang, since the "include all *-dev packages
from otherwise-supported things rule doesn't make as much sense for
golang.
