Dear Harald, Well, if I do this: sudo dnf erase nepomuk-core I get... Dependencies resolved. =================================================================================================== Package Arch Version Repository Size =================================================================================================== Removing: initial-setup noarch 0.3.10.1-1.fc20 @System 124 k kde-workspace x86_64 4.11.10-5.fc20 @System 33 M kde-workspace-libs x86_64 4.11.10-5.fc20 @System 2.7 M kdeplasma-addons x86_64 4.13.2-2.fc20 @System 8.9 M kdeplasma-addons-libs x86_64 4.13.2-2.fc20 @System 1.4 M nepomuk-core x86_64 4.13.2-1.fc20 @System 2.1 M nepomuk-core-libs x86_64 4.13.2-1.fc20 @System 1.1 M nepomuk-widgets x86_64 4.13.2-1.fc20 @System 247 k plasma-scriptengine-python x86_64 4.11.10-5.fc20 @System 88 k Transaction Summary =================================================================================================== Remove 9 Packages Installed size: 50 M Is this ok [y/N]: And if I do this: dnf info kde-workspace I see: Installed Packages Name : kde-workspace Arch : x86_64 Epoch : 0 Version : 4.11.10 Release : 5.fc20 Size : 33 M Repo : @System >From repo : kde-unstable Summary : KDE Workspace URL : https://projects.kde.org/projects/kde/kde-workspace License : GPLv2 Description : The KDE Workspace consists of what is the desktop of the KDE Desktop Environment. : This package contains: * khotkeys (a hotkey daemon) * klipper (a cut & paste history : utility) * kmenuedit (the menu editor) * krunner (a command run interface) * kwin : (the window manager of KDE) * plasma (the KDE desktop, panels and widgets workspace : application) * systemsettings (the configuration editor) Which makes me think that it is kde-workspace from unstable that ultimately pulls in nepomuk... Valerio On Wednesday, July 02, 2014 01:53:23 PM Reindl Harald wrote: > Am 02.07.2014 13:31, schrieb valerio.mariani@xxxxxxxxx: > > I see the same thing. I installed 4.13.2 from unstable and then I tried to > > remove nepomuk-core, but kde-workspace from unstable depends on it > > > > On the other hand, it does not seem to be running. It looks like both are > > installed but only baloo is running... > > are you *really* sure "kde-workspace" is from kde-unstable > and *not* from the normal Fedora stable/testing repos? > > they override the builds because kde-workspace is not 4.13 > by definition - it stays at 4.11 forever > > > On Wednesday, July 02, 2014 01:07:10 PM Markus Slopianka wrote: > >> On Wednesday 02 July 2014 10:13:19 Reindl Harald wrote: > >>> however, i guess if you wait a few days you get it > >>> from updates-testing because there are already the > >>> first 4.13 build on koji but not complete for now > >>> > >>> https://koji.fedoraproject.org/koji/buildinfo?buildID=540968 > >> > >> If that is what I now get from kde-unstable, this time Nepomuk is really > >> installed again by kde-workspace from unstable. ;-) > >> Is there a way to always lock out nepomuk-core from being installed? > >> I don't want 2 indexers on my system running at the same time. ;-) > >> _______________________________________________ > >> kde mailing list > >> kde@xxxxxxxxxxxxxxxxxxxxxxx > >> https://admin.fedoraproject.org/mailman/listinfo/kde > >> New to KDE4? - get help from http://userbase.kde.org > > > > _______________________________________________ > > kde mailing list > > kde@xxxxxxxxxxxxxxxxxxxxxxx > > https://admin.fedoraproject.org/mailman/listinfo/kde > > New to KDE4? - get help from http://userbase.kde.org _______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
