kdepimlibs transition

Harald Sitter sitter at kde.org
Fri Aug 28 09:53:45 UTC 2015

As it turns out the kdepim crew didn't assess transition implications
sufficiently rendering us in a state where there's a whole bunch of
third party apps that use kdepimlibs.

Since those apps are still using kde4libs we need a compatibility
kdepimlibs that is not coming from upstream :(

Consequently there now is a proposed kde4pimlibs [1]. It would be
great if someone could review and upload and get an archive admin to
let the stuff through NEW.

To go along with this and to facilitate pim transitioning out of the
proposed pocket there also is a notes page on the transition heap [2].
For the most part we are stuck on unblocking kdepimlibs (kf5) which
should be entirely possible once kde4pimlibs is in proposed (along
with rebuilds of 3 rdeps).

In theory with kde4pimlibs and rebuild-needing-rdeps in proposed the
entire stack should then be able to transition. If not beating on the
remaining issues until the stack transits is the goal here.

There are however further adjustments to be made later. Firstly
kde4pimlibs probably needs to stop injecting kdepim-runtime rdeps (how
ever it does that to begin with) and then all rdeps need rebuilding to
get rid of runtime. Effectively the compatibility recommended by
upstream is to have link compat but runtime compat will be extremely
limited to not existent. Nothing to be done about this now

kdepimlibs and kde4pimlibs should be entirely co-installable if
problems should get encountered please raise them upstream directly as
this needs addressing asap.

[1] http://anonscm.debian.org/cgit/pkg-kde/krap/kde4pimlibs.git/log/?h=kubuntu_wily_archive
[2] https://notes.kde.org/p/kubuntu-kdepim-15.08-transition

More information about the kubuntu-devel mailing list