On Thu, 05 Jul 2018 17:35:30 +0300 Lars Wirzenius <l...@liw.fi> 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


Reply via email to