Comment 5 for bug 1918013

Since this bug is a packaging issue being fixed in this SRU, it needs SRU information documented please, and should be verified as part of the SRU being landed.

Please also triage other similar-looking package conflicts such as bug 1691729 and bug 1927240. I assume these are covered already so am not blocking this SRU landing in -proposed but someone ought to verify that before landing all the new diversions into -updates.

I'd also like you to look at bug 1927711 please, but again I don't think this should be a blocker right now. However if this situation occurs again I think it'd be appropriate to do it before landing a further SRU with further diversions.