Description: With the release of KDE SC 4.4 Nepomuk will depend on Virtuoso for data storage. Officially only 6.1.0 and higher will be supported.
Since, however, many people already tested Nepomuk in KDE SC 4.4 with Virtuoso 5.0.12 and the database format changed significantly we provide this conversation tool.
Simply start it after installing Virtuoso 6.1.0 and let it do the conversion automatically.
Distribution packagers are encouraged to run the converter before starting Nepomuk with the --auto parameter.
Get Virtuoso 6.1.0 from http://sourceforge.net/projects/virtuoso/files/Last changelog:
1.1 * The converter now makes sure that Nepomuk is disabled. * Full text indexing is now enabled in the new DB. This way there is no need to wait for Virtuoso to update the index once Nepomuk is started. * Updated Virtuoso 5 to 5.0.13.
Hi Trueg,
When running the new version, the following error is generated :
*** Error 37000: [Virtuoso Driver][Virtuoso Server]SQ074: Line 1: syntax error at 'DB' before '.'
at line 1 of Command-Line-Load /tmp/kde-hq000006/virtuosoconverterG18451.tmp:
DB.DBA.RDF_OBJ_FT_RULE_ADD( null, null, 'nepomuk' ); DB.DBA.VT_BATCH_UPDATE ('DB.DBA.RDF_OBJ', 'OFF', null)
Connected to OpenLink Virtuoso
Driver: 05.12.3041 OpenLink Virtuoso ODBC Driver
Maybe these 2 sql commands, should be split over 2 lines ?
Also it might be good if the program asks if the backup should be deleted. It's always good to still have a copy, just in case :-)
Thanks
Regards
Raymond
This doesn't seem like the best way to do things. I need to upgrade Virtuoso from 5.0.12 to 6.1.0. So, I currently have a (build) source tree for 5.0.12, But, to build the converter, I need to download it and build it again. Not really a great design.
> Distribution packagers are encouraged to run the converter before starting Nepomuk with the --auto parameter.
Huh? How are we to do this? We can't use RPM scriptlets as this has to run per user. And we don't start Nepomuk, your upstream autostart .desktop file does.
Why can't this code be added to the Nepomuk Server so it automatically does this on startup?
It can't be done automatically because the conversion could require double the normal amount of db disk space, so I guess the virtuoso user (KDE) has to check if there is space and defer the conversion if not.
trueg: this could be a beeg problem if the user indexes everything. Is there a way to drop the strigi-indexed (ie re-creatable) stuff from the db to reduce its size before the conversion?
Details:
http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSNews#Announcing%20Virtuoso%20Open-Source%20Edition%20v6.1.0
would be nice but =>
sopranocmd --socket ${HOME}/.kde/share/apps/nepomuk/socket --model main --nrl $@
"/usr/bin/sopranocmd(17287)" Error in thread 3066518272 : "QLocalSocket::connectToServer: Invalid name"
Failed to contact Soprano server through socket at /home/kfl62/.kde/share/apps/nepomuk/socket
so can not alias nepomukcmd...
copy and paste from http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/TipsAndTricks#Remove_all_Strigi-indexed_data :)
It's not ${HOME}/.kde/share/... it's
${HOME}/.kde4/share/apps/nepomuk
I did not put this into kdebase for several reasons:
1. I never planned to support Virtuoso V5.
2. I do not want the kde build to depend on a 60mb download
3. The converter is a rather hacky thing provided for early adopters and developers. Most typical users will update via official packages and, thus, will never have seen a V5 db.
One could come up with a small patch for nepomuk server which would call the converter. That is very simple.
How will nepomuk+soprano+virtuoso react if the conversion is not done before the kde session starts, and is instead started manually by the user? Will nepomuk be disabled until the next session start after conversion?
Ratings & Comments
10 Comments
Hi Trueg, When running the new version, the following error is generated : *** Error 37000: [Virtuoso Driver][Virtuoso Server]SQ074: Line 1: syntax error at 'DB' before '.' at line 1 of Command-Line-Load /tmp/kde-hq000006/virtuosoconverterG18451.tmp: DB.DBA.RDF_OBJ_FT_RULE_ADD( null, null, 'nepomuk' ); DB.DBA.VT_BATCH_UPDATE ('DB.DBA.RDF_OBJ', 'OFF', null) Connected to OpenLink Virtuoso Driver: 05.12.3041 OpenLink Virtuoso ODBC Driver Maybe these 2 sql commands, should be split over 2 lines ? Also it might be good if the program asks if the backup should be deleted. It's always good to still have a copy, just in case :-) Thanks Regards Raymond
This doesn't seem like the best way to do things. I need to upgrade Virtuoso from 5.0.12 to 6.1.0. So, I currently have a (build) source tree for 5.0.12, But, to build the converter, I need to download it and build it again. Not really a great design.
> Distribution packagers are encouraged to run the converter before starting Nepomuk with the --auto parameter. Huh? How are we to do this? We can't use RPM scriptlets as this has to run per user. And we don't start Nepomuk, your upstream autostart .desktop file does. Why can't this code be added to the Nepomuk Server so it automatically does this on startup?
+1. And you should mail kde-packagers@ for this discussion.
It can't be done automatically because the conversion could require double the normal amount of db disk space, so I guess the virtuoso user (KDE) has to check if there is space and defer the conversion if not. trueg: this could be a beeg problem if the user indexes everything. Is there a way to drop the strigi-indexed (ie re-creatable) stuff from the db to reduce its size before the conversion? Details: http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSNews#Announcing%20Virtuoso%20Open-Source%20Edition%20v6.1.0
Yes, see http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/TipsAndTricks#Remove_all_Strigi-indexed_data
would be nice but => sopranocmd --socket ${HOME}/.kde/share/apps/nepomuk/socket --model main --nrl $@ "/usr/bin/sopranocmd(17287)" Error in thread 3066518272 : "QLocalSocket::connectToServer: Invalid name" Failed to contact Soprano server through socket at /home/kfl62/.kde/share/apps/nepomuk/socket so can not alias nepomukcmd...
copy and paste from http://techbase.kde.org/Development/Tutorials/Metadata/Nepomuk/TipsAndTricks#Remove_all_Strigi-indexed_data :) It's not ${HOME}/.kde/share/... it's ${HOME}/.kde4/share/apps/nepomuk
I did not put this into kdebase for several reasons: 1. I never planned to support Virtuoso V5. 2. I do not want the kde build to depend on a 60mb download 3. The converter is a rather hacky thing provided for early adopters and developers. Most typical users will update via official packages and, thus, will never have seen a V5 db. One could come up with a small patch for nepomuk server which would call the converter. That is very simple.
How will nepomuk+soprano+virtuoso react if the conversion is not done before the kde session starts, and is instead started manually by the user? Will nepomuk be disabled until the next session start after conversion?