Hi Guillem,
honestly, I have no idea where this bug exactly came from, but from behavior it is issue in
dependency resolution, which I guess is part of dpkg.
What I observed here is following scenario:
I had packages A (depends on B) and B installed.
removing B (probably via dependencies) results to: remove A B C (unwanted C)
removing A first, than B (two commands) -> C was not affected.
Best regards,
Brano
On 09/12/2015 07:17 PM, Guillem Jover wrote:
Hi!
On Sat, 2015-09-12 at 04:19:30 +0200, Branislav Zahradnik wrote:
Package: dpkg
Version: 1.18.2
Severity: normal
I had a problem with removing some KDE packages, leading to remove gnome.
After rejecting this bug from gnome package maintainer I tried to find more
(ie, remove packages one by one)
I had following issue (with apt-get output):
apt-get remove libkdeui5
The following extra packages will be installed:
libkdecore5 libkdesu5 libkjsapi4 libkjsembed4 libkntlm4 libkpty4
The following packages will be REMOVED:
libkdeui5 libkwineffects1abi5 libnepomuk4 libnepomukcore4 libnepomukquery4a
libnepomukutils4 liboktetagui4 libsendlater4
The following packages will be upgraded:
libkdecore5 libkdesu5 libkjsapi4 libkjsembed4 libkntlm4 libkpty4
then I removed "be REMOVED" packages in reversed order manually without getting
extra packages installed or upgraded.
similar happen with:
apt-get remove libgpgme++2
The following extra packages will be installed:
libreoffice-base-drivers
Suggested packages:
libjtds-java libreoffice-mysql-connector libmyodbc libmysql-java
libsqliteodbc tdsodbc mdbtools
The following packages will be REMOVED:
gnome libgpgme++2 libqgpgme1 libreoffice libreoffice-base libreoffice-
emailmerge libreoffice-evolution libreoffice-help-en-us libreoffice-java-common
libreoffice-officebean libreoffice-report-builder-bin libreoffice-sdbc-hsqldb
openoffice.org openoffice.org-evolution
openoffice.org-help-en-us
The following packages will be upgraded:
libreoffice-base-drivers
removing libqgpgme1 before solved problem again.
Sorry, but I don't think I understand what's the problem being
reported here. Also I don't quite see why this would be a problem in
dpkg (instead of say the package metadata, an ongoing transition or
apt) if there's one at all?
Thanks,
Guillem
