Anne Wilson wrote:
> Most of the problems seem to have been caused by an essential update to
> virtuoso coming out far too close to the 4.4 release date for comfort, yet
> needing to be included. Most of us that suffered worst were the ones that
> had been running virtuoso already. The developers thought that hardly any
> 'ordinary users' would fall into that category, and were surprised by the
> result. The 4.4.1 update should be out soon, and I'd be inclined to not
> push 4.4.0 to users that are less than comfortable with fixing things.
The thing is, 4.4.1 does absolutely nothing to solve that Virtuoso migration
issue. Only the Virtuoso Converter can solve it, but it doesn't seem to
actually work. So if you have been running Soprano prereleases with the old
Virtuoso, removing the Virtuoso database is probably the only solution.
(Well, maybe going through the dumping and restoring procedure indicated on
the Virtuoso website by hand could work, but?) Sadly, I don't see the
Virtuoso Converter getting fixed any time soon, upstream isn't very
interested in supporting users of prereleases. :-(
But all this is irrelevant for users who are upgrading from 4.3.5, who are
the ones affected by the KDE 4.4.0 stable push. So I don't see this as a
reason why we should have withheld the 4.4.0 update.
The issues Martin Kho encountered are completely different from the one you
described.
Kevin Kofler
