Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz
I've uploaded a version that should fix this. On Sat, 2018-08-11 at 19:42 +, Niels Thykier wrote: > On Thu, 05 Jul 2018 17:35:30 +0300 Lars Wirzenius wrote: > > On Thu, 2018-07-05 at 15:06 +0200, Andreas Beckmann wrote: > > > 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. > > > > I see the problem now. I was confused by you calling it an upgrade problem, > > when it isn't. It's a problem with one package containing the same file as > > another package, and the two packages are only tangentially related. > > > > It doesn't seem to me to be a particularly likely scenario, to me. A user > > would need to change their sources.list to point from stretch to buster, > > and then not upgrade anything else, but install python3-cliapp. > > > > I'll add the Breaks and Replaces some day. Or have all of cliapp removed > > from Debian. > > Hi Lars, > > Do you have an ETA on the upload fixing cliapp? At the moment, cliapp > is a key package and as such a potential blocker for the new Debian release. > > If you are pondering a removal (per your last sentence), the following > packages currently rely on cliapp in testing and would need to migrate > away first: > > """ > > Checking reverse dependencies... > # Broken Depends: > > cmdtest: cmdtest > freedom-maker: freedom-maker > live-wrapper: live-wrapper > vmdb2: vmdb2 > vmdebootstrap: vmdebootstrap > > # Broken Build-Depends: > cmdtest: python-cliapp > freedom-maker: python3-cliapp > live-wrapper: python-cliapp > vmdb2: python3-cliapp > """ > > Thanks, > ~Niels > signature.asc Description: This is a digitally signed message part
Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz
Lars Wirzenius: > On Sat, 2018-08-11 at 19:42 +, Niels Thykier wrote: >> Do you have an ETA on the upload fixing cliapp? At the moment, cliapp >> is a key package and as such a potential blocker for the new Debian release. > > Key pacakge? I did not know that. What makes cliapp a key package? > I had a look at https://udd.debian.org/cgi-bin/key_packages.yaml.cgi and it says: - reason: cmdtest depends python-cliapp source: python-cliapp - reason: xauth build-depends cmdtest source: cmdtest - reason: popcon source: xauth (Where popcon is that one of auth's binaries are installed on 5% or more of all machines reporting back to popcon) > I'll try to get this fixed soon. Sorry about the delay. > Thanks. :) ~Niels
Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz
On Sat, 2018-08-11 at 19:42 +, Niels Thykier wrote: > Do you have an ETA on the upload fixing cliapp? At the moment, cliapp > is a key package and as such a potential blocker for the new Debian release. Key pacakge? I did not know that. What makes cliapp a key package? I'll try to get this fixed soon. Sorry about the delay. signature.asc Description: This is a digitally signed message part
Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz
On Thu, 05 Jul 2018 17:35:30 +0300 Lars Wirzenius wrote: > On Thu, 2018-07-05 at 15:06 +0200, Andreas Beckmann wrote: > > 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. > > I see the problem now. I was confused by you calling it an upgrade problem, > when it isn't. It's a problem with one package containing the same file as > another package, and the two packages are only tangentially related. > > It doesn't seem to me to be a particularly likely scenario, to me. A user > would need to change their sources.list to point from stretch to buster, > and then not upgrade anything else, but install python3-cliapp. > > I'll add the Breaks and Replaces some day. Or have all of cliapp removed > from Debian. Hi Lars, Do you have an ETA on the upload fixing cliapp? At the moment, cliapp is a key package and as such a potential blocker for the new Debian release. If you are pondering a removal (per your last sentence), the following packages currently rely on cliapp in testing and would need to migrate away first: """ Checking reverse dependencies... # Broken Depends: cmdtest: cmdtest freedom-maker: freedom-maker live-wrapper: live-wrapper vmdb2: vmdb2 vmdebootstrap: vmdebootstrap # Broken Build-Depends: cmdtest: python-cliapp freedom-maker: python3-cliapp live-wrapper: python-cliapp vmdb2: python3-cliapp """ Thanks, ~Niels
Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz
On Thu, 2018-07-05 at 15:06 +0200, Andreas Beckmann wrote: > 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. I see the problem now. I was confused by you calling it an upgrade problem, when it isn't. It's a problem with one package containing the same file as another package, and the two packages are only tangentially related. It doesn't seem to me to be a particularly likely scenario, to me. A user would need to change their sources.list to point from stretch to buster, and then not upgrade anything else, but install python3-cliapp. I'll add the Breaks and Replaces some day. Or have all of cliapp removed from Debian. signature.asc Description: This is a digitally signed message part
Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz
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
Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz
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. -- I want to build worthwhile things that might last. --joeyh signature.asc Description: PGP signature
Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz
On Wed, Sep 06, 2017 at 12:31:19AM +0200, Andreas Beckmann wrote: > during a test with piuparts I noticed your package fails to upgrade from > 'stretch'. > It installed fine in 'stretch', then the upgrade to 'buster' fails > because it tries to overwrite other packages files without declaring a > Breaks+Replaces relation. > > See policy 7.6 at > https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces While it's true there's a bug, and I will fix that, I do not understand why piuparts is installing python3-cliapp. That doesn't seem like an obvious thing to do. The python3 version of the package did not exist in stretch, and upgrading the python2 version from stretch to buster seems to work just fine: I just tested that manually in a chroot. From the piuparts log I see that it is explicitly installing the python3 version after upgrading to buster. (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.) -- I want to build worthwhile things that might last. --joeyh signature.asc Description: PGP signature
Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz
Package: python3-cliapp Version: 1.20170827-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stretch'. It installed fine in 'stretch', then the upgrade to 'buster' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces >From the attached log (scroll to the bottom...): 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 cheers, Andreas python-cliapp=1.20160724-2_python3-cliapp=1.20170827-1.log.gz Description: application/gzip
