Hi Steve, (Hi Sebastian, this is a reply of the Debian bug #639300, which is about switching soprano from iODBC to unixODBC; you can find the whole log with the mentioned patch at [1].) [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639300 Alle martedì 6 marzo 2012, Steve Langasek ha scritto: > I'm surprised to say that after sitting on this bug for far too long, > it turns out that it's trivial to fix. Although it had been > reported that soprano would not work with unixodbc, once I actually > installed virtuoso, which the soprano test suite silently depends > on, I get the same results from test/virtuosobackendtest when built > against either iODBC or UnixODBC. I remember Sebastian Trueg (main soprano upstream) strongly recommending against using unixODBC (e.g. in [2], just last September), so I'm not sure whether this switch would break anything in the semantic desktop stack. (Disclaimer: I don't use Nepomuk myself.) Sebastian, what is the current status of soprano wrt unixODBC/iODBC? Which problems would result in using unixODBC? [2] http://trueg.wordpress.com/2011/09/22/about-strigi-soprano-virtuoso- clucene-and-libstreamanalyzer/ > I'm happy to upload this as an NMU if you would like. It's probably > worth an upload ASAP rather than waiting for 2.7.5+dfsg.1-1 to > migrate to testing, since it's hard to have usable ODBC drivers for > soprano until it's fixed. We're currently just started our KDE 4.7 transition, which includes also a soprano update from 2.6 to 2.7; if possible, I think IMHO it would be desiderable to wait for such dependency change, in case, after the transition is over (hopefully in two weeks, if everything goes fine). Would this timeframe suit you? -- Pino Toscano
Attachment:
signature.asc
Description: This is a digitally signed message part.