Soprano 2.3.63 – that is the magic version number you need to look out for.
And then once you have updated your kdebase copy to the latest trunk you run your favorite text editor on ~/.kde/share/config/nepomukserverrc. In there you set Soprano Backend=virtuosobackend in the [Basic Settings] section. After that you simply restart Nepomuk as described in the corresponding howto. You can also logout and log back in again but then you won’t be able to provide as nice bug reports.
Once done Nepomuk will convert your database. This can take a loooong time if strigi is enabled. But it will finish. :)
BTW: You need a recent snapshot of Virtuoso 5.0.12 for this to work.
Trueg's Blog 
Pingback: Akari (akari) 's status on Friday, 09-Oct-09 18:14:02 UTC - Identi.ca
Does it mean, that we’ll have finally good working nepomuk and strigi in KDE 4.4.?
that is the plan. :P
Sweeeeet! I hope this speeds up the whole shebang and by making it more appealing, more people will start participating and help you with NEPOMUK! :]
great news :-)
You can convert only not strigi data to speedup the process because strigi can obtain that data again.
I thought about doing that, too.
Still trying to compile the thing :/
Well, more important then a nice nepomuk-backend is(at least for me) a working strigi. Strigi takes aloooot of time to index something, it also takes alot of CPU cycles, at least on my system. Nepomuk itself is nice, but that damn file indexer drives me nuts.
Apart from that. Why is Virtuoso so nice I should make that jump? Any killerfeatures?
regards
out off the top of my head:
1. no java!
2. Less mem usage
3. Faster
4. Integrated full text index for way faster desktop searches that combine full text and graph queries (the latter includes tags and stuff)
5. Powerful SPARQL query extensions like aggregate functions and nested queries.
6. It will soon become a hard dependency. Then Nepomuk won’t work properly anymore with the sesame2 backend. (Due to the features listed above)
You are mistaken about Strigi. Strigi analyzers which are the only part that’s involved in indexing are very fast. Getting this data into the database is what takes most of the time.
This is why with redland backend indexing is disabled. With sesame2 is works somewhat. Virtuoso will hopefully do it faster. Not sure it will be instant indexing though.
The question that everyone is asking now:
May we use Soprano 2.3.63 with KDE 4.3? This is the solution for all NEPOMUK headaches with Fedora.
Soprano 2.4 is fully backwards compatible, so yes.
I installed in from opensuse kde playground repo on 11.2 rc8. No problems, converted the nepomak dat straight away.
I have been waiting for this moment for such a long time. Thanks, Sebastian :)
Are you the same guy that brought us Chakra? If that’s true, thank you for such a great KDE work.
BTW, I’m compiling the new Nepomuk system. May we have something in kdemod-playground? ;)
is there patch for kdebase 4.3.2 to support new virtuoso backend via soprano 2.6.63?
Actually it’s soprano’s task to support the new backend. ATM I have compiled trunk soprano and new virtuoso, while keeping the rest of the kde at 4.3.1. Now waiting for data migration to finish.
You might miss a feature or a bugfix though if you don’t upgrade kdebase. Sebastian might be a better person to explain why you need trunk kdebase :)
Wonderful! I hope someone will make packages for OpenSUSE soon, perhaps in KDE:KDE4:Playground.
http://download.opensuse.org/repositories/home:/cgiboudeaux:/KDE4:/UNSTABLE/openSUSE_Factory/
Install both iodbc and virtuoso stuff :)
Nice to hear this, but how do I actually install this? Soprano from kdesupport claims that virtuoso isn’t installed, however it’s installed from the link in your blog post………
Does it really not find Virtuoso or libiodbc?
Brilliant! Awesome work Sebastian!
Fail with FC11 and kde-unstable kde-redhat repo:
——————————
~/.kde/share/config@karen.dragonfear α:
nepomukserver ; ls -la /usr/lib64/soprano ; rpm -q virtuoso soprano
(Soprano::PluginManager) found no soprano plugin at “/usr/lib64/soprano/libsoprano_redlandbackend.so”
total 593920
drwxr-xr-x 2 root root 4096 oct 13 17:49 .
drwxr-xr-x 195 root root 139264 oct 14 18:52 ..
-rwxr-xr-x 1 root root 28736 oct 11 15:41 libsoprano_nquadparser.so
-rwxr-xr-x 1 root root 20192 oct 11 15:41 libsoprano_nquadserializer.so
-rwxr-xr-x 1 root root 30608 oct 11 15:41 libsoprano_raptorparser.so
-rwxr-xr-x 1 root root 45744 oct 11 15:41 libsoprano_raptorserializer.so
-rwxr-xr-x 1 root root 103464 oct 11 15:41 libsoprano_redlandbackend.so
-rwxr-xr-x 1 root root 196112 oct 11 15:41 libsoprano_virtuosobackend.so
[/usr/bin/nepomukservicestub] (Soprano::PluginManager) found no soprano plugin at “/usr/lib64/soprano/libsoprano_redlandbackend.so”
(Soprano::PluginManager) found no soprano plugin at “/usr/lib64/soprano/libsoprano_virtuosobackend.so”
(Soprano::PluginManager) found no soprano plugin at “/usr/lib64/soprano/libsoprano_redlandbackend.so”
el paquete virtuoso no está instalado
soprano-2.3.63-0.1.20091009.fc11.x86_64
~/.kde/share/config@karen.dragonfear α:
rpm -q virtuoso-opensource
virtuoso-opensource-5.0.12-0.1.rc9.20090916.fc11.x86_64
If this is installed from Fedora packages then I cannot help.
Pingback: Virtuoso, here I come! « vizZzion.org :: sebas' blog