I think a likely reason is that at-spi2-core has a Conflicts: at-spi, and during update it might not want to remove a package to satisfy a new recommends? So I think we actually need a hard dependency in the meta package here.
I think a likely reason is that at-spi2-core has a Conflicts: at-spi, and during update it might not want to remove a package to satisfy a new recommends? So I think we actually need a hard dependency in the meta package here.