Hi, I have installed the kubuntu 10.04 / kde3 64-bit distro and am trying to install that require the two libraries above and am getting the errors below. Thanks Murray root@kubuntu10:/usr/local/share/icons# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: kdelibs-data kdelibs4c2a The following NEW packages will be installed: kdelibs-data kdelibs4c2a 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. 8 not fully installed or removed. Need to get 0B/17.9MB of archives. After this operation, 62.3MB of additional disk space will be used. Do you want to continue [Y/n]? Y (Reading database ... 146714 files and directories currently installed.) Unpacking kdelibs-data (from .../kdelibs-data_4%3a3.5.10.dfsg.1-3ubuntu2_all.deb) ... dpkg: error processing /var/cache/apt/archives/kdelibs-data_4%3a3.5.10.dfsg.1-3ubuntu2_all.deb (--unpack): trying to overwrite '/etc/kde3/colors/40.colors', which is also in package kdelibs-data-kde3 4:3.5.12-0ubuntu6+r1152788 dpkg-deb: subprocess paste killed by signal (Broken pipe) Unpacking kdelibs4c2a (from .../kdelibs4c2a_4%3a3.5.10.dfsg.1-3ubuntu2_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/kdelibs4c2a_4%3a3.5.10.dfsg.1-3ubuntu2_amd64.deb (--unpack): trying to overwrite '/etc/kde3/khotnewstuffrc', which is also in package kdelibs-data-kde3 4:3.5.12-0ubuntu6+r1152788 Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/kdelibs-data_4%3a3.5.10.dfsg.1-3ubuntu2_all.deb /var/cache/apt/archives/kdelibs4c2a_4%3a3.5.10.dfsg.1-3ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1)

The outdated 3.5.10 version of kdelibs in the Ubuntu archives (including kdelibs-data) is not compatible with the new KDE3/Trinity version of kdelibs (which includes kdelibs-data-kde3). Please remove kdelibs-data, and note which programs will be removed with it. Then try reinstalling those programs, but with a -kde3 suffix appended. For example, kolourpaint becomes kolourpaint-kde3.

That its because your official archive maintainers were kind enough to remove the offending packages from the main archive,

and transfer complete control of the KDE3 system to the KDE3 repository maintainers. Ubuntu was not so kind. It is a very simple fix; just remove the old, outdated package and only install the new packages from the KDE3/Trinity repository. Also, I'd would like to point out that Trinity contains features that OpenSUSE does not. OpenSUSE uses a patched version of the original 3.5.10 release, and while they have added features over time their added feature set is quite different that Trinity's. For example, OpenSUSE users cannot resize the panel or system tray icons independently of the panel height.

Trinity users can.

And are they in the official repository now?

If so then OpenSUSE has a more open mind than Ubuntu. If not, at least they were polite enough to remove them so as to avoid conflicts with the KDE3 repository.

>> and transfer complete >> control of the KDE3 system to the KDE3 repository maintainers.

> Do you use Dolpin instead of Konq as some people say?

It always was there. And I am now one of those maintainers, I do with KDE3 repository whatever I want and this goes directly to OpenSUSE main repo in the case the packages in question were not yet dropped from OpenSUSE.

But some people say you broke the file manager so it is not as good as Konq in KDE3 was.

This is due to the fact that they have a different name, e.g. kdelibs-kde3 instead of kdelibs.

I could make kdelibs-kde3 conflict with kdelibs, but I seem to remember that a peculiar side effect crept in when I did that in the past. I can re-enable the conflict statement and see if any problems occur...thoughts anyone?

I don't know. Now that there is an upstream again in the form of Trinity they may be more receptive to the idea. The process should start with Debian, as Ubuntu mirrors Debian's package offerings for the most part. The only issue is that Debian wants an on-call package maintainer, and I am too swamped with the Trinity project itself to properly fill that role.

This is due to the fact that they have a different name, e.g. kdelibs-kde3 instead of kdelibs. I could make kdelibs-kde3 conflict with kdelibs, but I seem to remember that a peculiar side effect crept in when I did that in the past. I can re-enable the conflict statement and see if any problems occur...thoughts anyone?

I don't know. Now that there is an upstream again in the form of Trinity they may be more receptive to the idea. The process should start with Debian, as Ubuntu mirrors Debian's package offerings for the most part. The only issue is that Debian wants an on-call package maintainer, and I am too swamped with the Trinity project itself to properly fill that role. Any volunteers? ;-)

The official version in the archive of all KDE modules, e.g. kdelibs, is the KDE4 version.

Timothy Pearson wrote: I understand that it's not trivial to have a package without the -kde3 suffix?

If you enable the conflict statement, then you should also enable the provides statement. I opened a bug that some packages miss it. It will allow kdbg from the normal Ubuntu repository to work against the Trinity libraries for example.

Does anyone know what the duties and requirements of an on-call package manager would be? :)

I don't have time to argue over which implementation is better; there are limitations in what I can do that are out of my control due to the Debian package format and also the cooperativeness of the distribution maintainers. OpenSUSE has always been more supportive of KDE since the beginning, however I am doing my best under Ubuntu and Debian within the limits that I have. The features that have been added from OpenSUSE are not as numerous as those in the Trinity project (yes I did look at the patch list),

In my opinion it would have been better for KDE3 as a whole if we could have worked off the same codebase, but it seems that OpenSUSE has always shipped a heavily modified version of KDE. Not all users want those changes, so it is probably better to have the two separate versions. Trinity is the equivalent of the old vanilla KDE, and has pulled in many of the the non-SuSE specific patches from the SuSE RPMs, as well as other sources. SuSE is what it always was, and I can respect that. I politely ask that this list remain focused for discussion about the Trinity project itself, and that other projects that wish to remain completely isolated from Trinity only be brought up on the trinity-devel list in the context of GPL-released patches that can be applied to the Trinity codebase. If you or others would like to discuss OpenSUSE, please do it on their dedicated list(s).