package hexchat-plugins 2.12.0-2ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/hexchat-plugin.pc', which is also in package hexchat 2.10.2-1ubuntu3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hexchat (Ubuntu) |
Fix Released
|
High
|
Mattia Rizzolo | ||
Yakkety |
Fix Released
|
High
|
Mattia Rizzolo | ||
Zesty |
Fix Released
|
High
|
Mattia Rizzolo |
Bug Description
[Impact]
* updating hexchat-plugins from xenial to yakkety (or to zesty, fwiw)
plainly fails with a "trying to overwrite" dpkg error
[Test Case]
In xenial chroot:
* apt install hexchat hexchat-plugins
* sed -e s/xenial/yakkety/g /etc/apt/
* apt update
* apt install hexchat hexchat-plugins
=> fail
[Regression Potential]
* can't really see any.
Original bug report follows:
I have YAkkety proposed enabled.
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: hexchat-plugins 2.12.0-2ubuntu2
ProcVersionSign
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
Date: Wed May 25 18:07:59 2016
ErrorMessage: trying to overwrite '/usr/lib/
InstallationDate: Installed on 2016-04-22 (34 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageV
dpkg 1.18.7ubuntu1
apt 1.3~exp1
SourcePackage: hexchat
Title: package hexchat-plugins 2.12.0-2ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in hexchat (Ubuntu): | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in hexchat (Ubuntu): | |
assignee: | Dimitri John Ledkov (xnox) → Mattia Rizzolo (mapreri) |
status: | Confirmed → In Progress |
Changed in hexchat (Ubuntu Yakkety): | |
assignee: | nobody → Mattia Rizzolo (mapreri) |
status: | New → In Progress |
Changed in hexchat (Ubuntu Yakkety): | |
importance: | Undecided → High |
Changed in hexchat (Ubuntu Zesty): | |
importance: | Undecided → High |
description: | updated |
description: | updated |
Status changed to 'Confirmed' because the bug affects multiple users.