[Bug 1841516] Re: dpkg installation fails due to file conflict between python-cinderclient and python3-cinderclient
Corey Bryant
1841516 at bugs.launchpad.net
Thu Sep 24 17:03:38 UTC 2020
I've confirmed this is a bug on bionic-train. There is a work-around
which is to remove python-cinderclient, so I'm triaging this a Medium.
** Changed in: python-cinderclient (Ubuntu)
Status: Incomplete => Triaged
** Also affects: python-cinderclient
Importance: Undecided
Status: New
** No longer affects: python-cinderclient
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/train
Importance: Undecided
Status: New
** Also affects: cloud-archive/ussuri
Importance: Undecided
Status: New
** Changed in: cloud-archive/train
Status: New => Triaged
** Changed in: cloud-archive/ussuri
Status: New => Triaged
** Changed in: cloud-archive/train
Importance: Undecided => Medium
** Changed in: cloud-archive/ussuri
Importance: Undecided => High
** Also affects: python-cinderclient (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: python-cinderclient (Ubuntu Focal)
Status: New => Triaged
** Changed in: python-cinderclient (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: python-cinderclient (Ubuntu)
Status: Triaged => Invalid
** Changed in: python-cinderclient (Ubuntu)
Importance: Critical => Undecided
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to python-cinderclient in Ubuntu.
https://bugs.launchpad.net/bugs/1841516
Title:
dpkg installation fails due to file conflict between python-
cinderclient and python3-cinderclient
Status in Ubuntu Cloud Archive:
New
Status in Ubuntu Cloud Archive train series:
Triaged
Status in Ubuntu Cloud Archive ussuri series:
Triaged
Status in python-cinderclient package in Ubuntu:
Invalid
Status in python-cinderclient source package in Focal:
Triaged
Bug description:
Upgrading python3-cinderclient from 1:4.1.0-0ubuntu1 to
2:4.2.1-0ubuntu2 fails on Eoan due to a conflicting file between the
two packages.
It seems there is no equivalent 4.2 upgrade for python-cinderclient so
anyone who previously had both versions installed now meet the
conflict.
lathiat at optane ~$ sudo apt-get dist-upgrade --auto-remove --purge
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
lldb
The following packages will be upgraded:
python3-cinderclient
1 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.
Need to get 0 B/139 kB of archives.
After this operation, 5,120 B of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 381723 files and directories currently installed.)
Preparing to unpack .../python3-cinderclient_1%3a4.2.1-0ubuntu2_all.deb ...
Unpacking python3-cinderclient (1:4.2.1-0ubuntu2) over (1:4.1.0-0ubuntu1) ...
dpkg: error processing archive /var/cache/apt/archives/python3-cinderclient_1%3a4.2.1-0ubuntu2_all.deb (--unpack):
trying to overwrite '/usr/share/bash-completion/completions/cinder.bash_completion', which is also in package python-cinderclient 1:4.1.0-0ubuntu1
Errors were encountered while processing:
/var/cache/apt/archives/python3-cinderclient_1%3a4.2.1-0ubuntu2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
lathiat at optane ~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1841516/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list