Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#15805 - [kdebase-workspace] conflicts with policykit-kde
Attached to Project:
Pacman
Opened by Alessandro Doro (adoroo) - Wednesday, 05 August 2009, 09:48 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 01 October 2010, 12:13 GMT
Opened by Alessandro Doro (adoroo) - Wednesday, 05 August 2009, 09:48 GMT
Last edited by Andrea Scarpino (BaSh) - Friday, 01 October 2010, 12:13 GMT
|
DetailsDescription:
pacman -Syu error: failed to commit transaction (conflicting files) kdebase-workspace: /usr/bin/polkit-kde-authorization exists in filesystem kdebase-workspace: /usr/lib/kde4/kcm_pkk_authorization.so exists in filesystem kdebase-workspace: /usr/lib/kde4/libexec/polkit-kde-manager exists in filesystem kdebase-workspace: /usr/lib/libpolkitkdeprivate.so exists in filesystem kdebase-workspace: /usr/lib/libpolkitkdeprivate.so.4 exists in filesystem kdebase-workspace: /usr/share/dbus-1/services/kde-org.freedesktop.PolicyKit.AuthenticationAgent.service exists in filesystem kdebase-workspace: /usr/share/dbus-1/services/org.kde.PolicyKit.service exists in filesystem kdebase-workspace: /usr/share/kde4/services/kcm_pkk_authorization.desktop exists in filesystem Errors occurred, no packages were upgraded. $ LANG=C pacman -Si kdebase-workspace Repository : extra Name : kdebase-workspace Version : 4.3.0-2 Groups : kde Provides : None Depends On : kdelibs-experimental kdepimlibs kdebase-runtime libxxf86misc libxcomposite libxss lm_sensors libxklavier qimageblitz polkit-qt libxft libxdamage Optional Deps : kdebindings-python: plasma scriptengine for Python Conflicts With : kde-common Replaces : kdmtheme kde-common guidance-power-manager policykit-kde I think that replaces is not sufficient and kdebase-workspace should also conflict with policykit-kde. Additional info: * package version(s) kdebase-workspace 4.3.0-2 i686 policykit-kde 0.9.2-2 i686 Steps to reproduce: # pacman -Syu |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Friday, 01 October 2010, 12:13 GMT
Reason for closing: None
Additional comments about closing: old
Friday, 01 October 2010, 12:13 GMT
Reason for closing: None
Additional comments about closing: old
pacman.out
.
-u, --upgrades
Restrict or filter output to packages that are out of date on the local system. (Only package
versions are used to find outdated packages, replacements are not checked here.) This option
works best if the sync database is refreshed using -Sy.
I'm not sure about the meaning.
Anyway I see, e.g.
$ LANG=C pacman -Si qt
Conflicts With : qt4 phonon
Replaces : qt4 phonon
--
From the log:
:: Replace kdebase with extra/kde-meta-kdebase? [Y/n]
:: Replace kdegraphics with extra/kde-meta-kdegraphics? [Y/n]
:: Replace kdemultimedia with extra/kde-meta-kdemultimedia? [Y/n]
:: Replace kdenetwork with extra/kde-meta-kdenetwork? [Y/n]
:: Replace kdeplasma-addons with extra/kde-meta-kdeplasma-addons? [Y/n]
:: Replace phonon with extra/qt? [Y/n]
Every package above conflicts and replaces the previous package.
kdebase-workspace should conflict with policykit-kde. (For example, replacements are ignored with -S.)
However, there is something I don't understand: The following line should have appeared in Alessandro's log:
":: Replace policykit-kde with extra/kdebase-workspace? [Y/n]"
The replacements code was reworked recently, and it should be important to reproduce this bug(?) and report it with --debug.
However, from now on, "kdebase-workspace replaces policykit-kde" is interpreted as "kdebase-workspace is a new version of policykit-kde", so if a policykit-kde literal was found earlier in the repos (the repo priority is important here!), this replacement would not be considered.