Hi Sandro, On 2018-12-16 20:30, Sandro Tosi wrote: > On Mon, Dec 10, 2018 at 12:57 PM Andreas Beckmann <a...@debian.org> wrote: >> >> Control: retitle -1 python3-matplotlib-dbg: missing Breaks+Replaces: >> python-matplotlib-dbg (<< 2.2.3-3) >> >> On 2018-12-10 17:47, Sandro Tosi wrote: >>> On Mon, Dec 10, 2018 at 11:06 AM Andreas Beckmann <a...@debian.org> wrote: >>> is this right approach? there is a new src:matplotlib2 in experimetal >>> NEW to drop py3k packages (so src:matplotlib2 will only ship python2 >>> and src:matplotlib will only ship py3k package), so that should remove >>> the incompatibility? >> >> This will probably not change anything, but lets see what happens once >> they clear new. > > src:matplotlib2 (producing python-matplotlib*) has been accepted into > experimental - mind giving this another try? thanks!
that doesn't change anything for the case of installing python3-matplotlib-dbg (>= 3.0.2-1) on a system with python-matplotlib-dbg (<< 2.2.3-3), which can easily happen (depending on the unpack order chosen by apt/dpkg) while upgrading from testing or (yesterdays) sid to (todays) sid (once you uploaded the two packages from experimental to sid). So adding Breaks+Replaces: python-matplotlib-dbg (<< 2.2.3-3) to python3-matplotlib-dbg seems to be the best solution to have clean upgrade paths within testing/sid. Andreas
