Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#17972 - [soprano] should be built with Sesame backend for the KDE SC 4.4 release

Attached to Project: Arch Linux
Opened by mutlu inek (mutlu_inek) - Saturday, 23 January 2010, 20:06 GMT
Last edited by Pierre Schmitz (Pierre) - Sunday, 24 January 2010, 22:07 GMT
Task Type Feature Request
Category Packages: Testing
Status Closed
Assigned To Pierre Schmitz (Pierre)
Andrea Scarpino (BaSh)
Architecture All
Severity Low
Priority Normal
Reported Version 3.3.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I am using the KDE 4.4 RC from [kde-unstable] and have [testing] enabled.

I think it would be very useful if Soprano was built with the Sesame2 backend for 4.4 as well to ensure the migration of Nepomuk's data to the Virtuoso storage.

It won't be a problem for those who use Nepomuk and Strigi solely for file indexing to start with a clean slate, but those who used Nepomuk to tag and rate would lose their data without the Sesame backend. IMHO, the backend could be abandoned after 4.4, though.
This task depends upon

Closed by  Pierre Schmitz (Pierre)
Sunday, 24 January 2010, 22:07 GMT
Reason for closing:  Implemented
Comment by Andrea Scarpino (BaSh) - Saturday, 23 January 2010, 22:26 GMT
  • Field changed: Task Type (Bug Report → Feature Request)
  • Field changed: Summary (Soprano should be built with Sesame backend for the KDE SC 4.4 release → [soprano] should be built with Sesame backend for the KDE SC 4.4 release)
  • Field changed: Category (General → Packages: Testing)
  • Field changed: Architecture (All → All)
I am disagree. Sesame backend never worked here. Instead this virtuoso plugin is working for everybody.
We had problems with OpenJDK/Sun dependence too.

Anyway your point is valid: people who use the Java backend will lose their data (but you are the only one that I know). I am looking for a "migration plain" for datas.
Comment by Pierre Schmitz (Pierre) - Saturday, 23 January 2010, 22:32 GMT
I'll just build soprano with additional sesame backend. Virtuoso will still be the default. The only downside will be that the pacakge size of soprano will increase by ~!MByte.

Please check if soprano 2.3.70.20100120-2 does work. Nepomuk should start migrating the data from sesame2 to virtuozo on first login.
Comment by Andrea Scarpino (BaSh) - Saturday, 23 January 2010, 22:44 GMT
@Pierre
can we provide more backends like we do for phonon?
Comment by Pierre Schmitz (Pierre) - Saturday, 23 January 2010, 22:52 GMT
Maybe, but that would then be just soprano and soprano-sesame2. The virtuoso backend is not optinal. So I guess its fine to ship the sesame2 backend until the KDE 4.4.1 or .2 release.
Comment by mutlu inek (mutlu_inek) - Sunday, 24 January 2010, 21:43 GMT
Works wonderfully. Thanks a lot, Pierre!

And I agree that this can be removed rather early on in the 4.4 cycle. It has always been a major pita.

Loading...