On Fri, 5 Feb 2010, Dirk Mueller wrote:

> I've included the fix sebas pointed out. also updated kdebase* with fixes:
>
> fe9617eeb6430d12428d4bf1898bc955  kdebindings-4.4.0.tar.bz2
> ddfc358aebe5dc8f5de6f5d1ff7cb018  kdebase-4.4.0.tar.bz2
> 08179cba422038d4bb6537d63186bb23  kdebase-workspace-4.4.0.tar.bz2
> 54b28d1ea9fc93953e1863c06d7b7780  kdebase-runtime-4.4.0.tar.bz2
>
> Greetings,
> Dirk

Everything compiled cleanly, including the l10n tarballs.

I also created a Slackware package for Sebastian Trueg's 
virtuosoconverter, and patched kdebase-runtime to start this converter 
before nepomuk.

Before installing virtuosoconverter, nepomuk refuses to start 
(naturally, because I still had the old v5 database of earlier 
4.4.0 RC's) but after installing the converter and logging in again, 
the converter automatically and successfully migrated nepomuk's 
virtuoso database to the v6 format.

When I release my KDE SC 4.4.0 packages, I want to leave the users 
of previous KDE release candidates a choice of installing that 
converter, or not. Will it be enough to remove the user's 
.kde/share/apps/nepomuk/repository/main directory or are there other 
requirements to clean out the old incompatible nepomuk database data?

Cheers, Eric

-- 
Eric Hameleers <alien@slackware.com>
Jabber: alien@jabber.xs4all.nl
_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team