On Mon, 6 Aug 2018, Rob Browning wrote: > > As far as emacs is concerned, it's intended to fully displace the > emacsXY packages, hence the conflicts with all of the emacsXY-common > pacakges in the new emacsen-common.
Yes. And it seems testing/buster is even a bigger mess, as emacs (and related) packages drop in from unstable in an uncoordinated order. Wouldn't it have been better to keep all these transitions in experimental until they stabilize? Cheers, -- Cristian