Kpilot dependency problems APT-GET
 

Hi All I'm having some puzzling problems with apt-get installing kpilot. Here's the output:

Then, I try to install kdelibs4 and it gives me a laundry list of other "dependencies" I need to install. Does this have anything to do with kdelibs4 being a "metapackage?" Thanks in advance for the help.

Edit:
Distro is Ubuntu 5.10. Here's my sources.list:

Looks like you have two different version of KDE available to be installed and apt is getting confused. What is the output of apt-cache policy kpilot?

Thanks for getting back to me...here's the output:

Note: there's an "http..." before "us.archive.ubuntu...", of course. I just get an error when I put that into the thread because I haven't made enough posts to put links in.

Try sudo apt-get -s install kpilot kdelibs4 and if you get any warnings the use apt-cache search kdelibs4 to make sure that the library name has not changed as it has in Debian. If it has then it will most likely have a c2 you would need to add to the name of the kdelibs4 to install. Sometimes it can be necessary to add the extra packages it warns about to the end of the install line until it will install cleanly but do not do this with the libqt3c102-mt package it is too old for it to be needed. Also you may need to use apt-cache policy package_needed then take the version number which in your case here would be apt-get -s install kpilot=4:3.4.0-0ubuntu10 kdelibs4=?????? next_package=??????? ...... just keep adding the package_name=version_number for the packages it says it needs and you will get them all to install eventually then remove the -s from line to do the actual install.

Thanks for the help...I think I am making progress. However, I am still having problems:

Example 1
[Example 2]
There are numerous conflicts, as you can see - especially between the kdelibs4c2 and kdelibs4 packages. Any ideas?

For your second example take the kdelibs4=4:3.4.0-0ubuntu3.4, libarts1=1.4.0-0pre1ubuntu3 out of the line and use the kdelibs4c2, libarts1c2, libopenexr2c2 and libqt3-mt packages in the line. When adding the next packages if any are needed you want the highest version number for the package=???? that you would put on the line always taking the c2 version if available. With you trying to install both the kdelibs4c2 and kdelibs4 packages at the same time you are actually installing both the new (c2) and old versions at the same time it will not work this way.

Whew. OK, I tried your suggestions and am making progress. I have two outstanding issues:

This shows two unmet dependencies, kdelibs4 and libqt3c102-mt.

kdelibs4 - I am using kdelibs4c2, which you said conflicts with kdelibs4 (makes sense). So why is it asking for this?

libqt3c102-mt - I tried installing this independently, and I get this output:

I am hesitant about removing all of these packages, since many of them seem to be critical to the usability of the system
(Openoffice, k3b, kate, python, etc etc) Ideally, I don't want to remove the packages.

Ideas?

This here.
Is telling you kdelibs4c2 needs exactly version 4:3.4.3-0ubuntu1 of kdelibs-bin which is the older version. You should look at the output of apt-cache search kdelibs4c2 to see if there is a newer version because it looks like it has changed again and look at the apt-cache policy of every package you are trying to put on the line and choose the version= number that is at the same or higher number. Another thing to check it the libkcal package here on my install (Debian) it has changed from libkcal2a to libkcal2b so use the apt-cache search libkcal.

Thanks for all your help Stephen, but I ended up uninstalling the c2 version of kdelibs4 and just reinstalling a bunch of kde applications. Works now. Thanks again.

Good to hear it is working again you should figure out which one of the lines in your sources.list the c2 versions are coming from and comment it out so you do not have these problems in your next install/upgrade. Use the apt-cache policy to find the offending line like this.

As you can see I have a couple of options for the package in the 3.4.? version so if the 3.4.3-2 version was causing the problem I would comment out the sid line in the sources.list then apt-get update to refresh the package cache.