Hi, thank You for that!
Dne Čt 24. dubna 2014 22:02:09, Raymond Wooninck napsal(a):
In the next hours KDE:Current will publish KDE 4.13
SC. As that this release
comes with a big change (Nepomuk -> Baloo), we would like some simple steps
in order to perform the right upgrade.
Before the upgrade
In order to migrate data automatically from the Nepomuk store to the new
format (used by Baloo), you will need Nepomuk up and running, and just for
the time needed for the migration. Ensure that Nepomuk is running before
the update (in System Settings > Desktop Search). This is only necessary in
case Nepomuk is in use on the system.
The upgrade itself
* If you are already using KDE:Current then the upgrade should be a simple
"zypper up" or upgrade packages through YaST Software Management.
* If you are not yet using KDE:Current, then please follow the instructions
to add the necessary repositories. After adding them, a zypper dup is
required to ensure that all the KDE packages are coming from KDE:Current.
Please do not remove nepomuk, as that otherwise the migration to baloo will
fail !! Also after the upgrade please make sure that the following package
is installed "baloo-file". After this check, log off and back on. The
migrator will then run and move all the data that can be migrated to the
new system. It will also turn off Nepomuk at the end of the migration.
At this moment it would be safe to remove the nepomuk related packages like
nepomuk-core, libnepomukwidgets, soprano*, strigi, virtuoso and shared-
desktop-ontologies. There are only a few packages left that are still
requiring the nepomuk-framework (like bangarang, kweshtunotes, etc).
Recently I reinstalled the system because of exchange of hard drive and even I
copied all files from ~ to backup and back and I installed same packages in
same versions, after the reinstall, some thinks related to Nepomuk and Akonadi
were not working properly, so that I deleted them and set them up again. Now
indexing of my big disk and a lot of e-mails etc. is still running (virtuoso-t
fully consumes one CPU core). The question is if this matter for the
migration. I'd guess it shouldn't, but still...
All the best,
Komunita openSUSE GNU/Linuxu
Community of the openSUSE GNU/Linux