On Tuesday 24 April 2007 11:46, Marius Vollmer wrote: > "ext Florian Boor" <florian.boor at kernelconcepts.de> writes: > > - You need to install the libmimedir-gnome1 package manually, it is > > not pulled in automatically. > > Why is this? Could the Application Manager do something different to > make it work? Marius, The problem was caused by a packaging bug (mine), not a problem in the Application Manager. However, while fixing this (and other) packaging bugs I did come across a couple of problems caused by restrictions in the Application Manager: 1) I had chosen the wrong names for some packages. I have now created new packages with the new names but it is necessary to remove the broken packages in order to install the new ones. I used the normal Debian idiom of specifying that the new packages Conflicts:, Replaces: and Provides: the old package. apt-get then (correctly) removes the old package when asked to install the new package (either directly or as a result of a dependency). But the Application Manager just refuses to install the new package reporting conflicts with the old package. Could the Application Manager do the same analysis as apt-get to decide how to complete the installation? 2) Because of the first problem I needed to tell people to remove the old packages first. But these are library packages and are not visible (except in red pill mode). If I tell them to remove the actual user applications involved, the application manager does not seem to remove the dependencies. So I ended up telling them they had to use apt-get to remove the broken packages. Is there a better solution? Graham
