On 2018-07-05 11:50, Lars Wirzenius wrote: > On Wed, Jul 04, 2018 at 06:34:41PM +0300, Lars Wirzenius wrote: >> (Also, the advice to use Replaces+Breaks is just wrong for this >> package. The bug is that the same file is in both the python2 and >> python3 versions of the package. The correct solution is to have it in >> at most one package. I will be making that fix eventually.) > > In fact, it turns out I had already done this, in 1.20170827-1. Both > python-cliapp and python3-cliapp can now be installed at the same > time. I will close the bug. Thanks for reporting the issue, I must > have failed to close the bug in the changelog when uploading.
But the upgrade path from stretch is not clean: Selecting previously unselected package python3-cliapp. Preparing to unpack .../python3-cliapp_1.20170827-1_all.deb ... Unpacking python3-cliapp (1.20170827-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb (--unpack): trying to overwrite '/usr/share/man/man5/cliapp.5.gz', which is also in package python-cliapp 1.20160724-2 Errors were encountered while processing: /var/cache/apt/archives/python3-cliapp_1.20170827-1_all.deb So you will need some Breaks and Replaces against the old package in stretch. It may not be the upgrade path chosen by apt usually, but it is still a valid one, especially if you are doing a partial upgrade. I have some scripts (based on Ralf Treinen's work) looking for potential file conflicts between distros, checking co-installability with DOSE and then instructing piuparts to test certain package combinations and upgrade paths. Andreas
